- Three finished, deployed projects beat twenty tutorials.
- Your README is the first interview: explain what, why, how to run it and what you learned.
- Pin your best work and clean up everything else.
What recruiters look for in 60 seconds
Most recruiters and engineers spend about a minute on a portfolio before deciding whether to look deeper. In that minute they want to see that you finish things, write readable code and can explain your work.
- Pinned repositories that match the role you are applying for
- A clear README with a screenshot or live link at the top
- Consistent, meaningful commits over time
- Tests, structure and sensible naming
Choose projects that prove the right skills
Pick projects that mirror real work in your target track. A backend candidate should show an API with a database and tests; a frontend candidate a responsive, accessible app; a data candidate a clean, explained analysis.
Choose problems you genuinely care about — local transport, cricket statistics, a family business — because you will explain them more convincingly.
GitHub README tips: write a README that does the selling
Use the same structure for every project:
- One-line summary and a live link or screenshot
- The problem it solves and who it is for
- Tech stack and why you chose it
- How to run it locally in three commands or fewer
- Key features and what you would improve next
Show professional habits
Small details signal that you are ready for a team.
- Small, descriptive commits instead of one giant upload
- A .gitignore and no secrets or API keys in the repository
- Tests for the core logic
- Issues or a short roadmap showing how you plan work
Polish your GitHub profile
Add a profile README with a short introduction, your target role, your main skills and links to your best projects and LinkedIn. Pin your three or four strongest repositories and archive or make private anything unfinished that does not represent you well.
Mistakes that make recruiters close the tab
- Many forked repositories with no changes
- Tutorial clones with the original names and styling
- No README or a default template README
- Projects that do not run or have broken live links
- Hard-coded passwords or API keys
Frequently asked questions
Do I need a personal website as well?
Not necessarily. A clean GitHub profile and LinkedIn are enough for most junior roles. A simple portfolio site helps most for frontend and design-heavy roles.
Can I include university projects?
Yes, if you improved them beyond the assignment and can explain them well. Your final-year project is often your strongest piece.
How many projects should I pin?
Three or four that match your target role. Quality and relevance matter more than quantity.
Written by Mubashar Hussain · Founder, TechCareerWay
Engineering leader with 20 years building banking and fintech software across 7 countries. Spotted an error or outdated advice? Tell us.