Lead with what you built, not what you completed
Recruiters skim for evidence of shipped work. Put projects and outcomes at the top, and let the certificate sit quietly at the bottom.
Why the certificate-first CV stalls
A hiring manager reading your CV has one question: can this person do the work? A course certificate answers a different question, whether you finished a curriculum. Thousands of people finished the same curriculum this year, and they all wrote the same three lines about it. When your first section is education, you've spent your best real estate proving you're indistinguishable from every other graduate in the pile.
Shipped work is the opposite. A booking app that handles real users, a data pipeline you rebuilt for your old employer, a browser extension with three hundred installs, each of those is yours alone. Describe what it does, what you chose to build it with, and what happened after you shipped it. Numbers help: users, load times, hours saved, bugs closed. That's the section a technical reviewer actually reads.
Your previous career isn't a gap to apologise for, either. A nurse moving into health tech understands clinical workflows in a way no bootcamp teaches. A logistics coordinator turned backend developer knows exactly why the inventory API keeps timing out at month end. Frame those years as domain knowledge you bring on day one, not as time you spent doing something else.
So the order changes. Projects with outcomes near the top, a short summary that names the role you want and the domain you know, then experience reframed for relevance, then skills you've genuinely used, then education and the certificate as a single line. Same facts, completely different read.
The three moves that flip the read
Projects above the fold
Two or three builds, each with a one-line purpose, the stack you chose, and a measurable result.
Old career as domain depth
Name the industry you came from and the problems you already understand better than a new graduate.
Certificate as a footnote
One line under education. It confirms you trained. It was never going to win you the interview.
Two mechanical failures that sink switcher CVs
Your portfolio is buried at the bottom
A link on the last line gets skipped. Put the portfolio and repository links in the header, next to your email.
Link text that says nothing
"Portfolio" tells a reviewer nothing. Name the project and what it does, so the click feels worth making.
A skills list stuffed with tools you touched once
Every tool you list is fair game in the interview. Cut anything you couldn't debug under pressure.
Skills with no evidence attached
If a language appears in your skills section but in none of your projects, a reviewer reads it as padding.
Formatting that breaks the parser
Columns, icons and text boxes scramble in ATS parsing. Single column, real headings, a PDF exported from text.
Same career, two ways to put it on paper
| Section | Certificate-first CV | Project-first CV |
|---|---|---|
| Opening summary | "Recent bootcamp graduate seeking an entry-level role" | "Backend developer with six years in logistics operations" |
| First section after the summary | Education and course completion | Two shipped projects with stack and outcomes |
| Portfolio links | One line at the very bottom | In the header, named by project |
| Previous career | Listed as unrelated past employment | Reframed as domain knowledge for the target industry |
| Skills section | Every tool mentioned in the syllabus | Tools used in shipped work, grouped by depth |
| Certificate | Three lines with module titles | One line under education |
Find out what a recruiter sees in your first ten seconds
Upload your CV and get an ATS compatibility check, section-by-section feedback, and a ranked list of fixes. No cost, no waiting.
Questions switchers ask us
Should I put my bootcamp on my CV at all?
Yes, but keep it to one line under education: programme name, provider, year. It confirms you trained formally, which some employers do check. What it won't do is differentiate you, because everyone in the applicant pool has a similar line. The differentiation comes from your projects, so give those the space instead.
What counts as a project worth listing?
Anything you built that someone other than a marker could use. A tool that solves a real annoyance, an open-source contribution that got merged, an automation you wrote for your current job, a client site you shipped for free. Tutorial follow-alongs don't count, because the decisions were made for you. If you chose the architecture and hit real bugs, list it.
How do I describe my old career without sounding off-topic?
Translate it into the language of the role you want. Keep the job titles and dates factual, then rewrite the bullets around transferable evidence: systems you owned, data you worked with, stakeholders you managed, processes you improved. A teacher explaining a codebase to a junior is the same skill as explaining fractions. Say it in the target industry's terms.
Where exactly should my portfolio link go?
In the header line with your name, email and location, and again next to each project. Use descriptive text rather than a bare word like "portfolio", so a reviewer knows what they're about to open. Also check that the link survives PDF export, because links pasted as plain text in some builders stop being clickable.
How many tools should my skills section list?
Only those you could discuss for five minutes without notes. A tight list of eight tools you've genuinely shipped with reads stronger than twenty-five that include everything mentioned in a syllabus. Group them by how you use them, and make sure each one appears somewhere in your projects or experience so the claim has evidence behind it.
Will an ATS reject me for having no tech job title?
Screening software matches keywords and parses structure, it doesn't judge your career story. What gets switchers filtered out is usually mechanical: multi-column layouts, skills hidden in graphics, or missing the exact terms from the job description. Fix the structure and mirror the posting's wording, and your projects get read by a human. HRLens flags those parsing issues in seconds.