Is my CV good enough? Run this 12-point check

How do I know if my CV is good enough?

Your CV is good enough when it clears two bars at the same time: a recruiter skimming for roughly seven seconds can say what you do, at what level, and one thing you actually achieved — and an applicant tracking system can pull your name, contact details, job titles, dates and skills into its database without garbling them. Everything else is refinement. Both bars are deliberately unglamorous, and that's the point. Most CVs that go unanswered don't fail because the prose lacks sparkle. They fail because a parser dropped the phone number sitting in a page header, or because the reader couldn't work out in one pass which job the application was even for.

Notice that neither bar is absolute. "Good enough" is always measured against a specific job ad, which is why the CV that landed you three interviews last spring can go silent this autumn. A recruiter filling a payments engineering role isn't judging your document against some platonic ideal of a CV; they're judging it against the shortlist sitting next to it and the requirements list they were handed. So the honest question isn't "is my CV good?" but "does my CV make the case for this role, faster than the other forty on the pile?" That reframing changes what you edit and in what order.

You can test both bars at home in about ten minutes. For the parsing test, copy the whole document and paste it into a plain text editor: if your contact block vanishes, your bullets interleave with your skills list, or your dates detach from the right employers, that's roughly what the software sees. For the human test, hand the CV to someone outside your field, give them seven seconds, take it back, and ask what job you do and how senior you are. If they hesitate, the top third isn't working. Fix that before you touch anything below the fold.

What does a recruiter actually see in the first seven seconds?

In the opening seconds a recruiter reads four things in a predictable order: your current job title and employer, the role before it, the dates attached to both, and your education. Eye-tracking research on professional recruiters clocked that first pass at around 7.4 seconds, and it showed that they don't read top to bottom like a book — they scan in an F or E pattern, fixating on bold headings and the left edge of the page. Newer studies using structured review tools push the number closer to eleven seconds, and surveys of hiring managers suggest most form an initial view inside fifteen. Whichever figure you believe, the window is brutally short.

That pattern has a direct design consequence: the top third of page one is the only real estate that reliably gets read. It should carry your name, a plain contact line, a headline title that mirrors the job ad, and three or four bullets of quantified proof. Everything you care about but a recruiter doesn't — hobbies, a mission-statement paragraph, a graphic skills wheel — belongs lower or nowhere. The same research found that clean layouts with clear section headings held attention, while cluttered pages, missing job headers, dense paragraphs and multiple columns caused recruiters to disengage and move on to the next file.

Here's my contrarian take: skills bars and star ratings are the single most useless element in modern CV design. They're invisible to a parser, they communicate nothing verifiable to a human — four stars in Python according to whom? — and they burn prime page space that a measurable result could have used. The same goes for the decorative sidebar. If you want proof of skill, write "migrated 14 microservices to Kubernetes, cutting deploy time from 40 minutes to 6" and let the number do the persuading. Specifics survive both the seven-second scan and the interview that follows; graphics survive neither.

What's on the 12-point self-check I should run before sending?

Run these twelve checks in order, because the early ones cause the failures that make the later ones irrelevant. Start with the contact block: select all text in your document, and if your name, email and phone don't highlight, they're trapped in a header or footer field where many parsers never look. That single mistake produces an application with no name attached, and it's the most common reason a perfectly strong candidate hears nothing back. Next, check the headline directly under your name matches the title in the ad — if the posting says "Operations Manager" and your CV says "Business Excellence Lead," you've created a mismatch the reader has to resolve for you.

The middle checks cover content. Put three or four quantified achievements in the top third, each with a number, a timeframe or a scale attached. Use standard section headings — Experience, Education, Skills — because a parser that meets "My Journey" may treat the whole block as biography and ignore the keywords inside it. Keep to a single column with no text boxes, nested tables or icons. On length, one page is right for the first two or three years; after that, two pages is normal and often preferred, as long as every line earns its place. Padding a thin CV to two pages is worse than a tight one-pager.

Finish with the mechanical checks. Match hard keywords to the ad — tools, certifications, platforms — using the exact wording the employer used, including the acronym and the spelled-out version at least once. Use one consistent date format throughout, and add a one-line explanation for any gap longer than a few months. Keep bullets to two lines, opening with a verb and closing with a result. Proofread for typos, then rename the file something like Dana-Levy-Operations-Manager-CV.docx. Submit .docx unless the posting says otherwise; a text-based PDF is fine when you're emailing a person, but never an image-based export from a design tool.

Two of these twelve fail silently — the header-trapped contact block and the broken parse — which is exactly why so many job seekers conclude their CV "isn't good enough" when the content was fine all along. Run the plain-text paste test as your final step. If the output reads as a sensible top-to-bottom document with your details intact, you've passed the machine bar. If a section comes out scrambled or empty, rebuild that section in simple body text before you send anything. It takes five minutes and it's the highest-return edit on this entire list.

Which CV red flags get you binned fastest?

Three red flags do most of the damage: a pattern of short lateral stints, application material that reads as machine-generated, and vague duty-listing with no measurable outcome. In a 2026 survey of 1,500 hiring managers, job-hopping topped the list of candidate red flags at 65%, with heavily AI-generated materials close behind at 49% — a striking result given that 58% of the same group now use AI to screen incoming CVs. Roughly 42% flagged vague or generic descriptions of previous responsibilities. None of these is about talent. All three are about the story your document tells before anyone speaks to you.

Employment gaps are the flag job seekers fear most and the one that's easiest to defuse. Around 63% of hiring managers say an unexplained gap raises questions but deserves an explanation, while only about 12% treat it as a serious negative. The fix costs one line: "Career break — full-time caregiving, 2024–2025" or "Redundancy following restructure; completed AWS certification during search." Short tenures need slightly more work. Recruiters read frequent moves as flight risk only when they're sideways; a twelve-month stint that ended in a bigger title and wider scope reads as ambition. Group genuinely short contract roles under a single consulting heading with a date range that makes sense.

The AI-written flag is newer and catches people off guard, because the tells are stylistic rather than factual. Recruiters notice the same hallmarks repeatedly: triads of adjectives, "spearheaded" and "leveraged" in every bullet, sentences that describe a function without ever naming a number, a tool or a team size, and an opening summary that could belong to any candidate in any industry. Using AI to draft isn't the problem — plenty of recruiters use it themselves. Sending the draft unedited is. Strip the abstractions, put your real tool names and real figures back in, and the flag disappears along with the filler.

Is automated CV feedback better than reviewing my own CV?

Automated feedback beats self-review on the two things you genuinely can't do for yourself: seeing the parsed version of your file, and judging keyword coverage against a specific job ad without bias. You wrote the CV, so your eye fills in the missing context automatically — you read "Project Lead" and mentally attach the nine-person team and the €2M budget, while a stranger reads three words. A parser has no context at all. Running your file through an analysis tool shows you the extracted text, the fields it managed to populate, and the requirements from the ad that your document never mentions. That's diagnosis, not opinion.

Where a human reviewer still wins is judgement: whether your career story hangs together, whether a pivot is explained convincingly, whether a given achievement is impressive for your level or merely adequate. The smart sequence is to use both, in that order. Fix the mechanical failures first, because no mentor's advice about framing matters if the file arrives with your email address missing. Then take a clean, correctly parsing CV to someone in your target industry and ask the question that actually matters: would you call this person in? You'll get a far more useful answer once the noise is gone.

This is precisely what HRLens is built for. Upload your CV for a free AI CV analysis and you'll see the ATS-parsed text, the structural problems the twelve-point check is designed to surface, and where your keyword coverage falls short for the role you're targeting — in under a minute, before you send anything. If the analysis shows your layout is the culprit, our guide to why a designed CV scans badly walks through the rebuild. Run the check, fix what it finds, then apply with the confidence that the machine bar is behind you.

Frequently asked questions