How to Write an ATS-Friendly Resume in 2026
From CVory — a free ATS résumé builder. Unwatermarked PDF, no paywall at the download.
To write an ATS-friendly resume in 2026, use a single-column layout, standard section headings (Experience, Education, Skills), a common font, and save it as a text-based .docx or PDF — then mirror the exact keywords from the job description. Applicant tracking systems like Workday, Greenhouse, Lever, Taleo, and iCIMS parse your resume into a database, and the formats Greenhouse documents as causes of a failed parse (tables, text boxes, headers/footers, graphics, multi-column designs) can drop or scramble your information before a recruiter ever sees it. The goal is not to "trick" the software but to make your real qualifications machine-readable and keyword-aligned. Below is a concrete, step-by-step approach — formatting rules, section order, keyword matching, and the file-type choice — with before/after examples you can copy.
What is an ATS and how does it actually read your resume?
An applicant tracking system (ATS) is software employers use to collect, parse, store, and filter job applications. When you upload a resume, the ATS doesn't 'look' at it the way a person does — it runs a parser that extracts your text and tries to sort it into structured fields: name, contact info, work history (employer, title, dates), education, and skills. Workday, Greenhouse, Lever, Taleo, and iCIMS each do this slightly differently, but the parsing step is universal, and it's where most resumes quietly fail.
A common myth is that ATS software auto-rejects resumes that score below some hidden threshold. Greenhouse — one of the largest systems — states flatly that it 'never uses AI to rate candidates or auto-reject applications.' Recruiters instead search and filter the parsed database (for example, searching 'Salesforce administrator' + 'Atlanta'); Greenhouse describes recruiters using its 'filtering and search capabilities' to narrow a large applicant pool. If parsing mangled your job titles or your skills never made it into the database, you simply don't appear in those searches. So 'ATS-friendly' really means 'cleanly parseable and keyword-aligned,' not 'beat a robot gatekeeper.'
Knowing this changes your priorities: clean structure that parses correctly matters more than clever design, and the words you use must overlap with the words recruiters search for — which come straight from the job description.
- Parse: extract text and assign it to fields (name, title, dates, skills).
- Store: save the structured data to a searchable database.
- Search/filter: recruiters query by title, skills, location, keywords.
- Rank (some systems): score candidates by keyword and criteria match.
What formatting makes a resume ATS-friendly?
The safest ATS format is a single-column layout, left-aligned, with standard fonts (Calibri, Arial, Georgia, Helvetica, or Times New Roman at 10–12pt), simple bullet points, and clear text headings — and no tables, text boxes, columns, sidebars, images, icons, logos, or charts. This is not folklore: Greenhouse's support documentation lists 'resumes that have a columned layout', 'complex resumes with tables, headers, and footers', and 'resumes that include graphics, photos, or word art' among the things that cause an unsuccessful parse. The usual failure mode is a two-column layout being read straight across, interleaving your skills sidebar into the middle of a job description.
Keep your contact information in the main body, not in the document header or footer. Greenhouse names 'resumes with the name and contact information in the header, footer, or text box' as a cause of an unsuccessful parse. A correction to an earlier version of this guide: we used to say that older Taleo configurations ignore header and footer text. Oracle's own Taleo documentation says the opposite — its resume parsing 'can detect text in the header and footer' — so we have dropped that claim. The advice itself stands, for a better reason: header placement is a documented parsing risk in at least one major system and gains you nothing, so the body is simply the safer place.
Use real bullet characters (• or -) rather than images of bullets, and write dates in a consistent, parseable format like 'Jan 2023 – Present' or '01/2023 – Present.' Avoid fancy date ranges, em-dash-only separators with no spaces, or putting dates in a separate column. If you use a builder, choose a template flagged as ATS-safe; CVory's editor, for instance, marks designer (multi-column) templates and warns that they lower your ATS score for exactly this reason.
- Do: single column, standard fonts, text headings, real bullets, body-text contact info.
- Don't: tables, text boxes, columns, sidebars, images, icons, charts, header/footer contact info.
- Don't: rely on color or shapes to convey meaning — parsers see only text.
- Do: keep one consistent date format throughout.
What sections should an ATS resume include, and in what order?
An ATS-friendly resume should include these sections with standard, literal headings: Contact Information (top, in the body), a short Summary (optional), Skills, Work Experience, and Education — typically in reverse-chronological order, most recent first. Parsers are trained to recognize conventional headings, so 'Work Experience' or 'Experience' is detected reliably while creative labels like 'My Journey' or 'Where I've Made an Impact' may be missed, causing that whole block to be misfiled or dropped.
For each role, lead with a clear, recognizable job title, then the company, location, and dates — and keep the title standard. If your internal title was 'Growth Ninja,' write 'Marketing Manager (Growth)' so a recruiter searching for 'marketing manager' finds you. Under each role, use 4–6 achievement bullets that start with a strong verb and include a metric where possible.
List hard skills in a dedicated Skills section using the exact terms from the job posting (e.g., 'Python,' 'Google Analytics 4,' 'SOC 2,' 'Figma'), and also work them naturally into your experience bullets. Skills that appear in context (proving you used the tool) carry more weight with recruiters than a bare keyword list, so do both.
- Contact Information (name, phone, email, city/state, LinkedIn) — in the body.
- Summary (2–3 lines, optional) — front-load your strongest keywords.
- Skills — exact hard-skill terms from the job description.
- Work Experience — reverse-chronological, title → company → dates → bullets.
- Education — degree, institution, graduation year (drop GPA if dated or low).
How do you add keywords without keyword stuffing?
Add keywords by mirroring the specific nouns and tool names from the job description in the natural flow of your skills and experience — aim to cover the role's must-have terms once or twice each, in context, rather than repeating them. It is widely claimed that modern parsers do contextual and synonym matching on your behalf; we could not find vendor documentation promising it, so treat it as unproven. What Greenhouse does document is AI that 'automatically suggests search terms that are relevant to the role' — help for the recruiter's search, not for your wording. Recruiters still run literal keyword searches, so using the posting's exact phrasing ('accounts payable,' 'CI/CD,' 'stakeholder management') is what gets you surfaced.
Keyword stuffing — pasting a hidden block of terms in white text, or cramming the same word ten times — is both detectable and counterproductive. Recruiters read the resume after the search, and an obviously stuffed document reads as dishonest. Worse, white-on-white text is a well-known trick that many recruiters and systems flag. Coverage and relevance beat repetition.
A reliable method: paste the job description and your resume into a keyword-gap tool to see which required terms you're missing, then add only the ones you can truthfully back up with experience. CVory's keyword-gap feature does this against a pasted job description so you add real, supportable terms — not filler. Before/after example: Before — 'Responsible for the sales pipeline.' After — 'Managed a $2.4M sales pipeline in Salesforce, improving forecast accuracy 18% over two quarters.' The 'after' adds the searched tool (Salesforce), a metric, and the searchable concept (sales pipeline) in context.
- Mirror exact terms from the posting (tools, certifications, methodologies).
- Use each key term once or twice, in context — not a repeated wall of words.
- Never use hidden/white text — it's flagged and reads as dishonest.
- Only add keywords you can defend in an interview.
Score your résumé against any job — free
Paste your résumé into CVory's ATS checker and see exactly which keywords you're missing.
Should you submit a PDF or Word document to an ATS?
Submit a text-based PDF or a .docx — both parse well in modern systems as long as the text is selectable. Greenhouse accepts .doc, .docx, .pdf, .rtf and .txt; iCIMS lists .pdf, .doc and .docx among the formats it extracts text from. The real failure mode isn't the extension; it's an image-only PDF. Oracle states it plainly for Taleo: 'the resume will not be parsed when it is in an image format.' If your PDF was exported as a rasterized image (some design tools and 'WYSIWYG screenshot' exports do this), the parser sees a picture with zero extractable text and stores a blank record.
Test it in five seconds: open your PDF, try to highlight a sentence and copy it into a text editor. If the text comes through cleanly, it's parseable. If you can't select any text, or it pastes as gibberish, it's an image — re-export it as true text or use .docx instead. When in doubt, or when the application portal specifically requests Word, use .docx, which is always text-based.
Also avoid 'creative' file gimmicks: don't submit a multi-page design PDF where the resume is one big graphic, and don't password-protect or compress the file in a way that blocks extraction. Name the file clearly (e.g., 'Jane-Doe-Resume.pdf') since some systems display the filename to recruiters.
- Both .docx and text-based PDF parse well — selectable text is what matters.
- Image-only/rasterized PDFs parse as blank — always test by selecting text.
- Use .docx if the portal asks for Word or you're unsure.
- Avoid password protection, heavy compression, and design-as-image exports.
- Watch the file size, but check whose limit applies: Oracle documents that a Taleo resume 'cannot exceed 100 kilobytes or the size defined by the system administrator' — a configurable default rather than a universal cap — while Greenhouse accepts uploads up to 100 MB and lists a file that is too large (over 2.5 MB) as a parse failure. A photo-heavy export can still exceed whatever limit a given employer has set.
How do you test whether your resume is actually ATS-friendly?
Test your resume by checking three things: (1) can you select and copy all its text, (2) does a parser correctly read your name, titles, dates, and skills, and (3) do you cover the specific job's required keywords. The copy-paste test catches image-only files; an ATS checker simulates parsing and flags layout problems; and a keyword-gap comparison against the target posting shows whether you'll surface in recruiter searches.
A practical workflow before each application: paste the job description, run your resume through an ATS checker to confirm structure and formatting pass, review the keyword gap, and add any missing supportable terms. CVory offers a free ATS checker at /ats-resume-checker plus a real-time ATS score in the editor that updates as you type, including a layout check that flags multi-column templates — useful for catching the parsing risks above before you submit, not after a silent rejection.
Finally, sanity-check by reading the resume yourself: clean structure should serve a human too. If a recruiter can scan your titles, dates, and top achievements in 10 seconds, a parser almost certainly can as well.
- Copy-paste test: select all text — if you can't, it's an image, not text.
- ATS checker: confirms headings, layout, and contact info parse correctly.
- Keyword-gap check: compare your resume to the exact job description.
- Human scan test: titles, dates, and wins readable in ~10 seconds.
Frequently asked questions
Do ATS systems automatically reject resumes?
Mostly no. Greenhouse states that it 'never uses AI to rate candidates or auto-reject applications', and describes recruiters searching and filtering the parsed database themselves. The one real automatic rejection is a rule a recruiter configures on an application question — Greenhouse's own example is rejecting applicants who lack a required commercial driver's licence. If parsing scrambled your data or your keywords are missing, you won't appear in recruiter searches, which feels like rejection but is really an invisibility problem you can fix with clean formatting and matching terms.
Are multi-column resume templates ATS-friendly?
Generally no. Two-column and sidebar layouts are the most common parsing failure: many ATS parsers read across columns left-to-right, interleaving your skills sidebar into job descriptions and scrambling the result. Use a single-column layout. If you want some visual polish, keep it within one column using bold, spacing, and a single accent color rather than tables or side panels.
Is a PDF or Word document better for an ATS?
Both work in modern systems as long as the text is selectable. The deciding factor isn't the extension — it's whether the file is text-based or an image. Test by trying to highlight and copy your resume text; if you can't, it's a rasterized image that parses as blank. Use .docx if a portal specifically asks for Word or you're unsure about your PDF.
How many keywords should I put on my resume?
Focus on coverage, not count. Identify the must-have terms in the job description — tools, certifications, methodologies, the exact job title — and include each once or twice in context across your skills and experience. There's no magic number. Relevance and truthful, in-context usage beat repetition, and stuffing the same word repeatedly looks dishonest to the recruiter who reads it after searching.
Should I put my contact info in the header of the document?
No. Place your name, phone, email, and location in the main body at the top, not in the Word header or footer. Greenhouse lists a resume 'with the name and contact information in the header, footer, or text box' as a cause of an unsuccessful parse. We have corrected one detail here: this guide used to say older Taleo configurations ignore header content, but Oracle documents that Taleo parsing 'can detect text in the header and footer'. Body placement costs you nothing and removes a risk that is documented in at least one major system.
Does hidden white keyword text help beat the ATS?
No — avoid it. Pasting keywords in white-on-white text is a well-known trick that many recruiters and systems detect, and it reads as dishonest the moment a human opens the file. Recruiters review resumes after searching the database, so any deception is visible. Add only keywords you can genuinely support, written in normal, readable text.
How do I check if my resume is ATS-friendly before applying?
Run three quick tests: select-and-copy the text to confirm it isn't an image, run it through an ATS checker to verify headings and layout parse correctly, and compare it against the specific job description for keyword gaps. CVory's free checker at /ats-resume-checker and its real-time ATS score do this, including flagging multi-column layouts that commonly break parsing.
Sources
Primary sources for the factual claims above — vendor documentation, official government guidance, and named studies. Sources last checked 2026-09-16.
- Unsuccessful resume parse — Greenhouse Support, updated 2 March 2026
- Supported formats for resumes, cover letters and other candidate uploads — Greenhouse Support, updated 19 August 2026
- How does Greenhouse use AI? Here's everything candidates need to know — Greenhouse, 8 January 2025
- What really happens after you apply for a job — Greenhouse, 8 January 2025
- Auto-reject — Greenhouse Support
- Taleo Enterprise: Candidate Management (resume parsing, supported formats and size limit) — Oracle
- Taleo Business Edition: Resumes in Image Formats — Oracle
- Binary Files (formats available for text extraction) — iCIMS Developer Resources