An applicant tracking system, or ATS, is the software many employers use to collect and organise applications. Systems such as Greenhouse, Lever, Ashby and SmartRecruiters store your résumé, pull out your details and let recruiters search and filter. Understanding what they actually do, and what they do not, saves you from both panic and bad advice.
What an ATS really does
Two myths cause most of the confusion.
Myth 1: the ATS automatically rejects most résumés. In most setups, the system parses your résumé into fields (name, jobs, dates, skills) and stores it. A recruiter then searches or filters, and sometimes the employer adds screening questions that can disqualify, such as "Do you have the right to work in this country?". The software is mostly a filing cabinet with a search box.
Myth 2: you must stuff keywords to survive. Keyword stuffing makes your résumé worse for the human who reads it next. What matters is that the system can read your résumé correctly, and that the terms a recruiter would search for actually appear where they are true.
So the goal has two parts: make it parseable, then make it relevant.
Part 1: make it parseable
Parsing fails when software cannot work out where one section ends and another begins. Keep the structure plain.
- Use a single column. Two-column layouts, sidebars and text boxes often get read in the wrong order, so your skills end up in the middle of your last job.
- Use standard section headings. "Experience", "Education", "Skills", "Projects". Creative headings such as "My Journey" confuse parsers.
- Put contact details in the body, not the header or footer. Some systems ignore headers and footers.
- Use common fonts and plain bullets. Arial, Calibri and similar fonts are fine. Skip icons, rating bars and graphics for skills; a bar showing "Python 80%" is unreadable to a parser and vague to a person.
- Save as PDF or DOCX as the posting asks. A text-based PDF is generally fine. A PDF made from a scanned image or a design tool that outlines text is not.
- Write dates consistently. "Jun 2024 to Aug 2025" in every entry. Mixed formats can break the timeline.
- Do not put important text in images. If you have a logo or photo, that is fine, but your name and skills must be real text.
A quick test: copy all the text from your PDF and paste it into a plain text editor. If the order is jumbled or characters are missing, a parser will struggle too.
Part 2: make it relevant
Recruiters search for the terms in the job description. Your task is to be honest and clear about the match.
- Read the posting and pick out the real requirements. Highlight the skills, tools and responsibilities that appear more than once.
- Mirror the language where it is true. If the posting says "stakeholder management" and you did that but called it "client coordination", use their term. If you have not done something, do not claim it.
- Put the strongest match near the top. A short summary of two lines, then your most relevant experience, helps both the system and the reader.
- Spell out acronyms once. "Search engine optimisation (SEO)" lets a search for either term find you.
- Keep a master résumé and tailor a copy for each role. Ten minutes of editing per application beats sending one generic file to fifty roles.
Writing bullets that survive a quick read
Recruiters often spend well under a minute on a first look. Each bullet should show an action and a result.
- Weak: "Responsible for social media."
- Better: "Ran the college tech club's Instagram account; grew followers from 800 to 3,200 in six months with weekly short videos."
You do not need a number in every bullet, but where one exists, use it. If you cannot measure the result, describe the scale or the outcome: what changed because of your work.
For freshers: what goes where
If you have little work experience, lead with Projects and Education, then Skills. Describe each project in two or three bullets: what you built, which tools you used, and what it did. Add a link to the code or live demo. Internships, hackathons, open-source contributions and relevant coursework all count.
Things that do not help
- Hidden white text full of keywords. Parsers read it, recruiters spot it, and it can get you flagged.
- A one-size-fits-all objective statement. Replace it with a short, specific summary.
- Two pages when one is enough. For under about five years of experience, one page is usually right.
- Photos, date of birth, marital status. Practices vary by country, but in many places these are unnecessary and can invite bias.
A final checklist
- Single column, standard headings, plain font
- Contact details in the body
- Text copies cleanly into a plain editor
- Top section matches the role you are applying for
- Bullets show action and result
- Dates and formatting consistent
- File named sensibly, such as FirstName-LastName-Resume.pdf
A good résumé is clear to software and persuasive to a person. Do the first part once, then spend your effort on the second for every application.
