Most big U.S. employers don't hand your resume to a human first. Their applicant tracking system chews the file down into fields: name, titles, dates, skills. A recruiter searches those fields later. If the parse fails, you never show up in the results.
That's the whole problem in four sentences. The University of Iowa Career Services team puts a number on it: 99% of Fortune 500 organizations run ATS software. Smaller companies join the party the moment they post on a job board, a campus platform, or their own hiring tool.
Can a plain one-page file really decide whether you get a callback? Often, yes. The machine reading your file first has no idea what to do with a two-column design, a graphic header, or a clever section title. None of that maps to the fields a recruiter searches. You're still writing for a person, and that work matters more than the design ever did.
So your actual task stays boring: simple layout, predictable section names, bullets tied to the posting in the employer's own wording. That's it.
What an ATS actually does with your resume
An applicant tracking system is hiring software. It holds the job posting, the applications, and a parsed copy of your file in one place.
The parser's job is splitting your page into fields: contact info, work history, education, skills. Recruiters then search those fields. They don't sit down and read every PDF like a magazine spread, and pretending otherwise costs you interviews.
Thing is, a polished Canva layout can look sharp on your laptop and still scramble your dates or glue a job title onto the company above it. Nobody catches the mistake, because nobody ever sees your original file next to the parsed version.
Guides that dig into how Greenhouse reads resumes land on two rules nobody brags about at parties. Spell out titles instead of shortening them to "Sr.", and give company names a legal cue such as Inc., Co., Ltd, or LLC when that's the real name. Greenhouse turns up all over U.S. startups and mid-size tech firms. Workday-style systems run at the larger employers. Either way the layout advice barely changes. Skip tables for your work history, skip icons, skip text trapped in images. One column of real text is what the software can lift.
Formats that survive both bots and humans
Skip the hunt for a unique template. You want readable.
| Format | How it reads in ATS | How it reads to people | Use it when |
|---|---|---|---|
| Reverse chronological | Usually the cleanest parse | Shows growth in order | Your jobs already point at the role |
| Hybrid (skills, then chronology) | Fine if headings stay standard | Lets you lead with transferable skills | You're changing fields or returning after a gap |
| Functional / skills-only | Easy to mis-parse | Recruiters often distrust it | Almost never, except a short skills block on top of real jobs |
A Harvard-style page parses well because it's single-column and text-first, not because a school logo is hiding inside the file. Vendor writeups that score that layout keep repeating one point: once the file is parseable, your content sets the ceiling.
On length. Stay on one page if the relevant story fits. Two pages can make sense for a long senior career. Padding a second page with old duties just waters down the good material.
Work through this before you rewrite a line
- Paste the job posting into a plain document and highlight 10 to 15 phrases the employer repeated: tools, methods, credentials, outcomes.
- List your proof next to each phrase. A class project counts if you have no job yet.
- Pick reverse chronological or hybrid. Don't invent a third structure.
- Draft a 3-4 line summary that names the target role and one result, not a personality slogan.
- Rewrite every bullet as verb plus work plus result.
- Put the same keywords in Skills and in the bullets where you truly used them.
- Export a .docx or a simple text-based PDF, then upload it to the board or ATS named in the posting (Handshake, a company Greenhouse portal, LinkedIn Easy Apply, or the career site).
That sequence beats decorating first. Design is the last pass.
Bullet points that carry the hire
Duties are cheap. Outcomes get interviews. That's the section in six words, but the formulas behind it deserve a closer look.
Yale's formula is blunt. Pick an action verb for what you did. Name the project or the problem. State the result, with a number when you have one. Write it as your contribution, not the team's.
University of Iowa Career Services teaches the same spine: power verb, what you did, then the outcome. If a line still feels empty, they say to add who, what, when, where, why, or how.
Turns out, campus examples already sound like strong job-search copy. The Harvard College resume guide shows a membership drive that produced a 20% increase in the group and a 15% lift in social engagement. Another line has a student designing classes for 10 fifth graders and leading daily trips. No famous employer required for that structure.
UT Dallas puts numbers right up front: 20%, 50+, over 100, $1M. One rewritten sales line goes from a vague duty to exceeding sales targets by 15% through stronger customer conversations. A crew example names 20 people and production gains across 3 quarters.
UT Austin has a campus promo set that drew 500 attendees and raised more than $10,000. They also warn you off insider acronyms a recruiter outside your school won't recognize.
Over at University of San Francisco Career Services, the result is the line that answers why anyone should care. Their club example: a homepage and email list that produced a 20% jump in event participation.
Now put the two versions side by side. "Responsible for inventory" against "Collaborated with the warehouse team to cut stockouts 18% during peak season." Same job, and only one of them earns a second look. If you lack a perfect percentage, count the volume instead. Tickets closed. Students taught. Budget watched. Clients served.
University of Oregon points at those same indicators: clients, growth, donations, satisfaction. Not every task you ever did belongs on the page. Look at the posting and keep the proof that matches it.
Tailor to the posting without stuffing
Open the description and steal the nouns they already chose.
If they wrote "agile workflow," write "agile workflow" in a bullet where you actually used it. Don't reach for a clever synonym the parser may never map. Don't paste the whole qualifications block into Skills either. That's stuffing, and humans still read the file after the sort.
Why does the exact phrase matter so much? Because the search box on the recruiter side is usually looking for the words they typed into the requisition. Your fancier thesaurus version sounds more executive and matches nothing. Same meaning, zero hits.
Match tools and methods first. Soft claims like "team player" are weak tokens in most parsers and weaker still on the page. Put collaboration inside a result instead: you coordinated five interns, held a budget, and finished two weeks early. Yale has a line like that for a reason.
Gig and freelance work belongs here too. Name the project, the stack, the metric. "Managed remote campaigns" is thin. "Ran paid campaigns for 3 clients, 50,000 monthly visits, 12% lift in signups" is a job.
Headings and sections the parser expects
Stick to names the software already knows:
- Contact
- Summary or Profile
- Skills
- Experience
- Education
- Optional: Projects, Certifications, Volunteer
Contact info stays boring on purpose: name, phone, city and state, email, LinkedIn, portfolio. No photo. No full street address. No salary history.
Summaries work best short. A career-changer version can name the past strength and the target field in one breath. An entry-level version leads with a major or core skill, one proof line, then the role you want. Harvard reminds you that not every past job has to match. The page should still reflect skills the employer would value.
For Skills, keep a scannable list of 8-12 items, biased toward the posting. Then repeat the important ones inside bullets so they carry context. A lonely keyword with no proof is easy to ignore.
Education can sit high if you're a student or recent grad. Move it down once jobs tell a stronger story. GPA is optional; Harvard's sample uses 3.6 when it's a real asset.
Layout, files, and errors that dump you from the stack
Two-column templates, skill bars, and headers baked into images are the usual parse wrecks. Tables used as a design grid fail the same way. People will sink a whole weekend into icons and give the bullets five minutes, which is exactly backwards.
Save as .docx, or as a PDF produced from Word or Google Docs. Never from a design tool that draws letters as graphics. Greenhouse-oriented guides list PDF, DOCX, DOC, RTF, and TXT as accepted upload types, and they still tell people to avoid design-tool PDFs with columns or embedded graphics.
One common font. Headings slightly larger than body text. Normal margins. Hyperlink LinkedIn and your portfolio as real text, not icons.
Raw chatbot output doesn't belong in your summary. It reads generic, and generic loses. Edit until it sounds like you describing work you actually did. Leave salary off completely. The resume shows skills and results, not pay history.
Then test the file the ugly way. Upload it to the real portal and open the parsed preview if the ATS shows one. Read it top to bottom. If titles or dates jumped fields, fix the layout. Don't add more color.
Entry-level, career changes, layoffs, and remote jobs
No experience is not "no proof." Lead with projects, labs, campus jobs, and quantified extras. Harvard's classroom example works because it has a headcount and a daily rhythm. A GitHub repo, a student org budget, or a retail close-out shift can take the same shape.
Career changers do better with a hybrid page: tight summary, skills block mapped to the new field, then jobs that show the transfer. Dates and employers stay visible. Hiding the timeline in a functional format makes recruiters suspicious, and suspicious recruiters just move on to the next file.
If you just got laid off and you're staring at a blank page, the urge to explain the gap, defend the company, and list every duty you ever covered is completely understandable, because you don't want to look idle, and yet that impulse usually makes the resume longer and vaguer instead of sharper, which is the opposite of what a stressed job seeker needs right now. Skip the blame. Keep the dates honest. Push the work that still matches the posting, especially tools and results you can reuse.
Remote and hybrid postings reward proof of distributed work. Name the tools only if you used them, then attach a result: a team across time zones, an async standup, a documentation habit that cut rework. "Open to remote" in the summary is fine. It is not a substitute for a bullet.
Gig and contract history can look like jobs. Title, client or platform, dates, three result bullets. Don't bury paid work under a hobby header.
Resume tools, job boards, and ATS portals in one workflow
The file you just built has to travel. U.S. applications usually pass through a job board, a campus system, or a company ATS, and sometimes all three for the same role.
Handshake is the common campus path. Iowa even publishes upload steps. Treat Handshake like any other parser: standard headings, no graphics, then a complete profile that repeats your best keywords.
LinkedIn isn't a second resume with different facts. Mirror titles, dates, and core skills so a recruiter who clicks through from your PDF doesn't hit a mismatch. The About section can run longer. The resume stays tight.
Easy Apply still sends a file that gets parsed, so use the same clean resume you'd upload on a career site. Don't keep a "pretty" version and an "ATS" version with different job titles. One source of truth.
Company portals vary. Greenhouse shows up a lot in tech and mid-market hiring. Larger firms often run Workday or something similar. You can't control their software. You can control a single-column file and titles written in full.
Resume scanners and "ATS score" extensions can catch missing phrases. They can't promise an interview. Use one as a checklist against a single posting, then stop tweaking synonyms.
To be honest, most people lose more callbacks to a messy parse and empty bullets than to a missing buzzword on line 40.
Resume vs cover letter, in the same packet
| Resume | Cover letter | |
|---|---|---|
| Job | Parsed facts and proof | Why this team, in sentences |
| Length | One page for most people | About half a page |
| Keywords | In headings, skills, and bullets | A few, used naturally |
| File | .docx or clean PDF | Often a text box in the ATS, sometimes a second PDF |
The resume gets you past the filter. The letter is optional at many U.S. employers, and still worth writing when the posting asks for one or when you need to explain a change in direction in two short paragraphs.
FAQ
How long should a U.S. resume be? One page is the default for students, career changers, and most individual contributors. Two pages only if the extra space holds senior, relevant work. Recruiters skim, and empty lines of duties don't survive skimming.
What keywords should I add? The ones in the posting. Copy the tools, methods, and credentials you actually have. Technical terms go in Skills and again in a bullet that proves use.
How do I write a resume with no job history? Hybrid layout. Education, projects, and campus work first. Quantify what you can: people taught, dollars raised, bugs closed, shifts covered.
Should salary history go on the resume? No. Compensation talk waits for later stages, and only if the employer asks.
Do I need a special file for Greenhouse or Handshake? You need a parseable file, not a branded template. .docx or a simple PDF, full job titles, real company names, and standard headings.
Open tonight's target posting, highlight 10 phrases, and rewrite three bullets so each one carries a verb, a task, and a number. Export a single-column PDF or Word file and upload it in the same system the employer named.