Here’s a number that should bother you: on average, a recruiter spends 7.4 seconds on their first scan of your resume. Seven seconds. That’s less time than it takes to read this paragraph out loud.
And before a recruiter ever sees your resume, there’s a good chance a piece of software has already read it, scored it, and possibly rejected it. That software is called an Applicant Tracking System — ATS — and depending on which study you believe, somewhere between 75% and 99% of mid-to-large companies use one.
I’ve spent the last few years writing and reviewing hundreds of resumes for job seekers across tech, finance, healthcare, and everything in between. The pattern is always the same: it’s rarely that the person isn’t qualified. It’s that their resume gets filtered out before anyone qualified ever looks at it.
This article is the complete guide I wish every client read before we started working together. No fluff, no recycled advice. Just what actually works.
What an ATS Actually Does (It’s Not What Most People Think)
Let’s clear up a myth first, because this myth causes people to wreck perfectly good resumes.
The old advice says: “ATS robots can’t read fancy formatting, so use plain text, no columns, no nothing.” That advice is about a decade out of date.
Modern ATS platforms — Workday, Greenhouse, Lever, Taleo, iCIMS — don’t “read” your resume the way a human does. Most of them parse it. They extract data: your name, job titles, dates, employers, education. Then many of them rank you against the job description, often looking for keyword matches.
This means two things:
First, parsing failures are your biggest enemy. If the system can’t figure out where your work experience section starts, or it reads your dates in the wrong order, your resume might show up in the recruiter’s dashboard as a garbled mess — or as a blank candidate profile. It gets rejected not because of what it says, but because nobody could read it.
Second, keyword relevance still matters, but it’s not the crude “exact match or die” system it used to be. Many platforms now use semantic matching, so “managed a team” and “team leadership” can register as similar. Still, when a job posting says “project management,” and your resume says the exact phrase “project management,” you’re simply safer.
So the goal isn’t to make your resume ugly. The goal is to make it parseable and relevant while still looking good enough that when a human does open it, they’re impressed rather than confused.
The 7 Most Common Resume Mistakes That Get People Rejected
I review a lot of resumes that “feel” fine to their owners. These are the problems that come up again and again.
1. The functional resume format
You know the type — skills listed in clusters at the top, work history compressed into a bare timeline at the bottom. People use this format to hide employment gaps or career changes. Here’s the problem: recruiters know exactly what you’re doing, and most of them distrust functional resumes on sight. Many ATS platforms also struggle to match your experience to job titles when the structure is scrambled.
Use reverse-chronological format. Every time. If you have a gap, address it in your cover letter or a single honest line in your summary. Recruiters respect straightforwardness far more than they respect clever formatting.
2. Responsibilities instead of accomplishments
“Responsible for managing social media accounts.” Okay. So is every other applicant. What did you actually do with them?
The fix is a simple formula: action verb + what you did + measurable result.
Instead of: “Responsible for managing social media accounts”
Try: “Grew Instagram following from 2K to 31K in 14 months, driving a 40% increase in inbound leads”
No exact numbers? Estimate honestly, or describe scope: “Managed social media for a 3-person marketing team supporting 15 client accounts.” Scope is a number too.
3. Applying with one resume to fifty jobs
This one hurts because it’s so human. Applying to jobs is exhausting, so people blast the same resume everywhere and hope volume wins. It doesn’t — it just guarantees you’re a mediocre match for every single posting.
When a job description mentions a skill you genuinely have, that skill needs to appear on your resume in similar words. This isn’t gaming the system. If you don’t reflect the language of the role, the hiring manager has no way to know you’re a fit.
4. A summary that’s all about you
“Seeking a challenging position in a growth-oriented company where I can utilize my skills…” Stop. Every recruiter has read this sentence ten thousand times, and it says literally nothing.
Your summary — if you include one at all — should answer: who are you, what’s your strongest proof, and what do you want next? Three lines maximum. Example: “Supply chain analyst with 5 years in e-commerce logistics. Cut fulfillment costs 18% at my last company. Looking to bring that efficiency focus to a mid-size DTC brand.”
5. Creative formatting that breaks parsing
Two-column layouts, headers and footers containing critical info, tables, text boxes, icons instead of section headings. These look beautiful in a PDF viewer and parse terribly in an ATS. Keep your contact information in the document body. Use standard section headings: Experience, Education, Skills. Use a single column. You can still look polished — clean typography and good spacing do more for a resume’s appearance than any layout trick.
6. Skill lists that are actually noise
Listing 30 skills dilutes the 6 that matter. Worse, listing “Microsoft Word” in 2025 signals you’re scraping the bottom of the barrel. Your skills section should be 8–12 items max, directly relevant to the roles you’re targeting, and — this is key — the important ones should also appear naturally in your experience bullets, because some systems weight skills in context more heavily than skills in a list.
7. Typos in the first screen
I know. Obviously. But it still happens constantly, especially to non-native English speakers applying to English-language roles. “Manage” vs “Managed” inconsistencies, “recieve,” dates that don’t add up. A recruiter who spots an error in the top third of the page assumes there are more below it. Read it backward, out loud, and have one other person look at it. Then look again tomorrow with fresh eyes.
One Page or Two?
The eternal question. The honest answer: one page unless you have more than about 8–10 years of relevant experience.
Recruiters don’t reject two-page resumes out of principle. They reject resumes where page two is filler — ancient jobs from 2009 described in four bullets each, a “references available upon request” line (nobody has asked for this in fifteen years), hobbies that have nothing to do with anything.
If your second page is half full, cut things until it’s one page. If you’re a senior professional with genuinely dense, relevant experience, two full pages is fine.
Should You Use an AI Tool to Write Your Resume?
You’re reading this on the internet in the mid-2020s, so let’s address it directly.
AI tools are genuinely useful for: tightening awkward phrasing, generating accomplishment bullets from rough notes, and adapting your resume’s language to a specific job description.
They’re terrible at: inventing specific numbers (they’ll happily hallucinate “improved efficiency by 30%” with no basis), capturing your actual voice and judgment, and knowing what a recruiter in your industry actually cares about.
Use AI as an editor, never as an author. A resume that reads like ChatGPT output — “spearheaded,” “leveraged,” “dynamic professional” — blends into the pile. A resume with specific, concrete, slightly imperfect human detail stands out.
What to Do This Week
If you take nothing else from this article, take this sequence:
Pick your target role — one specific job posting, not a vague category.
Mirror its language where you honestly can. Same skills, similar phrasing, standard job titles.
Rewrite your top 5 bullets using the action + result formula with real numbers.
Simplify the layout — single column, standard headings, no text boxes.
Test it: copy and paste your PDF into a plain text file. If the order of information comes out scrambled, your formatting is a parsing risk.
Proofread twice, then have someone else do it once.
That’s it. No secret hacks. Just a resume that a machine can read and a human can respect in seven seconds.
