How to Write a CV That Actually Gets Interviews in 2026

Recruiters spend an average of 7 seconds on first review. That's not a fault to fix — it's a constraint to design for. In those 7 seconds, the recruiter is scanning for three things: job titles, years of experience, and signals that match the role they're filling. Everything else on your CV either supports those three signals or wastes prime real estate.

This is the no-nonsense guide to what works on a CV in 2026. The principles apply whether you're a fresh graduate, a senior engineer or anyone in between.

The 7-second test

Hand your CV to a friend. Give them exactly 7 seconds to look at it. Then ask: what's my most recent job title, and what company? If they can't answer instantly, your CV is fighting itself.

The fix is structural, not stylistic: put job title and company in bold, large, top of each experience block. Dates in lighter gray on the right. The recruiter's eye should land on titles like reading newspaper headlines.

The one-page rule (and when to break it)

For candidates with under 10 years of experience, one page is the default. Two pages should be earned, not assumed. Each extra page is another 30 seconds the recruiter has to invest — and they often won't.

Two-page CVs are appropriate for:

• 15+ years of relevant experience.
• Academic CVs (research, publications, conference talks).
• Highly senior or executive roles where committee scrutiny is expected.

When in doubt, trim. Every line on your CV should be earning its place by showing you can do this specific job. If a role from 2014 doesn't reinforce that, cut it down to one line or remove it.

The summary statement — should you include one?

Optional but increasingly useful in the AI-screening era. A 2-3 sentence summary at the top mirrors keywords from the job description, gives the recruiter immediate context, and survives well in applicant tracking systems.

A good summary is:

• Specific to the role (rewrite for each application).
• Quantified where possible (not "experienced" — say "8 years building fintech APIs").
• Free of buzzwords ("synergistic team player" is delete-on-sight).

A weak summary makes you look generic. Skip it entirely if you can't write a good one in two minutes.

Experience section — the heart of your CV

Every job entry follows the same structure:

Senior Software Engineer                       2022 — Present
Acme Corp
• Led migration from monolith to micro-frontends; reduced p95 page load by 38%
• Mentored 4 junior engineers; 3 promoted within 12 months
• Designed and shipped payment retry workflow recovering $1.2M in failed charges

The three rules:

1. Lead with verbs. "Led", "Built", "Designed", "Shipped". Not "Responsible for" or "Helped with".
2. Quantify. Numbers are the difference between a forgettable bullet and a memorable one. 38% beats "significantly". $1.2M beats "increased revenue".
3. Show outcomes, not tasks. "Wrote unit tests" is a task. "Reduced production bugs 60% by introducing test-driven development" is an outcome.

The skills section — keep it tight

A wall of 50 skills is the recruiting equivalent of "Jack of all trades, master of none". Group your skills into 3-4 categories and list 5-8 per category. For example:

• Languages: TypeScript, Python, Go
• Frameworks: Next.js, React, FastAPI
• Infrastructure: AWS (ECS, Lambda, RDS), Terraform, Docker

Only list skills you'd be comfortable being asked about in detail. "Familiar with Kubernetes" gets you a 45-minute Kubernetes deep-dive in the interview. Be honest.

Education — its place depends on career stage

New graduates: education goes near the top, includes GPA if 3.5+, relevant coursework, and academic honours. As your professional experience grows, education shrinks and moves down. By year five, education is one line at the bottom: degree, institution, year. That's it.

What to leave off

• Photos. Standard in some European and Asian countries; illegal-to-consider in the US, UK, Canada and Australia due to anti-discrimination law. Default to none unless you know it's culturally expected.
• Date of birth, marital status, religion. Same reason. Outside the EU it's increasingly seen as unprofessional anyway.
• References available upon request. Universally assumed. The phrase wastes a line.
• Hobbies and interests, unless they're genuinely relevant or extraordinary. "Reading and traveling" tells a recruiter nothing.
• Salary expectations. Don't preempt the conversation.

Applicant tracking systems (ATS) — what actually matters in 2026

Most companies use software (Workday, Greenhouse, Lever) to filter CVs before a human sees them. The mythology around "beating the ATS" with secret formatting is overblown. The genuine rules:

1. Use a standard PDF. Not a scanned image. Not a Pages export. Standard text-based PDF.
2. Include the role's keywords. If the job description says "Kubernetes" eight times and your CV doesn't mention it once, the ranking model will deprioritize you. Mirror the language naturally.
3. Use standard section headings. "Experience" beats "Where I've Worked". Boring, but parsable.
4. Avoid columns, tables and headers/footers for content. Many ATS parsers struggle with these. Single-column layouts win.

The CV Builder tool produces a PDF that ticks all four boxes — proper text, parsable layout, clean structure.

Tailoring per application

A generic CV gets you generic results. The 80/20 of tailoring:

• Rewrite the summary statement to reference the specific role and company.
• Reorder bullets within each job so the most relevant experience is on top.
• Add 2-3 skills from the job description if they're genuinely in your toolkit.
• Keep everything else as-is.

15 minutes per application; meaningful improvement in callback rate.

The cover letter question

Most companies don't read cover letters carefully — but a strong one wins ties. If the application asks for one, write 3 short paragraphs:

1. Why this company specifically (not generic — show you've researched).
2. Why you're a good fit, with one concrete example.
3. What you bring that the CV doesn't capture.

If they don't ask, skip it. A generic cover letter actively hurts.

The 30-second pre-send checklist

1. Job title and company are bold and instantly scannable.
2. Every bullet leads with a verb.
3. At least half the bullets are quantified.
4. Keywords from the job description appear naturally.
5. Standard PDF, single column, no header/footer for important content.
6. Spell-check the company name twice. Wrong company name kills the application instantly.