Side projects often show a recruiter something your job title cannot: initiative, and skills you built on your own time. A developer who ships an app after hours, a marketer who grows a newsletter, an analyst who publishes a dashboard, each is proving capability without being told to. But a side project only helps if you present it like work, with a clear result and a reason it belongs on the page. Listed as a hobby, it just takes up space.
Give side projects their own section
If a project is relevant to the target role, do not bury it in “Interests”. Create a “Projects” section, usually below work history, and treat each entry like a job: a title, a one-line description, and bullets that lead with outcomes.
- State the result: “1,200 subscribers in six months”, not “started a newsletter”.
- Name the tools: the stack, platform, or method you used, so the ATS catches the keywords.
- Add a link: a live URL or repo lets the reader verify it in one click.
Show relevance, not just effort
The best side projects on a CV map directly to the job. Applying for a data role? Feature the analysis project and cut the unrelated woodworking blog. A project earns its space by demonstrating a skill the posting asks for, so choose the one or two that match and leave the rest off.
Keep the claims verifiable
Because side projects are self-directed, credibility matters more here than anywhere. Use honest numbers, link to something real, and be ready to talk through the decisions in an interview. A modest project you can explain in depth beats an impressive-sounding one you cannot back up.
Turn each project into a results-first line with the bullet point writer, then run the file through the resume checker to make sure the new section reads cleanly. The keyword scanner confirms your project keywords match the role, and the resume builder formats the Projects block for you.