Common resume mistakes that get you screened out

Why good candidates get screened out

Over twelve years I have reviewed more than ten thousand résumés, and the most surprising pattern is this: the people who get screened out are rarely the least qualified. They are, far more often, qualified people whose résumés made a recruiter's job harder than it needed to be. A hiring decision starts as a triage decision. Faced with a folder of fifty or two hundred applications, a recruiter is not asking "who is the single best human here?" They are asking "who can I confidently move forward, and who can I set aside quickly?" Your résumé's first job is not to win; it is to survive that triage. Most mistakes in this guide are mistakes precisely because they hand the recruiter a reason to set you aside before your real strengths ever register.

There are two readers you have to satisfy, and they want different things. The first is the software, the applicant tracking system that ingests your file, pulls the text out, and files it into structured fields so a recruiter can search and sort later. It rewards clean, extractable text and the literal terms a recruiter will type into a search box. The second reader is the recruiter or hiring manager, who pulls you up and spends roughly six to eight seconds on a first pass deciding whether to keep reading. They reward clarity, relevance, and evidence of impact. A mistake that satisfies one reader while sabotaging the other still costs you the interview. The whole craft of a strong résumé is serving both at once, and almost every error below is a failure to do so.

The encouraging news is that these mistakes are not matters of talent or luck. They are concrete, identifiable, and fixable, usually in a single editing pass. You don't need a design degree, a clever template, or a secret keyword to beat. You need to stop doing a handful of specific things and start doing their opposites. This guide walks through each mistake in order of how often it quietly costs people interviews, shows you the fix, and ends with a priority order, a self-audit, and a checklist you can run before you ever hit submit. If you want the companion piece on how the software side works, read our deeper guide on writing a résumé that passes ATS; this article is about the human-and-machine mistakes that sit on top of it.

One framing is worth setting down before the list, because it changes how you read everything that follows. A résumé is not a record of your career; it is a persuasion document with a very specific reader under very specific conditions. That reader is busy, skeptical by default, looking at dozens of applications in a sitting, and deciding in seconds. They are not reading to admire you; they are reading to triage. Once you internalize that the audience is a hurried, doubtful skimmer rather than an attentive admirer, the mistakes in this guide stop looking like style preferences and start looking like what they are: friction that makes a hurried skeptic's job harder. Every fix is, at bottom, an act of empathy for that reader, making it effortless for them to see, fast, that you fit and should advance.

It also helps to separate the two kinds of mistakes you'll see below, because they fail you in different ways. Machine-facing mistakes — scrambled formatting, missing keywords, contact details stranded in a header, an image-based file — make you hard to find or invisible to search; they fail silently, with no feedback, which is why people repeat them for months without knowing. Human-facing mistakes — duties instead of results, no numbers, weak ordering, empty adjectives, typos — make you easy to set aside once found; they fail in the skim. A few mistakes are both at once, like a quirky job title that neither surfaces in search nor reads as relevant. The strongest résumés clear both bars together, and the method for doing so is the same throughout: clean, ordered, honest text that proves real impact.

The cost of a mistake compounds

It helps to understand why these errors are so much more expensive than they look. A résumé doesn't get one chance; it passes through a sequence of filters, and a mistake at any stage forecloses every stage after it. If your formatting scrambles in the parser, it never matters how compelling your bullets are, because no human reads them in order. If you lack the posting's keywords, you never surface in the recruiter's search, so your accomplishments are never even retrieved. If your top third is weak, the recruiter sets you aside in the skim before reaching the strong material lower down. Each filter is a gate, and a single mistake locks a gate. That's why fixing the highest-leverage mistakes — formatting, keywords, results-led bullets — returns so much more than polishing details further down the chain: you're unlocking gates, not decorating a room no one enters.

There's a second reason these mistakes punch above their weight: the recruiter's default in triage is rejection, not acceptance. With far more applicants than slots, the rational strategy under time pressure is to look for reasons to cut rather than reasons to keep. A two-column layout, a wall of duties, a typo, a generic summary — each hands the recruiter exactly the disqualifying signal they're scanning for. Your job is to give them no easy reason to cut, and several clear reasons to advance you. That asymmetry is the through-line of this entire guide: the bar isn't "be impressive," it's "remove every avoidable reason to be set aside, then make your genuine fit unmissable."

Mistake 1: Listing duties instead of results

This is the most common and most expensive mistake on the page, and it is worth more attention than any other. The vast majority of résumés describe responsibilities, what a person was supposed to do, rather than accomplishments, which is what they actually achieved. "Responsible for managing the social media accounts" tells a recruiter your job description. It tells them nothing about whether you were any good at it. And because almost everyone in that role had the same job description, a duty-listing bullet makes you indistinguishable from every other applicant. Sameness is invisibility, and invisibility is a soft screen-out.

The fix is a repeatable formula that I teach every member: strong verb + what you did + a quantified result. Lead with an action verb, state the concrete thing you did, and attach a number that shows the impact. The verb signals ownership, the action gives specifics, and the number proves it mattered. Once you internalize this shape, you stop writing job descriptions and start writing evidence.

Notice what changes. Every "after" version names a verb of ownership ("Grew," "Led," "Owned," "Migrated," "Coordinated"), specifies the work, and lands a number. The recruiter no longer has to guess whether you were effective; you've shown them. And crucially, this is not embellishment; it is the truthful, specific version of the same work, dug out of the vague language that hid it. The information was always there. The duty-listing résumé simply left it buried.

How to dig the accomplishment out of a duty

Most people write duties not because they lack accomplishments but because they don't have a method for surfacing them. Here is the one I use in every résumé review. Take any duty bullet and interrogate it with four questions: What was the situation before I acted? What did I specifically do? What was the result? How do I know — what's the number? Run "responsible for managing inventory" through those questions and it might become "Cut stockouts 40% by rebuilding the reorder-point model across 1,200 SKUs." Same job, but now the reader sees a before-state, an action, a result, and proof. If you've ever heard of the STAR method (situation, task, action, result) for interviews, this is the résumé version of the same instinct, compressed into a single line that leads with the result rather than the setup.

A useful discipline is to ban four phrases from your résumé entirely: "Responsible for," "Duties included," "Helped with," and "Worked on." Each one is a tell that you're about to describe presence rather than impact. Every time you catch yourself reaching for one, stop and ask what actually happened because you were there. "Helped with the product launch" hides a real contribution, so find it: "Owned the launch's email sequence, driving 2,300 sign-ups in the first week." The phrase you were going to write was the duty; the thing it was hiding is the accomplishment.

Strong verbs to lead with

The verb sets the tone of the whole bullet. Rotate among precise, ownership-signaling verbs and avoid repeating the same one down the page. Group them by the kind of work you're describing so the right one comes to hand:

Mistake 2: No numbers anywhere

The close cousin of duty-listing is the résumé that never quantifies anything. Even people who write action verbs often stop short of the number, and without it the bullet deflates. "Improved the onboarding process" is a claim with no shape. "Cut new-hire onboarding from three weeks to eight days" is a result a recruiter can picture, compare, and trust. Numbers are how a busy reader gauges scope and impact at a glance; they are the difference between a résumé that reads like everyone else's and one that stands out in the six-second skim.

The objection I hear most is "but my job isn't measurable." In twelve years I have almost never found that to be true. The goal is not to manufacture false precision; it is to add honest scope and scale so the reader can picture the size of your work. There are four families of metrics, and nearly every accomplishment fits at least one.

• Money — revenue influenced, costs cut, budget owned, savings generated, deals closed. "Managed a $1.2M budget"; "cut vendor spend 14%."
• Time — faster, sooner, on deadline, how often. "Reduced close cycle from 10 days to 4"; "shipped releases weekly."
• Volume or scale — people, customers, tickets, transactions, locations, data. "Served 4M daily requests"; "supported 120 staff across 6 sites."
• Quality or outcome — satisfaction, error rate, retention, ranking, compliance. "Lifted CSAT to 4.8/5"; "cut defects 30%."

Mine each role with three questions: How much? How many? Compared to what? If you genuinely can't pin an exact figure, an honest approximation ("~50 tickets a week," "roughly 30% faster") still beats a vague duty — just never fabricate a number you can't defend. For a deeper method on this, see our guide on how to quantify résumé bullets, which walks through mining metrics role by role.

Where to find numbers you think you don't have

When a member tells me their role had no metrics, we almost always find several in a ten-minute conversation. The numbers are there; they just live in places people don't think to look. A few reliable sources:

• The size of what you touched. Even if you can't measure your impact precisely, you can state the scale you operated at: "managed a 250-account portfolio," "supported a codebase of 80k lines," "handled intake for a 30-bed unit." Scale alone tells the reader the weight of the work.
• Frequency and cadence. How often did you do the thing? "Published 3 articles a week," "ran 12 retrospectives a quarter," "closed the books monthly across 4 entities." Frequency converts a vague responsibility into a measurable rhythm.
• Before-and-after comparisons. The most persuasive numbers are deltas. What was a metric when you started versus when you left? "Lifted retention from 71% to 88%," "took the backlog from 400 tickets to under 50." If you don't know the exact figures, an honest directional estimate still beats nothing.
• Relative standing. Where did you rank? "Top 3 of 28 reps," "highest CSAT on a 9-person team," "first cohort to hit the certification on schedule." Rank communicates excellence without needing an absolute number.
• Time saved or sped up. Process work is measurable in hours and days. "Cut monthly close from 10 days to 4," "automated a report that had taken 6 hours a week." Time saved is a number every hiring manager understands instantly.

One caution that's worth repeating: the goal is honest scale, not false precision. If you genuinely don't know whether it was 28% or 34%, write "roughly a third" or "~30%," and be ready to explain how you arrived at the estimate. A defensible approximation is a strength; a confident-sounding fabrication you can't back up is a trap that springs in the interview.

Mistake 3: Formatting that scrambles when parsed

Here is where interviews are quietly lost to something that has nothing to do with your experience. A résumé built in a beautiful two-column template, a slim sidebar of skills beside a wide main column, looks elegant on screen and turns to nonsense the moment a parser reads it. Many applicant tracking systems read the page left-to-right across the full width, line by line. When they hit a row that spans both columns, your sidebar text gets interleaved into your job history, and the stored version reads like word salad: "Skills SQL Senior Analyst Tableau Northwind Corp Python led a team of." The recruiter who searches for you later either can't find you or pulls up gibberish.

The fix is to stack everything in a single column, top to bottom, so the parser reads it in the order you intend. This one change prevents more parsing disasters than any other. And the disciplined version is not a downgrade — a clean single-column layout is also faster for a human to skim. You don't trade beauty for function; the safe format is simply better on both counts. The other formatting traps follow the same logic: anything that isn't plain, ordered, selectable text is a risk.

The subtler formatting traps

Beyond the big layout decision, a cluster of smaller formatting mistakes garbles otherwise clean résumés. Decorative bullet glyphs, fancy ligatures, and ornamental dividers can occasionally turn into stray characters in the parsed text — stick to standard bullets and simple hyphens or en-dashes. Tables used to lay out content (even an "invisible" one holding your skills in a grid) can be read cell-by-cell out of order by some parsers, so lay skills out as plain comma-separated text lines instead. Hyperlinks hidden behind text like "click here" lose the address when parsed; write the visible URL ("linkedin.com/in/yourname") so it survives as readable text. And dates belong in a consistent, spelled-out format — "Jan 2022 – Mar 2026," with "Present" for current roles — because right-aligning them with tabs is fine, but putting them in a separate column or table is where order scrambles. None of these are visible when you look at the rendered page; all of them show up the instant you run the copy-paste test.

The simplest test in the world catches almost every formatting mistake: open your résumé, select all the text, and copy it into a blank document. If anything is out of order, missing, or scrambled, the parser sees it that way too. If a name lives inside a logo image, a skill is shown as a progress bar, or your contact details sit in the document's header region, the copy-paste reveals it instantly. For a granular walkthrough of every layout rule, our guide on ATS résumé formatting goes element by element.

Mistake 4: Missing the keywords the posting actually uses

If a résumé never contains the words a recruiter searches for, it never surfaces — no matter how strong the experience behind it. Recruiters and the filters they run look for specific strings: the hard skills, tools, certifications, methodologies, and job titles named in the job description. If the role says "Kubernetes," a résumé that says "container orchestration platform" doesn't match the search. If it says "project management," that exact phrase needs to appear somewhere true. The mistake isn't a lack of qualification; it's a translation gap between how you describe your work and how the employer describes the role.

The fix is disciplined, not desperate. Read the posting twice — once for fit, once with a highlighter — and pull the eight to twelve most concrete, searchable terms. Confirm you genuinely have each one. Then place each term where it's true: in a short skills line for coverage, and inside an accomplishment bullet that proves it. "Cut deployment time 40% by automating our Kubernetes rollout" satisfies the filter and convinces the human, where a lonely "Kubernetes" in a skills blob does only half the job. Coverage plus evidence is the whole game. Our full guide to choosing résumé keywords details the extraction method.

A reliable method for extracting the right terms

Guessing at keywords is a mistake in itself; the posting tells you exactly what to use if you read it methodically. Here is the five-step extraction I teach:

1. Read the posting twice. First straight through for genuine fit. Then again with a highlighter, marking every hard skill, tool, certification, methodology, and the exact job title.
2. Separate must-haves from nice-to-haves. Terms in the "Requirements" or "Qualifications" section, and any term repeated more than once, are the must-haves. Those get priority placement.
3. Pull 8–12 concrete nouns. Focus on the things a recruiter would actually type into a search box: "SQL," "HIPAA," "Salesforce," "GAAP," "Series 7," "Figma," "demand forecasting." Skip soft, unsearchable phrases like "team-oriented."
4. Verify each against your real experience. Keep only the terms you can defend in an interview. A keyword you can't speak to is a liability, not an asset — it sets up a question you'll fail.
5. Place and prove. Put each surviving term in your skills line for coverage and inside a bullet that shows you using it for a result. Coverage without proof is hollow; proof without coverage may not surface in search. You need both.

A few exact-match details trip people up even when they have the right terms. Spell out an acronym and include the acronym once — "Search Engine Optimization (SEO)" — because a recruiter might search either form. Mirror the posting's spelling, including British versus American variants ("optimisation" versus "optimization"). And match the posting's word form for the key requirement phrase: if the role demands "project management," make sure that literal phrase appears somewhere true, even if "managed projects" also shows up in your bullets. Parsers and search filters are literal to a fault, and small mismatches cost you matches.

Mistake 5: Sending one generic résumé to every job

A single all-purpose résumé blasted to every opening is one of the top reasons for silence — and it's the mistake people are most reluctant to fix because tailoring sounds exhausting. It isn't. With a strong base résumé, you only adjust three things per role, and the whole pass takes about eight minutes.

1. The summary. Swap in the exact target job title and the two or three skills the posting emphasizes most. Two minutes.
2. The skills line. Reorder and lightly edit so this posting's must-have terms appear and lead. One minute.
3. The top two or three bullets of your most relevant role, so the accomplishments that matter to this employer are read first. Five minutes.

Keep a master résumé that holds every accomplishment you've ever earned, then cut and reorder for each application rather than writing from scratch. A generic résumé forces the recruiter to do the translation work of figuring out how you fit; a tailored one does that work for them, which is exactly what a six-second skim rewards. This per-role tailoring is the single highest-return habit in a job search — and it is precisely the work a résumé optimization service takes off your plate.

What an eight-minute tailoring pass looks like

To make this concrete, here's the same candidate adapting one base résumé to a specific posting. Suppose the role is "Marketing Manager — DTC brand" and the requirements name performance marketing, Meta Ads, Google Ads, email (Klaviyo), SQL, A/B testing, budget ownership, and ROAS/CAC reporting. The generic and tailored summaries diverge immediately:

The tailored version states the exact target title and folds in seven of the posting's must-have terms — naturally, because they're all true — and lands a headline result. The skills line and the top bullets of the most relevant role get the same treatment: reorder so this posting's must-haves lead, and surface the two or three accomplishments that map most directly to what the employer is hiring for. Everything else on the résumé stays put. That's the whole pass — title, skills order, top bullets — and it takes about eight minutes once your master résumé is strong. You are not rewriting; you are re-pointing an existing, complete document at one specific target.

Mistake 6: Burying your best material

Even a résumé full of strong, quantified accomplishments fails if the best ones are hidden on page two or at the bottom of a role. A recruiter's eye makes its first judgment in the top third of page one. If that zone is filled with your contact details, a vague objective, and your oldest or least relevant job, you've spent your most valuable real estate on your weakest content. The decision is half-made before they reach the bullet that would have won them over.

The fix is ruthless ordering. Lead each role with its most impressive, most relevant bullet — not the chronological first thing you did each morning. Put your strongest accomplishments and your most posting-relevant skills in the top third of the page. For experienced candidates, that means experience near the top and education below; for new grads with a thin work history, lead with education and a standout project. The principle is constant: the reader's attention is a scarce resource that decays down the page, so spend it on your best.

It helps to know how a recruiter's eye actually moves on a first pass. In that six-to-eight-second skim, they don't read left to right, top to bottom like a novel. They jump: name, current title, the company and dates of the most recent role, the first bullet or two under it, then the skills line and a quick scan for relevant keywords. That scan path is why the top of each section carries disproportionate weight — it's literally where the eye lands. Anything strong that sits in the fourth bullet of your second role, or at the bottom of page two, is in a zone the skim may never reach before the keep-or-cut decision is made. You're not writing for a careful reader who'll eventually find your best work; you're writing for a fast one who decides based on what's in the landing zones. Stack those zones with your strongest, most relevant evidence and let the rest support it.

What changed: the strongest, most quantified result moved to the top of the role, the routine maintenance line dropped to last and gained scope, and a second metric surfaced. Same job, same truth — but now the win is the first thing read.

Mistake 7: A dated objective statement

"Objective: To obtain a challenging position at a growth-oriented company where I can utilize my skills and grow professionally." If your résumé opens like this, you're spending the most-read lines on the page telling the employer what you want — which is the one thing they aren't yet trying to learn. The objective statement is a relic. It's self-focused where the reader is reader-focused, generic where the moment demands specificity, and it pushes your actual evidence further down the page.

Replace it with a three-to-four-line professional summary written for the reader. State who you are (your title and area), your years and strongest relevant skills, and one headline result with a number. This is prime real estate for the exact job title and top keywords, and it's the first thing the recruiter reads, so make it work hard.

What changed: the self-focused wishlist became a reader-focused proof statement — exact title, real skills, and a headline number — that doubles as keyword-rich and instantly relevant.

One nuance worth getting right: a summary is not the same as the old objective wearing new clothes. The test is whose needs the sentences serve. An objective talks about what you want from the employer; a summary tells the employer what they get from you. If your "summary" still contains phrases like "looking for an opportunity to grow" or "seeking a role that allows me to," it's an objective in disguise — rewrite it to lead with your title, your proven strengths, and a result. And keep it tight: three or four lines. A summary that runs to a full paragraph stops being a fast orientation and becomes another wall of text the skimmer skips. The whole point of the section is to let a recruiter understand, in two seconds, exactly who they're looking at and why you're relevant.

Mistake 8: Wrong length and visual clutter

Two opposite errors live here. The first is the résumé that runs too long — a new grad's three-page document, or a mid-career professional padding to fill space with every task they've ever performed. The second is the cramped, wall-of-text résumé with no white space, where eight-point font and zero margins make a recruiter's eyes slide off the page. Length itself rarely screens you out; irrelevance and unreadability do.

The guidance is simple. One page if you have under ten years of experience, two pages beyond that, and two to three for senior or executive roles. Within that, prune anything that doesn't earn its place — the part-time job from fifteen years ago, the obvious skills ("Microsoft Word," "email"), the high-school details once you hold a degree. Give the page room to breathe with clear headings, real bullet points, and consistent spacing. A recruiter skimming fifty résumés rewards the one they can read without effort.

What to cut first when you're over length

When a résumé runs long, the instinct is to shrink the font and the margins until it fits. That's the wrong fix — it makes the page harder to read while keeping the low-value content. Cut content instead, in this order. Remove roles older than ten to fifteen years unless they're directly relevant; a one-line summary of early career ("Earlier roles in retail management, 2008–2013") often suffices. Strip obvious skills no one is impressed by — "Microsoft Word," "email," "internet research." Delete the high-school line once you hold a degree. Trim each role from six bullets to the three or four strongest, dropping routine duties and keeping quantified wins. And remove anything that doesn't connect to the job you're applying for now; relevance, not completeness, is the standard. A résumé is a marketing document, not an exhaustive career archive.

The opposite problem — too little to fill even one page — is usually a sign the accomplishments are underwritten rather than absent. Before padding with filler, go back through Mistakes 1 and 2 and expand thin duties into fuller accomplishment bullets with context and numbers. A genuinely sparse history (a new grad, a short career) is fine on a confident one-pager; what reads badly is a half-empty page stretched with "Proficient in Microsoft Office" and triple line spacing. Fill the space with substance or let it be short.

Mistake 9: Typos, inconsistency, and careless errors

This is the most avoidable screen-out of all, and it stings the most because the work behind the résumé may be excellent. A typo, a misspelled company name, a date that doesn't line up, "manager" capitalized in one place and not another — each is a small thing, but together they signal carelessness to a recruiter whose whole job is judging signals. When two candidates are close, the clean one wins. And inconsistent date formats don't just look sloppy; they can confuse a parser trying to compute your tenure.

The fix is process, not talent. Proofread out loud — your ear catches errors your eye skims past. Read the bullets bottom to top, which breaks the narrative flow and exposes mistakes. Standardize every date to one format ("Jan 2022 – Mar 2026," "Present" for current roles). Check that company names, titles, and tense are consistent. Then have one other person read it cold; a fresh set of eyes catches what you've gone blind to after the tenth revision.

Mistake 10: Telling instead of showing

A résumé packed with self-description — "hard-working team player, detail-oriented, excellent communicator, results-driven" — tells a recruiter who you say you are. It proves nothing. Anyone can claim to be detail-oriented; the claim is free, so it carries no weight. Worse, these adjectives consume space that evidence should occupy. A recruiter believes verbs and numbers, not adjectives about character.

The fix is to convert every claim about who you are into evidence of what you did. Don't say "detail-oriented" — show it: "Caught a billing error that had overcharged 1,200 accounts, recovering $84k." Don't say "great communicator" — show it: "Presented quarterly results to a 40-person leadership team and a board of directors." The trait becomes undeniable because you've demonstrated it instead of asserting it. Cut the adjective; keep the proof.

The phrases to cut on sight

A handful of stock phrases appear on so many résumés that recruiters' eyes glaze past them. They consume space, prove nothing, and signal that the writer reached for a cliché instead of a specific. Cut each one and replace it with the evidence it was standing in for:

• "Responsible for…" → name the action and its result: "Led," "Owned," "Built."
• "Helped with…" / "Assisted with…" → state your specific contribution and what it produced.
• "Worked on…" → say what you delivered and the outcome.
• "Duties included…" → delete entirely and lead with an accomplishment.
• "Team player," "hard worker," "detail-oriented," "self-starter" → unprovable traits; demonstrate them through a result instead.
• "Results-driven," "go-getter," "synergy" as filler → replace with an actual result; the word is no substitute for the thing.

A simple test catches the rest: for every adjective on your résumé, ask "could the opposite candidate also write this?" Nobody describes themselves as careless, lazy, or a poor communicator, so claiming the positive carries no information — both the strong and the weak candidate write "detail-oriented." Only evidence distinguishes you, because only your real results are uniquely yours. Strike the adjective; keep the proof.

Mistake 11: Quirky internal job titles no one searches for

If your company called you a "Growth Ninja," a "Customer Happiness Hero," or a "Code Wizard," that title means nothing to a recruiter's search and little to a hiring manager scanning for relevant experience. Internal or whimsical titles are a hidden screen-out: you may have done exactly the right work, but it's filed under a label no one is looking for. The parser indexes the quirky string; the recruiter searches the standard one; you never connect.

The fix is to lead with the market-standard title for the work you actually did, and note the internal one in parentheses if you like. "Marketing Manager (internally: Growth Ninja)" gives you the searchable term, the honest record, and a small note of personality without sacrificing findability. The same goes for the reverse problem — an over-inflated title that overstates your scope. Use the title that a recruiter would recognize and search for, and let your bullets establish your true level.

Mistake 12: Exaggeration and outright lies

This is the most damaging mistake on the page, and it deserves the bluntest treatment. Inflating a title you never held, stretching dates to hide a gap, claiming a degree you didn't finish, or listing skills you can't perform are not clever optimizations — they are the errors most likely to end a candidacy, and sometimes a job. Fabrications surface in reference checks, background checks, and interviews, where a hiring manager asks you to walk through the work behind a claim and the story unravels. Misrepresentation is grounds for a rescinded offer or termination after hire, no matter how strong the rest of your record.

The reassuring truth is that you almost never need to lie, because honest framing of real work is more persuasive than invented credentials. The entire method in this guide — quantifying, leading with results, mirroring genuine keywords, tailoring — is about presenting your actual experience at its strongest. A gap can be named confidently. A career change can be bridged truthfully. An unfinished degree can be listed honestly as "coursework toward." The strongest résumé is the truest version of your real story, told well — never a fictional version told boldly.

The line between strong framing and dishonesty

People sometimes worry that aggressive framing tips into lying. It doesn't, as long as the underlying facts are true and defensible. There is a clear line, and it's worth naming explicitly so you can write boldly without crossing it.

The reliable test is the interview: can you walk a hiring manager through the work behind every line, in detail, without flinching? If yes, you're framing. If any line would unravel under "tell me more about that," it's a fabrication waiting to be caught. Reference checks, background checks, and probing interview questions exist precisely to find that line, and they find it more often than people assume. The honest version of your real story, told at its strongest, is both safer and more persuasive than any invention.

Mistake 13: Fumbling gaps, changes, and special cases

Real careers aren't tidy, and the mistake isn't having a gap or a pivot — it's handling it clumsily. An unexplained blank between jobs invites worse assumptions than a calm, brief explanation does. The fix in every case is the same: state the situation plainly in one confident line, then move the reader's eye straight back to your results.

Employment gaps

Use plain year ranges; parsers handle them fine. For a longer gap, name it without apology — "Career break (caregiving), 2024–2025" as a short dated entry, or one calm line in your summary. Recruiters see gaps constantly. For a deeper treatment, see our guide on explaining employment gaps on a résumé.

Career changes

Lead with a summary that states your target role in its own language, then reframe past accomplishments using the new field's vocabulary, grouping your most relevant experience first. Add a bridging credential — a course, certification, or project — to show momentum. Our résumé guide for career changers walks through the full reframe.

Relocation and remote roles

If you're targeting a city you don't live in yet, don't fabricate a local address — that unravels awkwardly later. List your current city plus a short line in the summary stating your openness to relocate, or note the target metro with "(relocating)." For remote roles, make "remote" presence explicit somewhere in the document so you surface in those searches and the recruiter isn't left guessing about your availability.

Visa and international candidates

Applying across borders adds its own avoidable mistakes. Use the standard, locally recognized job titles and spellings for the market you're applying to, and translate credentials into their local equivalents where it helps a recruiter place them. Keep work-authorization statements honest and answer authorization knockout questions accurately — guessing or hedging here screens you out faster than a clear answer ever would. Our guidance for visa and international talent goes deeper on visibility and access in a new market.

Over-explaining

The opposite mistake is just as common across all of these cases: a paragraph of justification for a gap, a pivot, or a relocation. Over-explaining draws attention to the very thing you're worried about and signals that you see it as a liability. One clear, confident line is enough; state it plainly, then redirect the reader's eye straight back to your results. The calm framing does more reassuring than any amount of apology.

Mistake 14: Contact, file, and apply-form errors

Finally, the small operational mistakes that can sink a perfect résumé before anyone reads it. Contact details placed in the document's header or footer region may be skipped by some parsers, so keep your name, email, phone, city/state, and LinkedIn URL as plain text lines at the very top of the body. An unprofessional email address undercuts everything above it; use a simple firstname.lastname address. And the file itself matters: submit a text-based PDF (or .docx when the form asks), never a scanned image, a .pages file, or anything where the text isn't selectable.

Name the file clearly — Firstname-Lastname-Resume.pdf — so the human downloading a folder of fifty applications knows instantly whose it is; avoid "resume-final-v7-REALLY-final.pdf." On the application form, the system often auto-fills fields from your parsed résumé and asks you to confirm; this is your chance to fix anything the parser got wrong, so don't skip it. Answer required and knockout questions honestly and completely, and if there's a plain-text box, remember that what you paste is exactly what the parser sees — make sure it reads cleanly.

Mistake 15: Letting your résumé contradict the rest of your story

A final, often-invisible mistake: treating the résumé as if it applies in a vacuum. It doesn't. Recruiters routinely cross-check your résumé against your LinkedIn profile and any cover letter you submit, and parsers index those surfaces too. When the titles, employers, or dates don't match across them, the mismatch reads as a red flag — at best carelessness, at worst something to hide — and it can quietly cost you a callback even when each individual document is strong.

• LinkedIn parity. Your job titles, employers, and date ranges should match your résumé exactly. LinkedIn is itself a searchable database recruiters mine, so mirror your strongest keywords in your headline and About section as well. Our guide on optimizing your LinkedIn profile covers this in depth.
• Cover letters. When one is asked for, keep it short, specific, and keyword-aware without repeating the résumé verbatim. Name the role, show you understand the problem the team is solving, and connect one or two proof points. A generic, template cover letter is its own screen-out.
• Consistent entity details. Same name spelling, same contact information, same title conventions everywhere you appear. Consistency is a trust signal to the human and a clean signal to the systems that index you across the web.

This whole-search consistency is part of what a Marqee strategist manages end to end — aligning your résumé, profile, and outreach so every surface tells the same strong story. It connects directly to the personal branding work that makes you recognizable to the people who hire, and it's why fixing your résumé in isolation only gets you part of the way there.

Before & after rewrites

Principles stick when you see them applied. Below are full-bullet rewrites of the kind our strategists make every day, showing several mistakes corrected at once. Read each "before" and try to name the mistakes yourself before reading the fix — it trains your eye for your own résumé.

Example 1 — Customer support specialist

Mistakes fixed: a creative heading became the standard, searchable title; duties became quantified accomplishments; the "hard worker / team player" adjectives were replaced with proof.

Example 2 — Career changer (teacher → project coordinator)

Mistakes fixed: the custom heading became standard; a target-role summary reframes transferable skills in the new field's language; vague traits became evidence with numbers.

Example 3 — Software engineer

Mistakes fixed: "various technologies" became named, searchable keywords (Go, Python, Redis, Kubernetes); generic tasks became quantified outcomes a filter and a hiring manager both reward.

Example 4 — New grad with thin experience

Mistakes fixed: the objective became a reader-focused summary; a class project was reframed as a real, quantified Projects section leading the page; even the part-time job gained scope and numbers. Thin experience, presented like accomplishments.

The fix-it priority order

You don't have to fix everything at once, and some fixes return far more than others. If you have twenty minutes, spend it from the top of this list down. The first three changes alone will move the needle more than every other tweak combined.

A 10-minute self-audit

Knowing the mistakes is one thing; catching them in your own résumé is another, because after the tenth revision you read what you meant to write rather than what's on the page. A structured audit forces fresh eyes. Print your résumé if you can — errors that hide on a screen jump out on paper — or open it beside this list, and answer each question honestly with a yes or a no. Don't rationalize a "sort of" into a yes; the recruiter won't. Every "no" is a mistake from this guide that's quietly costing you interviews, and the list is ordered so that fixing the "no"s from the top down spends your effort where it returns the most.

• Results, not duties? Does every bullet start with a verb and lead with what you achieved, not what you were responsible for?
• Numbers present? Does each top bullet carry a metric — percent, count, dollar, or time?
• Parses clean? When you copy all the text into a blank document, does it stay in order with nothing scrambled or missing?
• Keywords matched? Do the posting's genuine hard-skill and title terms appear, proven in bullets and listed in skills?
• Best material up top? Is your strongest, most relevant accomplishment in the top third and at the top of each role?
• Tailored? Did you adjust the summary, skills line, and top bullets for this specific posting?
• Showing, not telling? Have you replaced "team player" and "detail-oriented" with evidence?
• Standard titles and headings? Is your role title the one a recruiter would search, under headings a parser recognizes?
• Honest throughout? Can you defend every title, date, skill, and number in an interview?
• Clean and consistent? No typos, one date format, professional email, right length, file named clearly?

The pre-send checklist

Run this final pass before every application. It's the same discipline our strategists apply to every résumé before we submit on a member's behalf.

• Paste test. Copy all the text into a blank document. Anything out of order, missing, or scrambled means the parser sees it that way too — fix the layout.
• Contact check. Name, email, phone, and city/state are plain text at the top of the body, with a professional email address.
• Results sweep. Every top bullet leads with a verb and a number, not a duty or an adjective.
• Keyword match. The posting's must-have skills and the standard job title appear, proven and listed.
• Lead with the best. Your strongest, most relevant material sits in the top third of page one.
• Length and clutter. One page under ten years, two beyond; nothing padded, room to breathe.
• Proof pass. No typos, one date format, consistent tense, everything defensible in an interview.
• File and name. Text-based PDF (or .docx if asked), named Firstname-Lastname-Resume.pdf.

The screening systems aren't your enemy, and neither is the recruiter — sloppy, duty-listing, untailored résumés are what cost interviews. Fix the mistakes in this guide and your real qualifications finally get the read they deserve. If you'd rather not run every pass yourself, that's the entire point of Marqee: real career experts find the roles, tailor your materials for each posting, run recruiter outreach, discover warm referrals, and submit on your behalf — so you stop applying and start interviewing. Go deeper with our companion guides on passing ATS, quantifying your bullets, and choosing keywords, learn more Marqee Editorial, or browse the full resources library.

Frequently asked questions