We want an ATS-friendly CV — how do we explain this to candidates, and is it really necessary?

Parsers usually choke on text designed in graphic design tools and exported as PDF. Files without a proper text layer, or those with complex layering and tables, can't be read like plain copy. The fix isn't forcing requirements on candidates; it's using tools that let you preview the original document side-by-side when parsing fails.

Correction: I misremembered the figure, it was a bit lower.

If a 14-person shop writes "Upload an ATS-compliant resume" as if they get 10k applicants, any decent developer will just close the tab. An ATS exists to make your life easier, not to give candidates extra homework.

when I was job hunting whenever I saw corporate jargon like that in a job description I'd stay away thinking the company was stiff and bureaucratic. asking for system compliance instead of just a clean Word doc or PDF scares candidates off for no reason.

our applications doubled after we took that line out. honestly the cv coming in is already a pdf, so even if the system fails to parse it we just open it on the side and check it ourselves in two minutes. these kinds of requirements are a massive waste of time for small teams.

We tested this on 2 technical roles last quarter: with the ATS-compliant disclaimer, we only got 14 applications in the first two weeks. After removing it and adding "a clean, single-column format is recommended," applications jumped to 62 over the next two weeks, and our eventual hire came from that second batch.

Does the software you use ask candidates to upload a resume and then manually re-enter everything into separate form fields? If so the real issue isn't ATS compliance—it's the friction of an overly long application forcing people to type the same info twice.

What you need to do to stop losing candidates is straightforward: 1) Remove the ATS mention from the job posting immediately. 2) Cut the required fields in the application form down to a maximum of three (full name, contact info, file/link). 3) Route any applications where the system encounters a parsing error to a manual review folder instead of automatically deleting them.

How did you solve this? Solutions that work at a small scale collapse when you grow; I learned this late.

I'm also curious if anyone does it differently.

Good call starting this thread. A partnership without a payment schedule locks up at the first split.

Solutions that work at a small scale collapse when you grow; I learned this late.

I'm curious too. When making a decision, first look at what data you have on hand.

Mistakes made on the ATS-friendly CV side are usually reversible but expensive.

I can't fully agree with this. The answer varies greatly by industry; there is no one-size-fits-all rule.

Processes without records never improve, because you don't know what to fix. Correct me if I'm wrong.

My perspective changed after experiencing that. Solutions that work at a small scale collapse when you grow; I learned this late.

This is my opinion, I'm not claiming it's absolute truth.

Generally correct, but one part is missing. Any unwritten clause becomes a point of disagreement later, as both sides remember it differently.

Correct me if I'm wrong.

i have a question. when making decisions write down the worst-case scenario too, not just the best.

I don't think this advice fits everyone. Partnership isn't a decision to make without working together first.

Correct me if I'm wrong.

Yes, that's exactly how it is with ATS-friendly CV. A partnership without a payment schedule locks up at the first split.

If I were you, I'd go this route.

Correct.

My question might sound amateurish sorry about that. The only thing separating friendship from partnership is a written contract.

That's all sorry if I went on too long.