“What have you been working on?” is a near-guaranteed question in interviews after a career break. A solid portfolio of recent projects signals you have stayed engaged, refreshed your skills, and can ship. A weak portfolio undermines even strong technical interview performance — recruiters and managers want evidence, not just claims.
What hiring managers actually look at
Reality check: nobody clones your repo and runs your code. They look at:
- The README — does it explain what the project does and why?
- The first paragraph of the README — sells or sinks the project
- Code quality of one or two files (skim, not read)
- Live demo if you have one
- Your one-paragraph writeup on resume / LinkedIn
Optimize for that.
The shape of a strong portfolio project
A great portfolio project has:
- A real problem it solves (not a tutorial clone)
- A live demo at a public URL
- A README that explains motivation, architecture, and tradeoffs
- Some level of polish (no broken links, no half-finished screens)
- Stack relevant to your target role
Project ideas by target role
Backend / platform
- A URL shortener with custom analytics, rate limiting, and Redis caching
- A small key-value store with persistence and replication
- A CLI tool that processes a real dataset (NYC taxi data, GitHub events)
- An open-source library that fills a small gap you noticed
Frontend
- A real product you would actually use (personal finance, recipe organizer, fitness tracker)
- A complex UI component (drag-and-drop kanban, calendar, rich-text editor)
- Performance-tuned versions of common patterns (virtualized list, image lazy-load gallery)
- An open-source contribution to a popular OSS project
Data / ML
- An end-to-end project: ingest real data, train a model, serve predictions
- A Streamlit or Dash dashboard analyzing public data
- A reproduced research paper
- A Kaggle competition entry with detailed writeup
Mobile
- A small native app on the App Store or Play Store (even with 10 users)
- A widget, watch app, or shortcut
- A demo of mastery — animation, gesture, offline sync
What does not count as a portfolio
- Tutorials you completed (everyone has done these)
- To-do apps
- Half-finished projects with last commit 8 months ago
- Anything copy-pasted without modification
The README that gets you hired
Structure:
- One-line description: “A real-time collaborative whiteboard built with React, WebSockets, and Postgres.”
- Live demo link
- Why I built this: the problem you solved or the curiosity you scratched
- Architecture: a diagram or short description; technologies and why
- Hard parts: what was challenging, how you solved it
- Future work: shows ongoing thinking
- Run instructions
How recent does it need to be?
The most-recent commit timestamp matters. Hiring managers will look. A project from 2 years ago with no recent activity reads as abandoned. Aim for at least one significant commit in the last 6 months.
The number of projects
Quality over quantity. 2–3 strong projects beat 10 weak ones. If forced to choose between adding a fourth shallow project or polishing the existing three, polish.
Open source as a portfolio
A merged PR to a popular OSS project is one of the strongest signals — proves you can read someone else’s code, follow conventions, and engage with reviewers.
Find OSS issues labeled “good first issue” or “help wanted” in projects you actually use. Start small. Build a track record over months.
Frequently Asked Questions
Should I include projects from before my career break?
Older projects on your resume are fine; do not lead with them on GitHub. Hiring managers look at your most recent work.
Are SaaS side projects with paying users a strong signal?
Extremely. Even 5 paying users says you can ship, market, and support. Mention this prominently.
How do I handle proprietary code I worked on pre-break?
Describe it on your resume; do not commit it. Build new projects in OSS that show similar skills.