I remember advising a recent graduate who’d built a neat web app in their spare time but felt it “didn’t count” because they’d never had a job in tech. That’s a story I hear often: self-taught projects feel fluffy compared with formal experience, and candidates hide them or give vague descriptions. I disagree. When framed correctly, self-directed projects are powerful proof of technical ability, curiosity and resilience — three things hiring managers want. Below I share a step-by-step evidence checklist you can use to turn those projects into CV-ready, interview-ready assets.
Start with a crisp project headline
Your CV has limited space and recruiters scan quickly. Lead each project entry with a one-line headline that says what the project does and the main tech you used. Think of it like an elevator pitch:
Example on the CV: Personal finance tracker web app — React, Node.js, MongoDB — 50+ beta users. That single line tells a recruiter the purpose, the tools and that people actually used it.
Use an evidence checklist: what to collect and display
Below is a practical checklist you can follow for every self-taught tech project. Treat these items as small badges of credibility — the more you can tick, the stronger your claim.
| Evidence item | Why it matters | How to present it |
|---|---|---|
| Public repository (GitHub/GitLab) | Shows code, commit history and collaboration habits | Link on CV; highlight key commits or PRs in project description |
| Live demo or deployed app | Demonstrates a working product and user flow | Provide live URL; include a screenshot or short GIF in your portfolio |
| Readable README | Shows communication and project structure | Ensure README has setup, usage, tech stack and known issues |
| Tests and CI | Signals engineering discipline | Mention test coverage and CI service (e.g., GitHub Actions) briefly |
| Metrics or outcomes | Evidence of impact (usage, performance, time saved) | Quantify — “reduced load time by 40%”; “100 daily users” |
| User feedback or testimonials | Third-party validation | Quote short feedback or link to a feedback form/issue thread |
| Short case study | Explains problem, approach and learnings | 1–2 paragraphs in portfolio or linked blog post |
| Relevant libraries/tools | Shows modern tech awareness | List main frameworks and why you chose them |
How to write the project entry on your CV
Keep entries concise and outcome-focused. Use a short bullet set — no more than three bullets per project on your CV. Here’s a template I use with clients:
Example:
Where to host your evidence
Make it easy for recruiters to verify claims. I recommend a simple, clean portfolio page that aggregates your projects, links to repos and hosts short case studies. You can use:
On your CV include a single short URL (use a custom domain or a Bit.ly link) and ensure every project has a clickable link. Recruiters won’t hunt for proofs; you must make them visible at a glance.
Speak to skills, not just tools
Hiring managers care about what you can do with a tool, not just that you used it. Translate technical details into transferable skills:
List skill-focused keywords in both your CV bullets and project README so applicant-tracking systems (ATS) and humans pick them up.
Prepare a one-page case study for interviews
For interviews take one or two projects and prepare a one-page case study that covers:
This document is a conversation starter. I recommend converting it to a PDF and putting a link to it on your portfolio so you can email it to interviewers ahead of time.
Common pitfalls and how to avoid them
When I review CVs I commonly see these mistakes:
Quick checklist to complete before applying
Ticking these off transforms a hobby project into credible evidence you can use in applications and interviews. On Jobzvice Co I often publish examples and CV snippets — check jobzvice.co.uk for templates you can copy. Take the time to present your work clearly: self-taught projects are one of the fastest ways to demonstrate capability and motivation when you don’t yet have formal experience.
