Bad resume examples and what makes a resume terrible

What actually makes a resume bad?

A resume is bad when it makes the reader do the work of figuring out why you fit. Every terrible resume fails in one of three ways: the file doesn't parse cleanly, the content doesn't prove anything, or the whole thing was obviously written for nobody in particular. Typos and novelty fonts get all the attention in listicles, but they're rarely what kills an application. The real damage is quieter — a three-page document with a 2009 internship still on it, a skills section lifted straight from a template, a summary describing a "results-driven professional" who could be literally any of the other 200 applicants. None of that looks ugly. It's just empty.

The context matters. Eye-tracking research has put the first pass at roughly six to eight seconds, and newer studies measuring recruiters who review with the job ad open beside them land closer to eleven. Either way, the window is seconds, not minutes. Once a resume survives that gate, median review time jumps to about a minute and a half, mostly spent verifying titles, dates and the numbers you claimed. So there are two audiences and two failure points: a parser that decides whether your details land in the right database fields, and a human making a fast fit or no-fit call on six things — your name, current title and employer, previous title and employer, dates, and education.

Here's the unpopular part: the most damaging bad resume isn't the messy one. It's the competent-looking, well-spaced, perfectly spelled document that says nothing specific. Messy resumes at least get read out of curiosity. Polished-but-generic ones get a polite pass because there's no reason to pick them over the next file in the queue. The same goes for title mismatch — describing an operations coordinator's day-to-day while applying for a project manager role reads as a misfire, even when the underlying skills transfer. If your resume could be sent unchanged to five different job ads, you've already found your biggest problem.

Which formatting mistakes stop your resume from being read?

The formatting choices that break resumes are tables, text boxes, icons, skill bars, images and contact details tucked into the document header. A parser flattens your file into plain text and reads top to bottom, left to right. Anything that relies on visual position rather than reading order gets scrambled or dropped entirely. The classic symptom of a header-based contact block is a candidate profile with no name and no email — the fields come back blank because most screening engines skip header and footer regions. Skill bars and filled circles are images, so the parser extracts nothing from them. Your "Advanced: Python" rating becomes the word Python, or nothing at all.

Tables are the sneakiest offender because you often can't see them. Plenty of modern templates use a borderless table to line dates up neatly against job titles, and when the structure is stripped, dates detach from the roles they belong to. Workday in particular has a long record of mangling content inside tables, including simple two-column skills grids. Creative section headings cause a related problem: a parser looking for "Work Experience", "Education" and "Skills" doesn't know what to do with "My Journey" or "What I Bring". Boring headings aren't a lack of imagination. They're how your experience ends up in the experience field.

One honest nuance for 2026: native document columns are no longer an automatic death sentence. Testing against major systems suggests clean two-column layouts built with real column formatting — no tables, no text boxes, no images — often extract acceptably, and controlled benchmarks tend to ding them on structure rather than losing the words outright. Still, a single column is the only layout that behaves predictably everywhere, so save the two-column version for a PDF you hand to a person. The fastest check costs nothing: save your resume as plain text and read it. If dates float away from titles and your skills merge into a sentence, you've found the problem. If you want the full picture, here's why a beautifully designed CV can scan terribly.

What do bad resume bullet points look like?

Bad bullets describe duties in the passive language of a job description, with no number, scope or outcome attached. "Responsible for handling customer inquiries" and "Tasked with updating client records" tell a recruiter what the role involved, not what you were like in it. Anyone who held that title could have written them. The tell is grammatical: if a bullet starts with "responsible for", "duties included", "assisted with" or "involved in", it's a copy of the posting you answered, not evidence of your work. Recruiters spend most of their post-scan reading time verifying results and titles. Give them nothing to verify and there's nothing to be impressed by.

A strong bullet has four parts: what you did, how you did it, the measurable change, and the scope or constraint that makes it hard. "Cut order processing from 12 seconds to 800 milliseconds by rebuilding the event pipeline, for 40,000 daily transactions" works because every element is checkable. So does "Hit 118% of a $1.4M quota with an average deal size of $46K and a 71-day cycle." You don't need a percentage on every line — volume, team size, budget, ticket counts, uptime, headcount trained, tools owned all count. The one rule that matters: only use numbers you'd be comfortable explaining in an interview, because that's exactly where they'll come up.

The other bullet-level failure is buzzwords doing the job that evidence should do. In one widely cited survey, 68% of recruiters said they dismiss resumes stuffed with buzzwords that have nothing behind them, and keyword stuffing reads as dishonest rather than thorough — repeating a phrase from the job ad six times doesn't fool a modern parser and definitely doesn't fool a person. "Synergize", "dynamic", "detail-oriented", "passionate about driving innovation": cut all of it and use the space for one concrete result instead. If rewriting thirty bullets by hand sounds grim, the HRLens CV builder works by chat — paste the old version, then push each bullet toward specifics line by line.

Why do recruiters reject resumes that read as AI-written?

Recruiters aren't rejecting AI itself — they're rejecting the vagueness that unedited AI drafts produce. In a 2026 survey of 1,500 US hiring managers, heavily AI-generated application materials ranked as the second-biggest candidate red flag at 49%, behind only job-hopping at 65%. The complaint is consistent: "improved operational efficiency" with no number, no scope and no context could describe anyone, and when fifty applications arrive sounding the same, none of them stands out. A model can only write from what you feed it. Give it three sentences about your job and it fills the gap with adjectives, which is precisely the material recruiters have learned to skim past.

The giveaways are more structural than lexical. Every bullet opening with a power verb — spearheaded, orchestrated, championed — at a suspiciously uniform length is the loudest signal. So is the same claim restated across three roles, random bolding of dollar amounts or keywords pulled from the ad, a pile of em dashes, and vocabulary that's become shorthand for generated text: pivotal, intricate, showcasing, adept, cutting-edge, delve. Recruiters also notice career stories that are too smooth. A flawless upward trajectory with every gap quietly sanded away tends to trigger a LinkedIn cross-check, and a polished resume attached to a thin or contradictory profile is a far bigger problem than the writing style.

Use AI where it's genuinely good and stop there. It's excellent at structure, section order, tightening a sprawling paragraph, and catching the phrasing you've gone blind to after twelve drafts. It's bad at inventing substance, which is the part only you have. Write your own facts first — the numbers, the tools, the incident you handled at 2am — then let the model help you phrase them. Vary the rhythm deliberately: not every bullet needs a verb up front, and one sentence of context before a result often reads more human than another metric. The point isn't hiding that you used AI. It's making sure there's something underneath it.

How do you tell whether your own resume is one of the bad examples?

Run three tests, in this order: the plain-text test, the ten-second test and the evidence test. Save your resume as a .txt file and open it. If your name and email appear at the top, roles read in order, and dates sit beside the right employers, the parsing side is healthy. If the text scrambles, your layout is the problem and no amount of rewording will fix it. Then hand the file to someone for ten seconds and ask what job you're applying for. If they can't say, the top third of the page isn't doing its job — and the top third is nearly all a recruiter reads before deciding.

The evidence test is the harshest. Go bullet by bullet and ask whether a stranger could challenge the claim. "Improved team collaboration" can't be challenged, which is exactly why it's worthless. "Reduced sprint carryover from 30% to 9% across two squads" can be, which is why it works. Aim for a verifiable detail in at least two thirds of your bullets. While you're there, cut anything older than about fifteen years unless it's genuinely relevant, delete date of birth and marital status, and check that your length matches your experience: one page for under five years, two pages once you're managing scope or people. Three pages needs a real reason.

If you'd rather not audit yourself, get an outside read. A free CV analysis from HRLens scores your file out of 100 with five category scores — experience, tech stack, impact and ownership, clarity and structure, and ATS compatibility — plus a visual layout analysis showing how the document reads, and it accepts PDF, Word or an image, including Hebrew via OCR. Paste the job description too and it flags the skills the ad asks for that your CV never mentions. The Full Analysis at $3.99 adds the fix list, your likely rejection reasons and blind spots. Either way, you learn which of these bad-resume patterns is actually yours.

Frequently asked questions