Should You Add Projects to Your CV?
cover image is from-> Image by tirachardz on Magnific 1. The Problem I was reviewing for software engineering rol es, 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…
The question of whether to include personal projects on a CV is a common one for software engineers. Reviewing for software engineering roles, the author noticed their CV lacked personal projects. Despite having professional experience, they felt it would be beneficial to showcase something they had built.
Personal projects can fill gaps in a resume, given that recruiters typically only spend a few moments reviewing each one. While professional experience demonstrates teamwork, product contributions, and working with production systems, personal projects offer insight into an individual's problem-solving approach and independent project management.
However, not all personal projects are suitable for a CV. Tutorials or basic apps may not add much value. Moreover, many developers work with private repositories, so their professional work may not be visible publicly. A personal project provides a concrete example of their technical skills, including how they structure code, write READMEs, create live demos, and maintain tests and Git history.
When determining which projects to include, the author suggests looking for projects that:
- Solve a real problem
- Have a clear README
- Possess a live demo, if possible
- Demonstrate relevant technologies
- Showcase meaningful Git history, issues, or tests
Ultimately, the purpose of including personal projects is to have something impressive to show potential employers. The author acknowledges they will continue to explore this topic further in the future.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
