How to check if your CV will actually pass ATS

The quickest way to check is not a fancy tool

If you want to know whether your CV passes ATS, the fastest test does not involve uploading anything anywhere. Open your CV, select all of the text, copy it, and paste it into a plain text editor like Notepad or the notes app on your phone. Then read what comes out.

If your name, contact details, job titles, dates, section headings, and key skills all appear as readable text in a sensible top-to-bottom order, an applicant tracking system can most likely read it too. This is not a hack either. It is the same plain text test that MIT’s careers team recommends for catching text that goes missing or ends up in the wrong order. If chunks are missing, the order is scrambled, or whole sections vanish, you have found your problem before a recruiter ever did. That five-minute check tells you more than most people learn after weeks of silent rejections.

What passing ATS actually means

It helps to be precise about what you are testing for, because “pass the ATS” gets used as if it were a single pass or fail score. In practice it is not.

An applicant tracking system mostly needs to do three things with your CV. It needs to extract the text, recognise which parts are your experience, education, skills, and contact details, and then match your wording against what the role is asking for. Passing the first two is about structure and parsing. The third is about relevance. Plenty of CVs that get quietly binned do not fail because of some secret keyword trick. Some fail earlier, at the parsing stage, when the layout confuses the machine and part of the content never makes it through cleanly. You cannot win the relevance match if the document never parsed properly to begin with.

So when you check your CV, you are really running two separate questions. Can the system read it, and does the content match the job. The manual tests below answer the first. They cannot answer the second, and I will come back to why that matters.

The five-minute manual ATS check

You do not need to pay for this. Work through these in order and you will catch the vast majority of parsing failures.

• Do the plain text test. Select all, copy, and paste into a plain text editor. Everything important should survive as text in the right order.
• Try to select your details. In the original CV, highlight your name, your dates, and a couple of job titles with your cursor. If you cannot select them as text, they are probably images or sit inside a graphic, which is a strong sign a parser will struggle with them too.
• Search for a key skill. Use find in your PDF viewer and search for a specific skill or tool from your experience. If your own viewer cannot find it, do not assume an ATS will do better. Different tools pull text out in different ways, so treat a miss as a warning rather than proof.
• Check the reading order. This is where two-column and sidebar layouts fall apart. In the plain text version, does your work history read in a clean sequence, or has the second column been shuffled into the middle of the first?
• Check your headings. Standard headings such as Experience, Education, Skills, and Projects are easy for a parser to recognise. A clever heading like “Where I have made an impact” looks nicer and reads worse to a machine.
• Check your contact details are in the body. Some systems skip content in the very top header or bottom footer of a document, which is why university careers guidance warns against putting essential details there. Keep your email and phone number in the main body text to be safe.

If your CV clears all of that, it is in reasonable shape structurally. If it stumbles on two or three of these, that is your explanation for a lot of unanswered applications.

What the manual checks cannot tell you

Here is the honest limit. All of the tests above confirm that a machine can read your CV. None of them tell you whether the content is a strong match for the specific role you are chasing.

You can have a perfectly parseable CV that still gets nowhere because the evidence is generic, the language does not line up with the job description, or the most relevant experience is buried three-quarters of the way down. Parsing is the entry ticket, not the win. A clean CV full of vague, one-size-fits-all bullet points will read beautifully and persuade nobody.

That gap is exactly where a manual check runs out of road. It is good at “can it be read” and useless at “is it the right CV for this job”.

When an automated checker earns its place

This is where the idea of a checker becomes genuinely useful rather than just reassuring. The manual tests confirm your CV can be read. What they cannot do is compare your CV against a specific job description and tell you how well the two actually match, and that comparison is usually the bit that decides whether you get read.

Be a little sceptical of any single online result though. A free ATS resume scan from one site and a scan from another can disagree, because real applicant tracking systems are not all built the same way. Use a checker as a strong signal about parsing and relevance, not as a divine verdict on your career. The value is in the direction it points you, not in chasing a perfect number. Inside OutRung a dedicated ATS review is still in the pipeline rather than something I can hand you today, so the part I would point you to right now is the workflow in the next section that stops most of these parsing problems occurring at all.

If your CV fails, fix the structure not the styling

When a CV fails these checks, the instinct is often to reach for a different template. Usually the real fix is more boring than that. The problems tend to come from multi-column layouts, text boxes, tables, icons standing in for words, and polished PDFs that flatten the text order underneath. I have written separately about how to make a CV ATS friendly without stripping it back until it looks like a punishment, and the short version is that restrained structure beats decorative structure almost every time.

The point of checking is not to win a formatting argument with a machine. It is to remove the avoidable friction that stops your actual experience from being seen.

The deeper fix is to stop re-testing fragile documents

If you are running these checks on a hand-built PDF over and over, every fresh version of your CV is a fresh chance to reintroduce a parsing problem. That is a miserable way to apply for jobs, and it is why I lean towards keeping one trusted source of truth instead.

This is the part of OutRung that makes sense to me as a working job seeker rather than a marketing line. You keep a single master profile with your real history, skills, and evidence, and you generate a tailored CV for a specific role from that foundation. The output is structurally clean by construction, so you are not gambling on whether this week’s template quietly broke the reading order again. You spend your energy on relevance, which is the thing the manual checks could never measure anyway.

Check your CV once, properly, and then stop treating machine readability as something you have to rediscover by accident on every application.