Résumés & ATS
How to beat the ATS
An applicant tracking system (ATS) is the software many employers use to receive, store, and search résumés.
Understand what an ATS actually does
An ATS mostly does two things: it parses your résumé into fields (contact info, work history, skills) and it makes those fields searchable so recruiters can find candidates. It is a filing and search tool, not a gatekeeper that secretly rejects you. Ignore the scare stories — the practical goal is a document the system reads correctly and a human can evaluate.
- Treat the ATS as a search index, not an adversary — your job is to be findable and readable.
- Be skeptical of viral statistics about résumés "never being seen"; focus on clean parsing instead.
Match the posting's keywords honestly
Recruiters search by the terms in the job description, so your résumé should use the same words for skills and tools you genuinely have. If the posting says "stakeholder management" and you do that work, use that phrase rather than a personal synonym. The rule is honest matching, not stuffing — never claim skills you lack.
- Mirror the exact skill and tool names from the posting where they truly apply to you.
- Never keyword-stuff or list skills you cannot back up in an interview — it backfires fast.
- Weave keywords into real accomplishments, not a wall of disconnected terms.
Format so it parses cleanly
Parsing errors are the real risk. Tables, multi-column layouts, text inside images, and unusual section names can scramble how the system reads your résumé. Standard, boring structure parses best: clear headings, a single column, and real text rather than graphics.
- Use standard section headings like "Experience," "Education," and "Skills."
- Avoid tables, columns, text boxes, and any text embedded in an image or logo.
- Submit the file format the application asks for, and keep the layout simple.
Tailor per role instead of blasting one résumé
A single generic résumé matches few postings well. Adjusting the summary, the skills you surface, and the emphasis of a few bullet points for each role makes your document genuinely more relevant — both to the search and to the human who reads it next. Tailoring is honest editing, not deception.
- Adjust your summary and top skills to reflect each specific posting.
- Re-order or re-emphasize accomplishments so the most relevant ones lead.
- Keep a master version, then tailor a copy per application.
Key takeaways
- An ATS parses and searches résumés — it is a filing tool, not a secret rejection machine.
- Match the posting's keywords honestly for skills you actually have; never stuff.
- Format simply: standard headings, single column, real text, no tables or image-text.
- Tailor a copy per role so it is genuinely more relevant to the search and the reader.
Build a résumé, then check how well it matches the posting.
Narrative Pro lets you build a résumé from your accomplishments and check its keyword match against a job description you paste in — it scores the match and surfaces which of the posting's terms are missing, so you can tailor honestly.
FAQ
Common questions
What is an ATS?
An applicant tracking system: software employers use to collect, store, parse, and search résumés. Recruiters use it to find candidates by keyword and manage applications.
Does the ATS automatically reject my résumé?
Not on its own in the way the myths suggest. It filters and ranks by the criteria a recruiter sets — those filters can screen candidates in or out before a person looks, and parsing errors can hurt you, but a human typically reviews the candidates the search surfaces. Clean formatting and honest keyword matching are what help.
How do I add keywords without stuffing?
Use the posting's exact terms for skills you genuinely have, woven into real accomplishments. Do not paste a hidden block of keywords or claim skills you cannot defend — recruiters and interviewers catch it.
What formatting breaks an ATS?
Tables, multiple columns, text boxes, headers/footers with key info, and text embedded in images are the usual culprits. A simple single-column layout with standard headings parses most reliably.
Keep going