Applying & Standing Out
How applicant tracking systems actually work
An applicant tracking system is the software a company uses to collect and manage job applications. Every resume you submit to a corporate job posting goes into one. Understanding what happens to it there changes how you write your resume and where you spend your energy.
It stores your application and makes it searchable. It does not automatically reject you for missing keywords, and it doesn't scan your resume against a checklist and eliminate you. That's a persistent myth. The filtering mostly happens at the human level, once a recruiter decides which criteria matter and runs a search.
What ATS systems do affect is findability. If a recruiter searches the system for "project management" and your resume says "leading cross-functional initiatives," you won't show up in that search. This isn't about gaming the system. It's about using the same language the job description uses when it accurately describes your work.
Formatting matters more than most people expect. ATS systems parse your resume into structured data. Complex layouts, tables, headers and footers, and text in graphics often parse incorrectly. A recruiter might see a clean formatted resume on their screen, but the underlying data the system extracted might be garbled.
Not every system works the same way
There is no single ATS algorithm. Each vendor parses and ranks differently, so a universal "ATS score" is an approximation, never a guarantee. Some systems, like Greenhouse, don't auto-score or auto-reject at all by design. A human reads the actual resume and the parsed fields are just supporting metadata. Others lean on a competent parser but penalize multi-column and creative formats and skip anything in the header or footer. The strictest do literal, exact keyword matching.
The practical takeaway: you can't reverse-engineer one filter to beat, so aim for the two things that help across all of them. Make the resume parse cleanly, and use the role's actual language where it honestly describes your work.
What actually breaks parsing
A few formatting choices reliably scramble a resume, and every one is avoidable. Multi-column and table layouts are the worst offender: the extractor reads straight across the columns, so "Skills | Work Experience" becomes one garbled line. Nonstandard section headers hurt too, so call it Experience, not "Where I've worked." Contact details stuck in the document's header or footer region often get skipped entirely. And anything living inside an image, text box, or graphic usually doesn't get read at all.
A single-column layout, plain section headers, standard fonts, and your contact info in the body of the document parses cleanly almost everywhere. That one change does more than any amount of keyword tuning.
What most people don't know
The ATS is one filter of several. Recruiters at large companies are processing volume. They're looking for a reason to put you in the yes pile quickly, not a reason to reject you. The resume that makes it easy to see your relevant experience at a glance does better than the resume that's technically thorough but slow to read.
At smaller companies, the ATS might barely be used at all. Some founders and hiring managers pull applications themselves, skim for something that catches their eye, and reach out directly.
Referrals largely bypass the ATS. When someone submits your resume internally, it often goes directly to the hiring manager or recruiter with a flag. This is why referrals convert at much higher rates than cold applications.
What you can do
Use the job description's language when it accurately describes your experience. A clean, single-column resume format parses more reliably than a designed layout. And for any company you genuinely want to work at, a warm introduction from someone inside is worth more than optimizing your resume for the next twenty minutes.
If you want a read before you apply, PrepVault's Resume match score runs these same checks on any job. It scores how cleanly your resume parses and how well it matches the posting, shows you the structured data a parser would pull, and points out the specific gaps. It's free, and it's in the Prep tab of any job you're tracking.