If you've applied to a corporate job in the last decade, an ATS has touched your application. Most candidates only hear the term in panicky LinkedIn posts about resumes being "rejected by the robots," which is half wrong. Once you understand what the system actually does, the advice about it stops sounding mystical.

This is a beginner guide. No jargon, no fearmongering, no listicle of 47 ATS hacks.

ATS stands for applicant tracking system

An ATS is a database with a workflow on top. Companies use it to receive job applications, store CVs and cover letters, move candidates through stages (applied → phone screen → interview → offer), and keep records for compliance. Greenhouse, Workday, Lever, Ashby, Taleo, iCIMS — they're all variants of the same idea, with different feature sets and price tags.

Think of it as a CRM for hiring. Sales teams have HubSpot or Salesforce. Recruiting teams have an ATS.

The word "tracking" is the important one. The system's main job is to keep track of where each candidate is in the funnel, who has reviewed them, and what was said. The CV parsing piece — the part candidates obsess over — is one feature among many.

What it actually does to your CV

When you upload a CV, the ATS does three things:

1. Parses the file into structured fields (name, email, work history, education, skills).
2. Stores the original document so a human can open it later.
3. Tags the application with the job, the source (LinkedIn, referral, company page), and the date.

That's the whole pipeline. There's no AI gatekeeper deciding your worth. There's no "score above 80% to pass." Most ATS platforms have ranking features, but at small and mid-sized companies these are often not turned on, and where they are, recruiters routinely override them.

The parsing is where candidates can get hurt — not by being rejected, but by having their information end up in the wrong fields. If your work experience is in a two-column layout, the parser may read your job titles into the skills field. The recruiter then opens a search for "backend engineer" and you don't show up, even though backend engineer is your current role.

Where the "ATS rejection" myth comes from

The popular story is: a robot reads your CV, decides you don't have enough keywords, and trashes it before a human sees it.

The more accurate story is:

• A recruiter at a busy company gets 400 applications for a role.
• They search the ATS for the keywords from the job description.
• They review the top results and ignore the rest in practice, even though those resumes still exist in the database.

No robot rejected you. A human filtered by search, and the search was driven by what was in the parsed data. Your CV's job is to be findable in that search and credible once it's opened. The keywords matter — but as truthful descriptions of what you've done, not as a stuffing exercise.

How to actually "optimize" for an ATS

Most optimization advice boils down to: don't break the parser, and write the same way you'd write for a human reader. Specifically:

• Save as PDF, generated from text (not a scanned image).
• Single column. Two-column resumes parse poorly in many ATS platforms.
• Standard section headers: Experience, Education, Skills. Not My Journey or Where I've Made Magic.
• Use the actual words from the job description in your experience bullets, where they're true. "Managed Kafka pipelines processing 2M events/day" works because it both contains the keyword and proves the claim.
• No headers, footers, or text inside images. Parsers ignore them.
• No fancy fonts or icons that map to obscure characters in the parsed output.

Check out the CV format and structure guide for the layout details. The shorter version: the things that make a CV ATS-friendly are mostly the things that make it readable. They're not in conflict.

What the ATS does after you apply

Understanding the rest of the pipeline helps you stop refreshing your inbox.

Once you apply:

• Your CV sits in the database, attached to the job.
• A recruiter (or sometimes a coordinator) reviews applications in batches.
• They reach out to a shortlist for an initial screen.
• The rest of the applications are usually marked as "not advancing" but kept in the database — sometimes for years, depending on the company's data policies.

This is why you sometimes get a recruiter email a year after you applied. Your record is still there. They searched again, found you, and reached out.

It's also why ghosting feels common: most ATS platforms can send rejection emails automatically, but recruiters often don't trigger them on the bulk "not advancing" group, especially at companies with high volume. Silence isn't a personal verdict, it's an unconfigured workflow.

Common myths, debunked briefly

• "You need to use white text to hide keywords from the human and trick the ATS." Most parsers strip styling. The keyword still gets indexed. The human, if they zoom in or copy-paste, sees the trick. This is a way to get screened out, not in.
• "Tables and columns are always rejected." Some ATS platforms parse tables fine; others don't. The safe play is to assume they don't, but "rejected" overstates it — usually it's parsed badly, not rejected.
• "Specific ATS platforms have public scoring algorithms you can game." Almost all the public ATS-scoring tools are built by resume-optimization companies, not by the ATS vendors themselves. Their scores are guesses.

If you're applying to enough companies that you've started thinking about ATS at all, you probably also need a reusable, cleanly structured CV that's easy to tweak per role. Postulit's LinkedIn-to-CV flow gives you a parseable, single-column starting point so you only have to think about content from there.

The ATS isn't a wall. It's a database. Once you stop treating it like an opponent, your CV gets quieter, more truthful, and easier for the actual human on the other side to act on.