11 min read
You've sent twenty applications and heard nothing back. The file looks sharp on your screen, but you're not sure a Workday or Greenhouse upload is reading the same words you see. That gap. between what you designed and what the parser extracts. is where most qualified people lose visibility before a recruiter ever opens the attachment.
This guide walks you through building a resume that gets past ATS filters without gimmicks. Before you tailor the next posting, check your resume for free against the job description, then follow the steps below for layout, headings, keywords, and bullets. For file-type specifics, start with which ATS-friendly template to use in 2026 . this page is the build sequence.
You don't need a separate product or a secret keyword list. You need a boring, accurate file that machines can read and humans can skim in ten seconds. That's the whole job.
Quick Wins
- Paste your resume into Notepad. If dates or employers scramble, fix layout before you apply again.
- Rename one experience heading to Work Experience and confirm Education and Skills use the same capitalization.
- Highlight three must-have nouns from the posting and Ctrl-F your file to see if they appear inside dated bullets.
What ATS filtering actually is (and what it isn't)
An applicant tracking system is software employers use to collect applications, parse resumes into structured fields, and help recruiters search and sort candidates. Workday, Greenhouse, Lever, Taleo, and iCIMS all do this differently, but the first gate is usually the same: can the system read your file and map your experience into rows a recruiter can filter?
ATS filtering is automated parsing plus employer-configured search and eligibility rules. Not a single magic score that automatically hires or rejects everyone who falls below a number.
This is not a reason to stuff keywords into a footer. Parsers look for structure first: contact block, experience with dates, education, skills. Recruiters then search for terms that match the posting. A file that parses cleanly but says nothing specific about the role still loses to someone who wrote boring, honest evidence.
I've screened stacks of these, and the resume that gets past ATS filters is almost always plain. Single column. Standard headings. Month-and-year dates. Bullets that name a tool, a scope, and something measurable you can defend in an interview.
What ATS filtering is not: a single universal rejection script, a reason to lie about titles, or permission to paste the job description into a footer. Employers configure systems differently. A hospital, a retailer, and a software company can all use Workday with different questions and search habits. Your job is to submit a file that extracts cleanly and states honest facts recruiters can verify.
Greenhouse and Lever often show recruiters a parsed profile beside the PDF. Taleo and iCIMS may lean harder on structured fields during application. The common thread: if the parser cannot map your experience into rows, search and filters work against you even when a human eventually opens the attachment.
Step-by-step: build a resume that gets past ATS filters
Step 1: Pass the plain-text paste test
Open your resume, select all, copy, and paste into Notepad or TextEdit. Read top to bottom. If your name lands beside a job title from 2018, or if a sidebar phone number disappears, the ATS will struggle too. Fix the source file. remove text boxes, merge columns, and export a text-based PDF from Word or Google Docs.
Save the file as Firstname_Lastname_Resume.pdf. Avoid special characters in the filename. If the posting asks for DOCX, keep a .docx master and export PDF only when allowed.
Step 2: Lock in headings parsers recognize
Use Work Experience (or Professional Experience), Education, and Skills. Skip creative labels like My Journey or Core Competencies. parsers and recruiters both map faster when headings match what they expect. Put experience near the top for mid-career applicants; new grads can lead with Education when it is the strongest proof.
Each job block needs employer, title, city and state if you include location, and start and end dates as Month Year. Write Present for current roles. Do not hide months unless you are prepared to explain gaps in an interview.
Step 3: Pull honest keywords from the posting
Open the job description. Highlight three required tools, methods, or credentials you actually have. Mirror the exact wording when it is truthful. If the posting says financial analysis, do not rely only on business reporting in your bullets. Place each term inside a dated line under the employer where you used it.
Posting term: Salesforce case management
Weak bullet: Handled customer issues.
Strong bullet: Resolved billing and access cases in Salesforce across phone and email queues while meeting documented response targets.
Repeat for a second composite role. A registered nurse posting that asks for Epic documentation might rewrite Nurse duties at hospital to Registered Nurse, medical-surgical unit. documented assessments and medication administration in Epic per hospital policy.
Step 4: Rewrite bullets recruiters and parsers both read
Take a mid-level analyst who still writes Responsible for weekly reports. ATS imports that vague line exactly. Rewrite it:
Before: Responsible for reports.
After: Built weekly inventory variance reports in Excel and Power BI for six regional managers, reducing manual reconciliation time.
Before: Helped with projects.
After: Coordinated cross-functional rollout of a CRM migration, tracking milestones in Jira for a 12-person implementation team.
Use frequency, volume, or audience when you do not have a percentage. Never invent metrics. Specific language gives parsers nouns to index and gives recruiters a reason to call.
Step 5: Tailor the top third for each application
Keep a master resume. For each role you care about, save a copy named with the company and date. Change the summary or headline line to include the exact job title. Reorder three bullets under your current job so the first bullet mentions a must-have from the posting. That is enough tailoring for most corporate applications. you do not need to rewrite ten years of history every time.
If the posting lists a certification you hold, put the full name in a certification line and once in a bullet. Spell out acronyms on first use: Customer Relationship Management (CRM).
Keep contact information in the document body, not in a header or footer that parsers drop. One email, one phone, city and state if you include location. LinkedIn URL as plain text is fine when your profile matches the resume. mismatched headlines create doubt during recruiter notes.
For senior roles with ten-plus years, two pages is normal. For early career, one page of dense evidence beats two pages of high school clubs. Cut roles older than ten to fifteen years unless they carry a credential the posting requires.
Edge case: career change with a title mismatch
When your last title does not match the role you want, lead with a one-line summary that names the target function and anchor proof from projects, internships, or volunteer work. Do not change employer titles. add context instead. A teacher moving into corporate training might write: Instructional designer. built LMS modules in Articulate for 200+ staff across four departments under a relevant contract or internal project heading.
For overlapping contract and full-time work, list both with honest dates rather than hiding overlap. Parsers flag impossible timelines; recruiters flag trust problems.
Edge case: NDA clients and internal codenames
You can describe scope without naming the client: Fortune 500 financial services client or Series B SaaS company. Keep tools and outcomes specific. Vague secrecy reads like padding. If you truly cannot describe the work, focus bullets on methods and scale you can discuss.
Copy-paste summary block for your next edit session
Open your resume and the posting side by side. Use this checklist before you save the tailored export:
- Paste test passed. contact info, employers, and dates in logical order.
- Headings: Work Experience, Education, Skills. same capitalization throughout.
- Every role has Month Year start and end (or Present).
- Three posting must-haves appear inside dated bullets, not a keyword footer.
- File name: Firstname_Lastname_Resume.pdf (or DOCX if required).
A third composite pattern for customer support roles: swap Answered phones for Resolved tier-one billing and access tickets in Zendesk across chat and email queues, documenting cases per SLA guidelines when the posting names Zendesk and SLA management.
For more on keyword placement, read what keywords ATS tools look for and how to beat an ATS system .
Common mistakes that fail ATS filters
Using a two-column Canva template. Sidebars push contact info and skills out of reading order. Parsers merge columns into nonsense. Switch to a single-column Word or Docs layout.
Stuffing a Skills footer with every tool on the posting. Lists without dated proof create interview risk. Put tools you have used in bullets; keep the skills section short and honest.
Uploading the same generic file everywhere. A master resume is fine; a single unchanged upload for every industry is not. Swap the summary line and three bullets when the posting changes.
Relying on icons, charts, or skill bars. Visual ratings do not parse. Replace them with text proficiencies or drop them entirely.
Skipping the re-check after edits. One formatting fix can break another section. Run the paste test again after every major change.
Applying on mobile without reviewing the export. Tailoring on a phone is fine for quick edits; final export and paste-test on a laptop catches layout issues small screens hide.
Check the file before you apply
Building a resume that gets past ATS filters starts with a diagnostic, not guesswork. Upload your file to HireFlow's free ATS resume checker with the job description you plan to submit. Look for parsing warnings, missing sections, and gaps between posting language and your dated bullets.
Use the score as a checklist, not a hiring promise. Fix structure first, then keywords, then one bullet at a time. When a posting asks for a cover letter, draft one with the free cover letter generator and verify every fact matches the resume.
Read how to check resume ATS compatibility free for paste-test and gridline checks you can run locally in five minutes.
Build a file machines and humans both read
A resume that gets past ATS filters is not flashy. It is accurate, single-column, and full of dated proof. Fix parsing first, then tailor the top third for each posting, then stop guessing.
- Paste-test before every batch of applications.
- Standard headings and Month Year dates on every role.
- Honest posting terms inside bullets you can defend in an interview.
Open your master file, run the free resume check , rewrite one bullet under your current job, and save a tailored copy for the next posting. That is how you get past ATS filters without a gimmick.
Read more
Frequently asked questions
Text-based PDF or DOCX in a single-column layout usually parses most reliably. Avoid scanned images and design templates with tables or text boxes. Follow the posting when it specifies a format.
Place honest must-have terms inside dated bullets and a concise skills section. One clear mention in context beats repeating every synonym in a keyword block.
Often yes. Multi-column layouts and icons confuse parsers. A plain single-column file with standard headings extracts more reliably in Workday, Taleo, and iCIMS.
Yes for roles you want. Change the summary line, reorder three bullets, and mirror exact tool names when you have used them. Save a dated copy per application from your master file.
No. It shows whether your file parses and whether honest posting language appears in context. It cannot see knockout rules, referrals, or applicant volume.