How do applicant tracking systems read your CV, and how do you get past them?

The short answer

Applicant tracking systems read your CV as structured text, not as a beautiful page. The safest approach is a simple layout, clear headings, standard job titles, and the exact evidence the vacancy asks for. They usually do not make a mysterious decision on their own; they help sort, store, and rank. If your CV is hard to parse or too far from the job, it may never reach a human in a useful form.

That means the way past them is not to “hack” anything. It is to make your CV easy for software to read and easy for a person to judge in the same document.

What an applicant tracking system is actually doing

An applicant tracking system is a record-keeping and workflow tool first. Employers use it to collect applications, move people through stages, assign notes, and search for candidates later. When your CV goes in, the system tries to identify parts of it: your name, contact details, work history, education, skills, dates, and sometimes keywords that relate to the role.

The important thing is that the system is not reading like a person. It does not admire design, infer context from a clever layout, or reward a polished aesthetic if the underlying text is messy. It mainly needs to know what the words are and where they belong.

If the software can extract the text cleanly, your CV becomes searchable. If it cannot, you get the worst case: a file that looks fine to you but is garbled, incomplete, or wrongly ordered when the employer opens it.

That is the first thing to understand about getting past it. The aim is not to impress the software. The aim is to avoid confusing it.

How CVs usually get read by software

Most systems attempt some version of these steps:

1. Extract the text from the file.
2. Identify the sections of the document.
3. Read dates, job titles, employers, education, and skills.
4. Compare the content with the vacancy.
5. Store the candidate in a database and make the profile searchable.

That sounds technical, but the practical effect is simple. Anything that makes those steps harder can hurt you.

A CV can be awkward for software when it contains:

• text inside images
• decorative columns that confuse the reading order
• tables used for main content
• headers and footers that hide key details
• icons instead of words
• unusual section names
• heavily nested formatting
• text boxes
• scanned pages that are just pictures of text

The cleaner the structure, the more likely the software is to extract the right words in the right order.

Why format matters even when the content is strong

A good CV with bad structure can look broken once parsed. Your work history might appear out of sequence. A skill might be detached from the job that proves it. A recruiter searching the system for a requirement may not see you because the words were not extracted where the system expected them.

That is why format is not cosmetic. It affects whether the document survives the first technical pass.

What ATS software is usually looking for

Systems are not all identical, but most of them are trying to answer the same questions:

• Who are you?
• What have you done?
• What roles have you held?
• What skills do you list?
• Do you appear to match the vacancy?
• Can a recruiter search for you later?

They tend to look for clear labels and familiar patterns. “Experience,” “Employment History,” “Education,” and “Skills” are easier to process than inventive headings that mean the same thing but make the parser guess.

They also tend to work better when the CV gives them obvious signals. If the job asks for project management, the phrase should appear in your CV where it is true. If the role needs Python, Python should not be buried inside an over-designed section where it may not be found.

The matching is often basic. That is useful to know, because it means the winning CV is usually not the most dramatic one. It is the one that gives the right clues quickly.

Do applicant tracking systems reject resumes?

They can filter applications out of the visible pile, but not always in the dramatic, automated way people imagine. Sometimes the system rejects a file because it cannot be uploaded properly. Sometimes the employer has set a knockout question that removes applicants before anyone sees the CV. Sometimes a recruiter searches for a phrase and never comes across your profile because the wording does not line up.

So the honest answer is: yes, a CV can fail before a human gives it proper attention, but often the failure is not a machine “rejecting” you for being imperfect. It is a mismatch between the document, the form, and the way the employer searches.

That is why the safer question is not “How do I beat the system?” It is “How do I make sure my CV survives the system and reaches the person who can judge it properly?”

The layout rules that matter most

If you want your CV to survive parsing, start with the layout.

Use a simple structure

Keep the document in a plain, familiar order:

• name and contact details
• profile or summary
• skills
• work experience
• education
• additional information only if it helps

That order is not sacred, but it is predictable. Predictability helps software and helps people.

Use standard headings

Use headings that say what they are. “Experience” means experience. “Employment History” means employment history. “Education” means education. “Skills” means skills.

Avoid clever alternatives that force interpretation. If the system has to guess whether “Where I Have Made an Impact” means work history, some of your content may not be handled well.

Keep body text readable

Use a normal font, normal spacing, and enough white space that the page is easy on the eye. A visually busy CV can still be readable, but if the layout needs the reader to work out where the next line begins, the machine may struggle too.

Avoid columns for core content

Columns often look tidy to humans and behave badly in parsing. If your main experience is split across multiple columns, the order can come out scrambled. A single-column layout is usually safer.

Do not put key text in images

If your contact details, skills, or section labels are inside an image, a system may not read them. The same applies to logos, decorative banners, and graphical blocks that replace actual text.

Be careful with tables

Tables can be fine for simple data, but they are risky when used for main narrative content. If your job history sits in a table with dates in one cell and duties in another, the extracted text may not read naturally.

Save in a sensible file type

A CV in a normal text-based file is usually safer than one locked up in an image-heavy format. The most important thing is that the text remains readable. If a file opens beautifully but the words are not extractable, it has failed the basic job.

What content helps you get through

A readable CV is necessary, but not enough. Once the software can see it, the content still needs to look relevant.

Match the job title where it is truthful

If your current or previous title is close to the target role, say so clearly. If the employer is hiring for a product manager and your actual title was “Product Lead,” that is useful. If your title was less obvious, the profile summary and the first bullet points should make the connection plain without exaggerating it.

Use the language of the vacancy

If the advert says stakeholder management, use stakeholder management where that is genuinely part of your work. If it says data analysis, use data analysis where you have done it. Software often searches for terms that appear in the job description.

That does not mean copying the advert word for word. It means translating your real experience into the same language the employer used, so the match is visible.

Put relevant evidence near the top

The first part of your CV should answer the likely question: why should we keep reading? If the role is about operations, put your operations evidence high. If it is about software engineering, do not bury the engineering under unrelated detail.

The software may not literally “understand” relevance the way a human does, but the system and the recruiter both benefit when the strongest fit appears early.

Use specific achievements, not only duties

A CV that only lists responsibilities can look thin. A CV that shows what you actually did gives the system and the reader better material to search and judge.

For example, “Managed client projects” is weaker than “Managed client projects from brief to delivery, coordinating timelines, approvals, and handover.” The second line gives more searchable substance and a clearer sense of scope.

What gets CVs into trouble

Some problems are technical, and some are strategic. You need to avoid both.

Weird formatting that breaks parsing

This is the obvious technical problem. If the document is visually clever but textually awkward, the software may misread it. If your name is split over two lines in a banner, if dates are hidden in sidebars, or if whole sections are built from shapes and text boxes, you are taking a risk.

Generic content that never shows fit

A CV can be perfectly readable and still fail because it is too vague. If every bullet says the same kind of thing and none of them match the role, the employer has little reason to shortlist you.

Overstuffed skill lists

A long list of disconnected tools and buzzwords can look like keyword stuffing. More importantly, it can make your CV less believable if the skills are not anchored in jobs, projects, or outcomes.

Missing dates or unclear chronology

If the system cannot tell when you did what, your experience may be harder to sort. Use clear date ranges. Be consistent. Do not make the reader infer whether a role lasted months or years.

Overcomplicated section names

If the parser cannot tell what a section contains, the words inside it may be less useful. Keep the labels conventional so the content lands where it should.

How to make your CV easy for both software and people

The best CVs for applicant tracking systems are usually the same CVs that are easiest for recruiters to scan.

Start with a clear profile

Write a short summary that states what you are and what you do best. It should not be a slogan. It should be a useful label.

Good summaries answer questions like:

• What kind of role are you targeting?
• What is your strongest area?
• What scale or context have you worked in?
• What are the most relevant capabilities?

For example, a summary that says you are an operations manager with experience in process improvement, supplier coordination, and team leadership is more useful than a generic statement about being motivated and hardworking.

Keep your skills section real

Only list skills you can support elsewhere in the CV. If you say you know a tool or method, the work history should show where you used it.

A good skills section is selective. It is not a dumping ground. It helps the system search, but it also helps the recruiter understand your strengths at a glance.

Write bullets that can be scanned quickly

Each bullet should ideally carry one clear point. Start with the action, then the object, then the result or context if needed.

For example:

• Improved onboarding by redesigning the checklist and reducing missed handover steps.
• Coordinated weekly release planning across engineering, product, and support.
• Built reporting templates that made monthly updates faster and clearer.

That style is useful because it gives concrete terms the system can extract and a human can follow without effort.

Make your chronology obvious

Your CV should not force anyone to guess where one job ends and another starts. Keep dates in the same place. Keep role titles and employers easy to identify. If there was a career break, treat it honestly and briefly instead of letting the reader wonder.

What if your CV has a gap, a switch, or a mixed background?

This is where many people worry that an applicant tracking system will automatically discard them. Usually, the real problem is not the system itself. It is that the document does not explain the story well enough.

If you changed careers

Do not hide the change. Make the target role clear at the top, then show the transferable evidence that supports it. If you moved from operations into data work, the CV should make the bridge visible: reporting, analysis, process improvement, or tools you used in both settings.

If you have gaps

Keep the dates consistent and be brief. A gap that is explained plainly is less distracting than a gap that seems accidental. If you were studying, caring, travelling, or recovering, a short honest line is better than silence.

If you have a mixed background

Lead with the thread that matters for the role. A mixed background is not a problem if the CV shows a pattern. The system may not “understand” your career change, but it can still read the right words in the right place.

What to do when the advert is full of keywords

Some job adverts are written in a way that makes people panic and start stuffing every phrase into the CV. That usually makes things worse.

Read for the real requirements

Separate must-haves from nice-to-haves. If the role is clearly asking for three main things, those are the themes your CV should emphasise. You do not need every phrase in the advert, and you should not pretend to have experience you do not have.

Mirror the language naturally

If the employer uses “cross-functional collaboration,” and that is part of your work, use the same phrase. If they say “client stakeholder engagement,” and you have done that, use it. If they say “building roadmaps,” and you have actually built roadmaps, use it.

If the phrase does not genuinely fit your experience, do not force it in just to look machine-friendly. A recruiter will usually notice the mismatch quickly.

Keep the strongest proof close to the top

If the vacancy revolves around one skill, the clearest evidence for that skill should not be buried. Put it where a search or scan is most likely to find it: the profile, the skills section, and the first few bullets of the most relevant role.

What file type and submission method should you use?

The best answer is the one the employer asks for. If they specify a file type or an online form, follow that instruction exactly.

If you upload a CV

Use a file that preserves text cleanly. The document should open properly and remain searchable. Before sending, check that the text order is still sensible when you open it after saving.

If you paste into a form

You may need to strip out formatting and make the text plain. That can be inconvenient, but it often helps the system read the content reliably.

If the form asks for both a form and a CV

Treat the form as the primary source if it contains the key knockout questions. Make sure the information there matches the CV exactly, especially job titles, dates, and qualifications.

If the platform adds fields for skills or job titles

Use them carefully. These fields can help the system search, but only if the words are accurate and consistent with the document.

How to test whether your CV is machine-readable

You do not need to guess. You can check whether the document is likely to survive parsing.

Open it after saving

If the text flows sensibly when you reopen the file, that is a good sign. If headings have shifted, columns have collapsed, or dates appear in the wrong place, revise the layout.

Copy and paste the text

If you can copy the text from the CV and it pastes in a coherent order, that suggests the document is likely readable. If the result is jumbled, the structure may be too complex.

Review it without the design

Strip away the visual polish in your mind and ask: does the information still make sense? A strong CV should survive as plain text. If it only works as a designed object, it is too fragile.

What not to do if you want past the system

Some advice sounds useful but usually backfires.

Do not stuff the document with repeated keywords

If you repeat a phrase over and over, the CV can look unnatural and may annoy the reader. Use the right language, but use it where it belongs.

Do not make the design do the work

A stylish layout is not a substitute for relevant evidence. If the document is hard to read because it is visually ambitious, you have lost the point.

Do not use creative labels for ordinary sections

“My Journey” is not better than “Experience.” “What I Know” is not better than “Skills.” Simplicity wins here.

Do not hide the facts you think are weak

If your dates, titles, or qualifications are awkward, explain them cleanly. Hiding them often creates more suspicion than the truth does.

Do not assume the software is the real decision-maker

Even when the system screens applications, a person usually cares about fit, clarity, and confidence in the evidence. Write for both.

What actually gets you past ATS and into a shortlist

The practical answer is not one trick. It is a set of habits that make the CV work in ordinary hiring systems.

First, keep the structure simple enough that text can be extracted correctly. Second, use standard section headings so the software knows what it is looking at. Third, put the most relevant evidence near the top. Fourth, use the wording of the job where it reflects your real experience. Fifth, keep the chronology clear and the facts consistent.

If you do those things, you remove most of the preventable barriers.

But the final hurdle is still relevance. A readable CV that does not answer the vacancy will not go far. The best way through is to make the match obvious without pretending it is stronger than it is.

A practical editing order

If you want to improve a CV for applicant tracking systems, edit it in this order:

1. Check that the file opens cleanly and the text order is sensible.
2. Replace any unusual section titles with standard ones.
3. Remove or simplify columns, tables, text boxes, and image-based elements.
4. Make the work history chronological and easy to follow.
5. Move the most relevant evidence to the top of the profile and the most recent role.
6. Add the exact words that truthfully match the vacancy.
7. Cut anything decorative that makes the structure less readable.
8. Confirm that dates, titles, and skills are consistent everywhere.

That sequence handles both the technical and the human side.

If you only change one thing

Make your CV read well as plain text.

If the software can extract the content cleanly, and if the resulting text still tells a clear story about your fit, you have done the main job. The rest is about relevance, not tricks.

Jobee can help you search for roles that match the words and skills already on your CV, but the CV itself still has to be clear enough to be read by the system and the recruiter.

The real rule

Do not try to outsmart the system. Make it easy for the system to see that you are a good fit.

That means plain structure, standard headings, truthful keywords, clear chronology, and evidence that appears where it matters most. If your CV does that, it does not need to be mysterious. It just needs to be legible.