How to write an ATS-friendly resume (that humans like too)

Most medium and large employers, and a growing number of small ones, receive applications through an applicant tracking system (ATS). Workday, Greenhouse, Lever, iCIMS, SuccessFactors, Zoho Recruit and similar tools collect every application for a job in one place so a recruiter can sort, search and move candidates through stages.

"ATS-friendly" simply means your resume survives that trip intact: the software can pull out your name, contact details, jobs, dates, education and skills correctly, and a recruiter searching for the skills the role needs will find you. The good news is that the same choices that help the software also make your resume faster for a person to read.

What an ATS actually does with your resume

When you upload a resume, the ATS runs it through a parser. The parser extracts the text from your file and tries to split it into fields: contact information, work history (employer, title, dates), education, skills. Those fields fill in your candidate profile, which is what recruiters usually see first.

After that, two things matter:

• Search and filters. Recruiters search the candidate pool for terms like React, SQL or B2B sales, and filter by things like location or years of experience. If a skill is not written in your resume, you will not appear in that search.
• Knockout questions. Many applications include yes/no questions ("Are you authorised to work in India?", "Do you have a valid driving licence?"). Wrong answers can remove an application automatically. This has nothing to do with resume formatting, so read those questions carefully.

Some systems also show a "match" score comparing your profile with the job description. These scores vary a lot between vendors, and recruiters treat them as a hint, not a verdict. Your job is to make sure the parser reads everything and that the skills you really have are stated clearly.

Layout rules that keep your resume readable

Parsers read text in order, top to bottom and left to right. Anything that breaks that reading order risks scrambling your information.

Use a single column

Two-column designs look elegant, but many parsers read straight across the page, mixing a line from your sidebar with a line from your work history. A single column with clear headings is the safest choice. If you love a design-heavy resume, keep it for in-person networking and send the single-column version through job portals.

Keep text as real text

• Don't put important text inside images, icons, charts or text boxes. Parsers often skip them entirely.
• Avoid tables for layout. A simple table is sometimes read correctly, but it's a gamble you don't need to take.
• Don't place your name or contact details in the document header or footer area; some parsers ignore those regions. Put them in the body at the top of page one.
• Skip skill "bars" and star ratings. "Python ●●●●○" tells the software nothing and tells the recruiter very little.

Use standard fonts and simple bullets

Fonts like Calibri, Arial, Helvetica, Georgia, Garamond or Inter are safe. Use 10–12 pt for body text and keep your bullet characters simple (round bullets or hyphens). Unusual symbols can turn into question marks after parsing.

Write dates consistently

Pick one format and stick to it, for example Jan 2023 – Mar 2025 or 01/2023 – 03/2025. Put dates on the same line as the job title or company. Parsers use them to calculate your years of experience, and inconsistent dates are one of the most common reasons a profile shows the wrong number.

Section names and order

Parsers look for familiar headings. Creative headings like "Where I've Been" or "My Toolkit" make the software guess. Use the standard names:

A reliable order for most people is: contact details, summary, experience, projects (if relevant), education, skills, certifications. Freshers and recent graduates can move education and projects above experience; see our resume guide for freshers.

Wording: write for the search box and the reader

Name skills exactly as the job post does

If the job asks for "Microsoft Excel", write "Microsoft Excel" rather than only "spreadsheets". If it says "Node.js", don't rely on "Node". For acronyms, write both forms once: "Search Engine Optimisation (SEO)". Recruiters search for the words in the job post, so mirror them wherever they honestly describe your experience. Our guide to tailoring keywords to a job description walks through the full method.

Put skills in context, not just in a list

A skills section helps the search, but skills that also appear inside your experience bullets are far more convincing to the person who reads your resume next.

Lead with action and result

Start each bullet with a strong verb (built, reduced, launched, negotiated, automated), say what you did, and finish with the result. Numbers help a lot: time saved, money earned, users served, error rates reduced. If you can't share exact figures, approximate honestly ("about 30%") or describe scale ("for 3 regional offices").

File format and file name

• PDF or DOCX. Modern ATS platforms read text-based PDFs well, and a PDF keeps your layout identical everywhere. If a job portal specifically asks for Word, send a .docx.
• Make sure the PDF has real text. Open it and try to select a sentence with your mouse. If you can't, it's an image (often from scanning or "print to image"), and the parser will see an empty page.
• Name the file clearly: Priya-Sharma-Resume.pdf, not final_v7_NEW.pdf. Recruiters download a lot of files.
• Keep it short. One page is ideal for students and people with under about five years of experience; two pages is normal beyond that.

Three ATS myths to ignore

"75% of resumes are rejected by a robot"

This number has circulated for years without a solid public source behind it. In most companies a person still decides who moves forward. The real risk isn't a robot rejecting you; it's a recruiter never finding you in a search, or finding a garbled profile.

"Hide keywords in white text"

Pasting the job description in white text is easy to spot (the parsed profile shows all of it) and it looks dishonest. It can get your application flagged. Only list skills you can discuss in an interview.

"You need to beat a score of 100"

Different tools score differently, and no employer publishes its exact ranking rules. Use an ATS checker to catch problems such as missing sections, unreadable formatting or missing keywords, then focus on making the content strong for the person who reads it.

A checklist before you hit "Apply"

1. Single column, no text in images, tables, headers or footers.
2. Name, phone, e-mail, city and LinkedIn or portfolio link at the top of page one.
3. Standard section headings in a sensible order.
4. Consistent date format on every job and degree.
5. The job post's main skills appear in your resume, in the same words, where they are true for you.
6. Every bullet starts with a verb and most include a result.
7. Text-based PDF (or .docx if asked) with a clear file name.
8. Spelling and grammar checked, ideally by a second person.