The Top 5 Reasons Your CV Gets Rejected (And What to Do About Each One)

You hit submit. You wait. Nothing.

No rejection email. No interview invite. Just silence — which, in many ways, is harder to deal with than a clear no. Because silence gives you nothing to work with. You don't know if your CV was read and found lacking, or whether it never reached a human at all.

The frustrating reality of the modern job market is that both outcomes are common. CVs get filtered out by automated systems before a recruiter sees them, and they get passed over by recruiters in the first few seconds of scanning. In most cases, the candidate has no idea which happened — or why.

The good news: the reasons CVs fail are remarkably consistent. The same five problems appear again and again, across industries, across seniority levels, across markets. Fixing them won't guarantee you an interview, but not fixing them will consistently cost you one.

Here's what they are, why they matter, and what to do about each.

1. Your CV Isn't Tailored to the Role

This is the single most common reason a strong candidate fails to get a call. And it's the most fixable.

Recruiters read applications all day. They are exceptionally good at spotting a CV that has been copied and pasted from one application to the next, with the company name swapped out and nothing else changed. The tell is subtle but unmistakable: a generic CV emphasises the candidate's career in the abstract rather than demonstrating why this specific role, at this specific company, is the logical next step.

The problem runs deeper than optics. A non-tailored CV fails to connect your experience to the specific requirements of the role. It asks the hiring manager to do the interpretive work of figuring out why your background is relevant, rather than making that connection explicit and easy. Most hiring managers won't do that work. They'll move to the next application.

What does tailoring actually mean in practice? It means reading the job description carefully and asking: what are the three or four most important things this role requires? Then checking: does my CV surface evidence of those things clearly and early? The content of your experience doesn't change — but which parts of it you foreground, how you describe them, and which language you use should shift meaningfully from one application to the next.

Every job is different. Your CV should be too.

2. Missing Role-Specific Keywords

Before a recruiter ever sees your CV, it may pass through an Applicant Tracking System — software that screens applications automatically, looking for signals that the candidate matches the role requirements. The most basic signal an ATS looks for is keywords: specific terms from the job description that appear (or don't appear) in your application.

This matters more than most candidates realise. An ATS doesn't evaluate how well you've described your experience. It checks whether your CV contains the right terms. A highly qualified candidate whose CV describes relevant experience in slightly different language from the job posting can score lower than a less qualified candidate who happens to have used the exact phrases the system is scanning for.

The fix is straightforward, though it requires discipline. Read the job description carefully and identify the specific terms, skills, tools, and role titles it uses. Then check your CV. If your document describes the same capabilities in different language — "data visualisation" where the posting says "data viz," "client-facing communication" where it says "stakeholder management" — update your language to mirror the posting's terminology naturally.

The word "naturally" matters. ATS systems are increasingly sophisticated, and some are designed to flag keyword stuffing — the practice of cramming terms into a document in ways that are grammatically awkward or contextually incoherent. The goal is authentic alignment: using the same language as the job posting because you're genuinely describing the same capabilities, not because you've inserted keywords without meaning.

A quick check before every application: open the job posting alongside your CV. Read both. If someone swapped the CV in place of the job description, would the terminology feel consistent? If not, identify the gaps and address them.

3. Spelling and Grammar Errors

This one is both the most avoidable mistake and one of the most penalised.

Research consistently shows that a significant share of recruiters — estimates typically sit around one in five — will reject a CV on the spot for a single spelling or grammar error. Not because a typo fundamentally changes their assessment of your capability, but because attention to detail is considered a basic professional standard, and a document you're presenting as your best self to a new employer is the place to demonstrate it.

There's also a signalling dimension. A CV with errors signals one of two things to a hiring manager: either you don't have high standards for your own work, or you don't care enough about this application to check it carefully. Neither is the impression you want to make before the first conversation.

The challenge is that your own errors are hard to catch. You read what you meant to write, not what you wrote. This is a well-documented feature of human cognition, not a personal failing — and it means that self-proofing has real limits.

What actually works: read your CV aloud, slowly. Your mouth moves more carefully than your eyes scan, and you're more likely to catch places where the text doesn't flow correctly. Read it backwards, sentence by sentence, which breaks the narrative context that your brain uses to fill in gaps. Ask someone else to read it — a fresh pair of eyes catches things yours will miss. Use grammar-checking software as a final pass, but don't rely on it exclusively because it misses context-dependent errors.

A CV that reads cleanly and professionally signals exactly the level of care and diligence that most employers are looking for in a new hire.

4. Weak or Vague Bullet Points

Most CVs describe what the candidate did. The ones that get interviews describe what the candidate achieved.

This is a more meaningful distinction than it sounds. "Responsible for social media management" is a job description, not an achievement. It tells the hiring manager what you were supposed to do, but says nothing about whether you did it well, what impact it had, or what they would gain by hiring you. Compare it with: "Grew Instagram engagement by 47% over six months by overhauling content strategy and introducing a weekly video series." Same underlying work. Completely different signal.

The difference between these two ways of writing about experience is the difference between a CV that reads as a list of duties and one that reads as a record of impact. Hiring managers are trying to make a prediction about the future: will this person make a meaningful difference in this role? The evidence they have to work with is the evidence of past impact. CVs that provide it make the case. CVs that describe tasks without outcomes leave the hiring manager guessing.

A useful framework for rewriting vague bullet points is CAR: Context, Action, Result. Context sets the situation briefly — what was the problem, the challenge, or the starting point? Action describes what you specifically did — not what the team did, not what the process called for, but your individual contribution. Result describes what happened — ideally in specific, quantified terms.