Technical CVs fail in two predictable ways: they read like a tools list, or they bury real impact under jargon. Whether you work in software, product or data, the fix is the same — make your work legible to the person reading it, and make its relevance obvious. That reader is often a recruiter or hiring manager who is not as deep in your stack as you are, so clarity beats cleverness every time.
Lead with impact, not your tech stack
The first thing a reader should learn is what you build and what it achieves, not an alphabet soup of technologies. Open each role with the problem you worked on and the outcome — the feature shipped, the pipeline built, the metric moved — then bring in the tools as supporting detail. A CV that starts with 'reduced page load time and lifted conversion' is far stronger than one that opens with a list of frameworks.
Organise the skills section — and keep it honest
A technical skills section is expected, but a flat list of forty technologies helps no one. Group them (languages, frameworks, data/cloud, tools) and, ideally, signal depth — what you use daily versus what you have touched. Be honest about level: listing something you used once invites an awkward interview question. Reserve the section for genuine, current competence and let your experience prove the important ones in context.
Show what you built and what changed
Impact is the hardest thing for technical people to write and the most valuable. For each significant piece of work, capture what you built, the scale or constraints, and the result. 'Built an internal dashboard' is weak; 'Built an internal analytics dashboard used by three teams, cutting a weekly manual report from half a day to minutes' shows judgement and value. Where you cannot share exact figures, describe the effect qualitatively — but always answer 'so what?'.
Handle projects and open-source work
Side projects, open-source contributions and portfolio work are legitimate evidence, particularly earlier in your career or when changing specialism. Include the ones that demonstrate relevant skill, describe your actual contribution, and link to them if you can. Keep the framing consistent with paid work: what it does, your role, and why it is worth a reader's time.
Tailor to the role and the stack
Read the advert and mirror its priorities. If the role centres on a particular language, cloud platform or methodology that you genuinely know, make sure it is visible and evidenced near the top — not stranded at the bottom of a list. A data role that emphasises stakeholder communication needs that shown, not just your modelling skills. Tailoring is as important for technical CVs as any other; the stack you lead with should match the job.
Readability and ATS
Resist the temptation to design something elaborate. Multi-column layouts, icons and skill 'rating bars' often confuse applicant tracking systems and add little for humans. A clean, single-column, standard-heading CV parses reliably and reads quickly. Save the creativity for a linked portfolio or GitHub, where it belongs.
Adjust emphasis for your level
Junior candidates should lean on projects, learning and the fundamentals they have demonstrated. Senior candidates should foreground scope, ownership, technical decisions and their impact on teams and systems — architecture, mentoring, trade-offs made and why. The same principles apply; what changes is where the weight sits.
Common mistakes to avoid
- A giant, ungrouped technology list with no sense of depth
- Describing tasks instead of outcomes
- Over-designed layouts that break ATS parsing
- Jargon with no explanation of what was achieved
- The same generic CV sent regardless of the stack in the advert
A worked example
Before: 'Used Python and SQL to build reports.' After: 'Built a Python and SQL reporting pipeline that automated a weekly finance report, removing around a day of manual work each week and cutting errors from manual copy-paste.' The tools are identical; the second version proves you understand why the work mattered — which is what a hiring manager is actually buying.
Where to put links
Include a single clean line near the top for the links that matter — a portfolio, GitHub or relevant profile — rather than scattering URLs through the document. Make sure anything you link is current and worth a click; a broken or empty repository does more harm than no link at all.
Common questions
Should a tech CV list every technology I've used?
No. Group your genuine, current skills and signal depth, and let your experience evidence the important ones. A huge undifferentiated list dilutes the strong signals and invites questions about tools you barely know.
How do I show impact on a technical CV?
For each piece of work, state what you built, the scale or constraint, and what changed as a result — a metric moved, time saved, reliability improved. If exact numbers aren't shareable, describe the effect qualitatively, but always answer 'so what?'.
Do side projects and open source belong on a tech CV?
Yes, especially early-career or when changing specialism. Include ones that show relevant skill, describe your actual contribution, and link to them — framed the same way as paid work.