ATS-friendly resume: write for the software and the recruiter

When you apply through a company’s careers page, your resume usually lands in an ATS first. An applicant tracking system is the software recruiting teams use to receive, sort and search applications. It doesn’t decide on its own who gets hired, but it does shape who a recruiter sees first.

That means your resume has two readers: the system, which has to pull the information out of your file, and the person, who needs to understand in a few seconds why you fit the role. A good resume works for both.

What the ATS does with your file

Every system is a little different, but the basic flow is similar. Your file is converted to text, the system tries to split it into sections such as experience, education and skills, and the recruiter can then search or filter candidates by keywords, job titles and requirements.

In practice, two things follow from that:

• If the text doesn’t come through, it isn’t there. Information inside images, text boxes or elaborate layouts can get lost in the conversion.
• Wording matters. If the posting asks for "data analysis in SQL" and your resume only says "management reporting", a recruiter searching for SQL may never find you, even if you write SQL every day.

Format: plain beats clever

Your resume doesn’t need to be ugly. It needs to be machine-readable.

• Stick to a single column. Two-column layouts sometimes scramble the reading order.
• Use standard section headings: Experience, Education, Skills, Languages. Creative headings make sections harder to detect.
• Keep key details out of headers, footers, tables, icons and images.
• Send a PDF exported from a word processor, or a DOCX when the posting asks for one. A scanned PDF is a picture, not text.
• Format dates consistently, for example "Mar 2022 – Aug 2024".

A quick test: open your PDF, select all the text and paste it into a plain text editor. If the order makes sense and nothing disappears, an ATS will most likely be able to read it too.

Keywords: mirror the posting, don’t copy it

Read the job description and pull out three groups of terms:

1. The job title and its common variations.
2. The tools, technologies and methods listed as requirements.
3. The main responsibilities, in the company’s own words.

Then check that your resume uses those terms where they are true. If you did the same work under a different name, use the name the posting uses. If you don’t have that experience, leave it out. Beyond being dishonest, it will come up in the interview.

Stuffing the page with loose keywords, or hiding them in white text, doesn’t help. People notice, and a list of words without context says nothing about what you actually did.

Show outcomes, not just duties

Once you get past the filter, a person makes the call. For each role, swap task lists for lines that show what changed because of your work:

• Weak: "Responsible for sales reports."
• Better: "Automated the weekly sales report with SQL and Power BI, replacing a manual spreadsheet process."

If you have real figures, such as turnaround time, volume or scale, use them. If you don’t, describe the before and after clearly. Never make up a number to sound more impressive.

One master resume, one version per job

Keeping a complete master resume and tailoring a copy for each application takes effort, but it’s usually worth it for the roles you want most. Adjust the summary, the order of your experience and the wording, without changing facts. Save each version with the company and job title so you always know what you sent.

Pre-submit checklist

• Does the text copy and paste in the right order?
• Is the role you want visible at the top, in your summary?
• Are the requirements you meet written in the posting’s terms?
• Does each role show at least one concrete result or change?
• Are your contact details, location and LinkedIn link up to date?

No tweak guarantees an interview. What a well-built resume does is clear the obstacles: the system can read it, and the person can quickly see why it’s worth talking to you.