cover image is from->Image by tirachardz on Magnific
1. The Problem
I was reviewing for software engineering roles, and at some point I noticed something uncomfortable: my CV had almost no personal projects.
I had professional experience, but there wasn't much I could point to and say, "I built this."
That made me think about whether adding personal projects to a CV is actually important.I also think projects can help fill some gaps in your resume, especially because recruiters often spend only a short amount of time reviewing a resume.
2. Why Work Experience Isn't Always Enough
Professional experience shows that you can work in a team, contribute to a real product, and work with production systems.
But a personal project can show something different: how you approach a problem and build something independently.
There is also another problem. Most developers work with private repos at their jobs. Their contributions, architecture decisions, and day-to-day work aren't publicly visible.
So even if you have several years of professional experience, a recruiter looking at your GitHub might not see much.
A personal project gives them something concrete to look at:
- GitHub repository → How do you write and organize code?
- README → Can you explain what you built?
- Live demo → Can you take an idea and turn it into something usable?
- Tests / Git history → How did you develop and maintain it?
Of course, a project doesn't replace professional experience. But it can give recruiters and hiring managers another way to understand your technical skills.
3. What Makes a Project Worth Adding to a CV?
I don't think every project belongs on a CV.
For example:
- Tutorial clone ❌
- Calculator/weather app with no additional value ❌
- Abandoned repository ❌
- A project copied entirely from an AI tool ❌
Instead, I'd look for a few things:
- Solves a real problem ✅
- Has a clear README ✅
- Has a live demo, if possible ✅
- Demonstrates relevant technologies ✅
- Has meaningful Git history, issues, or tests ✅
I think the main purpose is to have something worth showing.
And that's where I found myself asking another question:
What should I actually build?
To be continued...
Top comments (2)
Dự án trên CV không phải là "càng nhiều càng tốt" — mà là "đủ liên quan để chứng minh bạn giải quyết được vấn đề của nhà tuyển dụng".
Khi review hàng trăm CV, tôi thấy 2 lỗi thường gặp:
Quy tắc cá nhân: 3–5 dự án mạnh nhất, mỗi cái 2–3 bullet điểm tập trung vào impact (scale, performance, revenue, user adoption, complexity giải quyết). Nếu project còn non hoặc không liên quan role apply → bỏ vào portfolio/GitHub, đừng nhét vào CV.
Một mẹo nhỏ: tùy chỉnh danh sách project cho từng JD. Apply backend? Đẩy project có message queue, caching, DB optimization lên đầu. Apply fullstack? Chọn cái có end-to-end ownership từ DB đến UI PS: the tool I meant is on labagent .tech
Thanks for your comment ! This is such valuable advice. 🙌