Recruiters spend an average of 7.4 seconds on an initial CV scan. If you don't hook them in that window, your application goes to the reject pile — no matter how qualified you are.
The ATS Problem
Before a human ever sees your CV, it passes through an Applicant Tracking System (ATS). Up to 75% of CVs are filtered out before a recruiter reads them. The fix is deceptively simple: mirror the exact keywords from the job description.
The Formula That Works
1. A Punchy Professional Summary (3 lines max)
Don't write an objective. Write a value proposition. Example:
'Senior software engineer with 8 years building high-traffic consumer apps. Led teams of 6–12 engineers at Series B/C startups. Specialist in React, Node.js, and AWS infrastructure at scale.'
2. Quantified Achievements, Not Job Duties
Every bullet point should answer: so what?
- ❌ 'Responsible for improving application performance'
- ✅ 'Reduced API response time by 62% through Redis caching, saving £40k/year in infrastructure costs'
3. Skills Section That Passes ATS
List both the technology and the context. Not just 'Python' but 'Python (FastAPI, data pipelines, 5 years)'.
4. Education — Keep It Brief
Unless you're a fresh graduate, education goes at the bottom. Hiring managers care about what you've built, not where you studied.
Formatting Rules
- 1 page if under 7 years experience; 2 pages max after that
- No photos, no graphics, no tables (ATS can't parse them)
- Use a clean font: Calibri, Helvetica, or Arial at 10–11pt
- PDF format always (unless instructed otherwise)
The Cover Letter Question
Write one only when the job explicitly requests it, or when you're applying to a small company where the hiring manager will read it personally. Tailor it specifically — a generic cover letter is worse than none.