U.S. employers want a resume, not a long academic CV. Most applications hit an applicant tracking system before a person opens the file.
If the parser cannot pull your job titles, dates, and skills into the right fields, your file sits unopened while a cleaner resume moves ahead. That is a parse problem, not a talent problem.
How do you write one file that a parser and a tired hiring manager can both use? Keep the layout simple, reuse the posting's skill names where the work is real, and put a number on what changed so someone can catch it in a few seconds.
What applicant tracking systems actually do
An ATS is hiring software that stores applications, extracts fields from your file, and lets recruiters search or filter. It is not a single product. Large U.S. employers often run Workday, Greenhouse, Lever, or iCIMS. Smaller teams may use a job-board inbox or skip software.
Jobscan reported in 2025 that 97.8% of Fortune 500 companies use an ATS. Treat that as a big-company pattern, not a rule for every shop with five people.
Thing is, ATS-friendly mostly means readable. The parser looks for ordinary headings, a work history it can split into jobs, and words that line up with the requisition. Columns and icons still break that. A high keyword score will not save a page a human cannot scan.
Build the resume in this order
Work from one live posting. A generic master file is a draft, not the version you submit.
- Dump every job, project, tool, and metric you can prove into a working doc you will never send.
- Paste the job description into plain text and highlight required skills, titles, software, and licenses.
- Use reverse chronological order unless you have almost no work in the field.
- Write a short summary that names the target role and one or two proof points.
- Rebuild each relevant job with 3 to 5 bullets that start with a verb and end with a result.
- Add a skills list that uses the employer's wording where that wording is honest.
- Export a .docx or a text-based PDF, name the file with your name, and test the parse.
Clone that version for the next posting. Don't keep editing the same generic PDF.
Formats that parse cleanly
School career offices still push a clean, dated work history. Harvard's resume guidance wants a page that reflects skills the employer would actually value, not a collage of everything you have ever done.
| Format | How it reads | Use it when | Skip it when |
|---|---|---|---|
| Reverse chronological | Newest job first under Experience or Work Experience | Your path already looks like the posting | Your recent titles have nothing to do with the role |
| Combination (hybrid) | A short skills or projects block, then dated jobs | You are changing fields or mixing contract work | You bury dates until the timeline disappears |
| Functional | Skill clusters with weak or missing dates | Almost never for a U.S. corporate ATS | The company filters on titles and dates |
Stay in one column. Label sections Experience, Education, and Skills. Jobscan's layout notes flag tables, columns, graphics, and text parked only in headers or footers, because parsers often skip those zones.
Pull keywords from the job posting
You copy the posting into a text file and you highlight every tool, certificate, and job title they used, and then you check your draft to see whether those same phrases appear in a way you can defend on a call, which is slower than blasting a master PDF but it is the part that actually gets you past a filter.
If they wrote Salesforce and pipeline reviews, write those phrases. Don't swap in a cousin word the system may not map.
Job titles count as keywords. U.S. News career advice points out that a vague internal title can take a clearer parenthetical if it still describes the work. Lying about the title is a different problem.
Repeat a must-have skill in the summary, the skills list, and one bullet when you truly used it. Once is easy to miss. A paragraph of leadership, communication, and teamwork helps nobody.
Thin posting? O*NET shows how U.S. labor data describes the occupation. Use it to fill language gaps. Don't use it to invent a year of Python.
Some scanners publish match scores. Vendor writeups often tell people to land around 75-80%, not a perfect 100. Chasing every noun makes the page unreadable. Keep the required skills you can talk about in an interview.
Bullet points that show impact
A bullet that only restates the job description is dead weight. Hiring teams want evidence.
Harvard's examples lean on results: membership up 20%, a class taught to a defined group, process work that changed an outcome. University of Utah career services uses the same pattern, such as increasing social media engagement by 30%.
Run every line you keep through this checklist:
- Start with a past-tense verb: led, built, reduced, shipped, trained.
- Name the scope: team size, accounts, tickets, budget, sites.
- Add a metric if you have one: percent, dollars, time, error rate.
- Mention the tool only if the posting cares: SQL, AWS, HubSpot, OSHA.
- Cut filler adjectives. Dynamic and results-driven waste the scan.
Weak: Responsible for customer support and handling tickets. Stronger: Resolved 40-plus Slack and email tickets a day and lifted CSAT from 4.1 to 4.6 in two quarters.
No clean percent? Use frequency, scale, or a before/after you can prove. Don't invent a 27% lift.
Contact line, summary, skills, and education
Put your name, city and state, phone, email, and LinkedIn in the body, not inside a banner graphic. Utah's student guide suggests a simple LinkedIn slug and a file name built from your name. Skip a full street address. It eats space and nobody mails you.
The summary is not a memoir. Three or four lines. Name the target job, the years, and one proof point. "Operations coordinator with 6 years in last-mile logistics. Cut late deliveries 18% by rebuilding the carrier scorecard in Excel and Slack." Early-career version: degree, tools, and a project result.
Skills stay short and honest. Match the posting's spelling. JavaScript is not JS if they wrote JavaScript. Split a long list into labeled lines (cloud, analytics, languages) so it still reads as text, not a sidebar.
Education sits below experience once you have real jobs. Students can lead with it. School, degree, city, graduation or expected date. GPA is optional; keep it when it is strong. Coursework only helps when it maps to the posting. Required licenses and clearances get their own short block. Don't bury a must-have license in a paragraph.
Remote work, career changes, and first jobs
Remote postings still parse like other jobs. If the role is remote, say it on the title line: Customer Support Specialist (Remote). Then prove the work style. "Ran daily standups in Zoom and logged bugs in Jira for a distributed team of 12" beats "comfortable with remote work."
Career changers should not hide the old job. Keep the dates. Translate the work. A store lead who wants operations can talk about scheduling, shrinkage, and vendor SLAs. To be honest, you will rewrite the same retail bullet four times, and that dated job with translated metrics still beats a skills cloud with no timeline.
First jobs live on internships, campus work, projects, and volunteer shifts. One project with a metric beats six vague clubs. "Built a Python script that cleaned 12,000 survey rows for a campus lab" is a job bullet. "Member of coding club" is not.
Freelancers can list clients or project types as jobs, with dates. Put a portfolio URL in the contact line as plain text. Five strong projects beat a 10-page dump.
Files, fonts, and a parser test
Use Arial, Calibri, Georgia, or another common font at 10-12 points. Jobscan's template guidance warns that custom fonts may not exist inside ATS software. One-inch margins and 1.0 to 1.15 line spacing keep the page from looking sparse or cramped. Utah's layout advice still holds.
Submit .docx or a real text PDF unless the posting names a format. Image PDFs fail. Pages, InDesign, and Canva files with text locked in pictures fail. Two pages is fine for a long career. One page is enough early on. Don't pad with 8-point type.
Turns out a lot of so-called ATS rejections are unreadable files. Paste the resume into Notepad or any plain text box. If the order explodes in plain text, the order will explode in the ATS too. Scanners such as Jobscan are useful as a missing-skill check, not as a score you must max out.
Name the file like Jane_Doe_Resume_Acme.docx. Recruiters download dozens of files named Resume_final_v3.
Errors that still get people screened out
Most of these are layout, not talent.
- Tables, columns, text boxes, icons, photos, and skill bars
- Contact info only in headers or footers
- Cute headings such as Where I've Made Magic instead of Experience
- Typos, broken dates, and tools you cannot discuss on a call
- A four-page career novel, or a one-page file in tiny type
- A British-style CV template with a photo, nationality, and References available on request
Lies are worse than gaps. Many systems store this file next to your next application. Inflated titles are easy to catch on a screen share.
A cover letter still earns its keep
Write one page that names the company and the role, then point to one proof already on the resume. Paid rewrite services can tidy prose, but they will not multiply interviews on their own, and you still have to tailor the next posting.
Pick one live listing tonight. Highlight eight skills you actually have. Rewrite the top third of the resume until those skills show up in the summary, the skills list, and one quantified bullet. Export a clean file, run a parse test, and submit that version instead of the generic master.