Graduate CV ATS Guide UK 2026

The graduate CV problem in 2026

Most UK graduate CVs in 2026 don't fail because the candidate is unqualified. They fail because the CV never reaches a human. Roughly 60–75% of UK employers — every Big 4 firm, every major bank, the NHS, most FTSE 350 companies and an increasing number of scale-ups — run new applications through an Applicant Tracking System (ATS) before any recruiter sees them. The ATS scans for specific keywords, formatting patterns, structured experience blocks and signals of role fit. Miss those, and your CV is filtered out before lunch on the day you applied.

This guide is the version of CV advice we wish someone had given us at 21. It's UK-specific (the conventions matter — UK CVs and US résumés differ in length, layout and what's expected), it's grounded in the actual ATS systems UK employers use, and it's about getting through filters without sounding robotic.

What ATS systems UK employers actually use

Knowing the system you're being filtered by changes how you write the CV. The five most common in 2026:

• Workday — used by most FTSE 100 firms, the NHS and Big 4. Strict about heading hierarchy, prefers chronological experience blocks with explicit start/end dates in MM/YYYY format.
• Greenhouse — the dominant ATS at venture-backed UK scaleups (Monzo, Stripe, GoCardless, Wise). Forgiving on formatting but heavy on keyword matching to the JD.
• Lever — common at growth-stage startups. Similar to Greenhouse; pulls keywords from your headline, role titles and skills section.
• SuccessFactors / SAP — used by older enterprise employers (BT, BAE Systems, Unilever). The strictest on formatting; complex layouts, two-column CVs and embedded text-as-image will fail to parse.
• Taleo / Oracle — banking and consulting (HSBC, Barclays, Accenture). Looks specifically for explicit education-section fields and gap analysis.

If the role is at a bank, FTSE 100 or NHS, assume strict ATS rules. If it's a tech startup, assume keyword-led ATS rules. Both still reject the same common mistakes.

The 10 mistakes that get UK graduate CVs filtered

1. Two-column layouts. ATS parsers read top-to-bottom, left-to-right. A sidebar with skills on the left and experience on the right gets parsed as a single column, mashing them together and breaking the keyword extraction. Use single-column.

2. Tables and text boxes. Same reason. Tables of skills, "core competencies" boxes, project boxes — they all break parsing on strict systems. Use plain bulleted lists under H2 section headings.

3. Headers and footers for contact info. Workday in particular ignores text in document headers and footers. Put your email, phone and LinkedIn in the body of the CV, in the first 3 lines.

4. PDFs that are images, not text. If you can't highlight and copy text out of your CV, neither can the ATS. Export as text-based PDF from Word / Pages / Google Docs, never as a scanned image.

5. Custom fonts that fail to embed. Stick to a system-installed font (Calibri, Arial, Helvetica, Georgia, Garamond, Cambria). Niche fonts often ship as images-of-text in the rendered PDF and fail ATS parsing.

6. Missing role keywords. If the JD says "stakeholder management" six times and your CV says "managed client relationships", the keyword match drops. The ATS isn't doing semantic matching — it's doing string matching for the first filter pass. Mirror the JD's exact phrases when you genuinely have the experience.

7. Buzzword-only skills sections. "Hardworking, motivated, team-player" tells the ATS nothing because every CV has those. Skills should be specific, technical and verifiable: "Excel pivot tables", "SQL", "Python (Pandas, scikit-learn)", "Salesforce Lightning", "WCAG 2.1 accessibility audits".

8. Date format inconsistency. Mixing "Sept 2024 – Present", "09/24-Now" and "Autumn 2024" will confuse the ATS into showing gaps that aren't there. Pick one format (MM/YYYY is safest) and apply it everywhere.

9. Implicit role titles. "Worked at Stripe over the summer" needs to be a role title. ATSs scan for explicit job titles in your experience section. Use "Software Engineering Intern · Stripe" formatted exactly the way the JD presents the target role.

10. Five-page life stories. The UK convention is two pages for an experienced grad, one page for an undergraduate. Anything longer is read as inability to prioritise.

Section-by-section: what to put where

Header (top of page 1)

Your name in 14–16pt. Underneath: phone, email, city (no postcode), a LinkedIn URL, a portfolio URL if relevant. No photo (UK convention, unlike Germany). No date of birth or nationality (illegal for the employer to ask, unnecessary to volunteer).

Summary (3–4 lines)

The summary is what a human recruiter reads first if your CV gets past the ATS. Two lines on what you do, two lines on what you're looking for. Avoid the "passionate, driven, team-player" template. Instead:

Final-year Computer Science student at Manchester. Two summer internships at fintechs (Monzo, Wise) building backend services in Go. Looking for graduate software engineering roles in UK fintech from autumn 2026.

Specific. Bookended with the role you want. Easy to skim.

Experience (most space)

Reverse-chronological. For each role:

``` [Role Title] · [Company] MM/YYYY – MM/YYYY [City] · [Work mode if remote/hybrid]

• [Bullet 1: action verb + scope + measurable outcome]
• [Bullet 2: same shape]
• [Bullet 3: tools or methodology used] ```

Each bullet should fit a "I did X to achieve Y" structure. Numbers matter. "Improved customer retention" is weaker than "Improved customer retention by 12% over Q3 by introducing post-purchase follow-up emails." The number doesn't have to be huge — it just has to be specific.

Education

Degree, university, expected/awarded year, classification if 2:1 or above. Optional: 2–4 specific modules if they map to the JD ("Distributed Systems", "Stochastic Processes"). A-Levels only if they're recent — 24-year-olds with 5 years of experience can drop A-Levels.

Skills

Group by category. Don't list 30 skills; pick the 8–12 that are genuinely strong AND relevant to the JD.

``` Languages Python, TypeScript, SQL Frameworks React, Next.js, FastAPI Tools Git, AWS, Docker, Linear ```

Projects (optional, recommended for early-career)

If you don't have much experience, projects are how you demonstrate range. Two paragraphs each: one paragraph on what it is, one on what you built. Link to the live deployment or GitHub.

A graduate CV checklist before you submit

Run this list against your CV every time you send it out. If you can't tick all 10, fix it before you apply.

1. ☐ Single column, no tables, no text boxes
2. ☐ Contact details in the first 3 lines of the body (not in a header)
3. ☐ Saved as text-based PDF from Word / Docs / Pages
4. ☐ System font (Calibri / Arial / Helvetica / Georgia)
5. ☐ Two pages maximum, one if undergraduate
6. ☐ All dates in MM/YYYY format, applied consistently
7. ☐ JD's exact key phrases echoed where you genuinely have the experience
8. ☐ Skills section is specific (no "hardworking, motivated, team-player")
9. ☐ Each experience bullet has a measurable outcome where possible
10. ☐ Summary names the role you actually want, not a generic intro

What to do once your CV is fixed

Even a perfect CV has a 0% conversion rate against a role you don't match. The faster path to interviews is matching your CV to roles that actually fit before you spend time tuning the application.

KeyStep's KeyMatch tool ranks every live UK and EU role against your CV using AI semantic matching — not keyword search — and gives each role a 0–100 fit score plus the specific skill gaps for that role. You spend your time on the top 10 matches, not on 200 roles you'll never hear back from.

When you find a role that scores 80+, use CV Improver to tune your CV to that specific JD before applying. Most users see a 20–40 point ATS score lift after one pass — enough to flip from "silent rejection" to "first-round phone screen" on a meaningful share of applications.

If you're applying to graduate schemes specifically, the graduate scheme landing page lists every live UK graduate scheme KeyStep is tracking — recruited in autumn for next-summer starts, and again in spring for same-year intakes.

A clean CV gets you past the ATS. A matched CV gets you the interview. Use both.