Bad Resume Examples: 11 Mistakes and How to Fix Them
See complete bad resume examples, compare them with improved versions, and learn how to fix weak bullets, vague summaries, poor formatting, irrelevant content, and ATS readability issues.
A bad resume rarely looks ridiculous. It usually looks reasonable enough to send—and that is exactly why the problem is easy to miss.
The dates are there. The job titles are there. The page is clean. But after a few seconds, the reader still cannot answer the questions that matter: What role does this person fit? What have they actually achieved? Why should I keep reading?
That is the difference between a resume that contains information and a resume that makes a convincing case. A strong resume should be easy to read, clearly relevant to the role, and supported by evidence. When one of those pieces is missing, even a qualified candidate can look generic.
Below, you will see a complete bad resume example, a stronger version of the same candidate, and 11 common mistakes you can fix without inventing experience or turning the document into a keyword puzzle.
What Actually Makes a Resume Bad?
A bad resume creates friction. The hiring system may struggle to extract the information, the recruiter may struggle to scan it, or the content may fail to prove that the candidate can do the job.
Most weak resumes fail in one or more of these ways:
It is difficult to read, scan, or parse.
It does not make the target role obvious.
It describes responsibilities without showing scope, results, or evidence.
It gives equal space to relevant and irrelevant information.
It relies on generic claims that could describe almost anyone.
None of this means there is one perfect format or a secret ATS score. Applicant tracking systems differ, and their role can include collecting applications, parsing resume data, supporting search, and applying employer-defined rules. For a detailed explanation, read The Truth About ATS: Stop Writing Resumes for Robots.
A Complete Bad Resume Example
The resume below is not absurd. It has a recognizable structure, relevant work history, and no obvious spelling disaster. That makes it useful: it resembles the kind of document people genuinely submit.
Jordan Lee
Operations Professional
- jordan.lee@email.com
- (312) 555-0147
- Chicago, IL
Objective
Motivated and hardworking professional seeking a challenging position in a growing company where I can use my communication, organization, and problem-solving skills while continuing to develop professionally.
Experience
Operations Assistant | ABC Company | 2022 - Present
Responsible for handling administrative tasks and helping different departments
Worked on reports, spreadsheets, and other documents as needed
Helped customers and employees solve problems
Participated in meetings and supported various company projects
Helped train new employees and answered their questions
Administrative Assistant | Northstar Services | 2020 - 2022
Answered phones and emails
Managed calendars and scheduled meetings
Entered data and organized company files
Assisted managers with daily tasks and special requests
Education
Bachelor of Arts in Business Administration | Midwest College | 2020
Relevant coursework: Business Communication, Management, Marketing, Accounting, and Organizational Behavior
Skills
Communication, teamwork, problem solving, Microsoft Word, Microsoft Excel, email, organization, time management, hard worker, fast learner
Additional Information
Available immediately. References available upon request.
Why This Resume Does Not Work
The target role is unclear
“Operations Professional” is broad, and the objective focuses on what the candidate wants rather than the value they bring. A recruiter should not have to reverse-engineer the candidate’s direction from several sections.
The experience proves attendance, not impact
Phrases such as “responsible for,” “worked on,” and “helped with” show that Jordan was present. They do not show the scale of the work, the problem solved, the quality of the result, or what changed because Jordan handled it.
The skills section is mostly self-description
“Hard worker,” “fast learner,” and “teamwork” are not useless qualities, but listing them does not prove them. Stronger resumes either show those qualities through achievements or replace them with concrete, role-relevant capabilities.
Relevant and low-value information receive equal weight
The coursework, “references available upon request,” and long generic skills list take space without strengthening the application. Meanwhile, the most important section—recent experience—contains almost no evidence.
The document looks complete but says very little
This is the central problem. The resume has enough content to fill the page, but not enough signal to create confidence.
The Same Candidate, Rewritten
The improved version does not give Jordan a new career. It uses the same employers, dates, education, and general responsibilities. The difference is how the information is selected and explained.
Jordan Lee
Operations Coordinator
- jordan.lee@email.com
- (312) 555-0147
- Chicago, IL
Professional Summary
Operations professional with 6 years of experience improving workflows, coordinating cross-functional projects, and supporting business teams through clearer processes and reporting.
Experience
Operations Assistant | ABC Company | 2022 - Present
Coordinated reporting workflows across sales, finance, and customer support teams, reducing weekly preparation time by 6 hours
Created a request-tracking process that improved response times by 24% and increased visibility across departments
Supported 12 cross-functional projects by coordinating timelines, communication, and stakeholder updates
Prepared weekly performance reports used by managers to track operational improvements
Administrative Assistant | Northstar Services | 2020 - 2022
Managed calendars, documentation, and internal communication for a team of 15 employees
Improved the file organization system, making frequently used documents easier to locate
Education
Bachelor of Arts in Business Administration | Midwest College | 2020
Skills
Process improvement, project coordination, stakeholder communication, reporting, Microsoft Excel, workflow optimization, operations management
What Changed?
The generic objective became a focused professional summary.
The headline now names a clear target role.
Responsibilities became examples of scope, ownership, and outcomes.
Soft-skill claims were replaced with job-relevant capabilities.
Older experience was shortened instead of receiving the same weight as the current role.
Unnecessary filler was removed, making the strongest evidence easier to find.
The improved resume is not better because every bullet contains a percentage. It is better because each section helps the reader understand the candidate’s direction and evidence.
11 Bad Resume Examples and How to Fix Them
1. A Generic Objective
Bad example: “Motivated professional seeking a challenging opportunity where I can use my skills and grow with the company.”
This sentence could appear on thousands of resumes. It tells the employer what the candidate wants, but not what role they fit or what they can contribute.
Better: “Operations Coordinator with four years of experience improving reporting workflows and supporting cross-functional projects.”
Objectives are not automatically wrong. They can still help some students, career changers, or candidates with a very specific target. The problem is a generic objective that adds no information. A summary or objective is useful only when it adds context that the rest of the resume does not make obvious.
2. An Empty Professional Summary
Bad example: “Results-driven team player with excellent communication skills and a proven track record of success.”
Adjectives are not evidence. A useful summary should quickly establish the candidate’s role, experience, specialization, and strongest relevant proof.
Better: “Customer Success Specialist with five years of experience supporting B2B software accounts, improving onboarding, and managing renewals across a $1.2M portfolio.”
3. Responsibility-Only Bullet Points
Bad example: “Responsible for preparing reports and communicating with stakeholders.”
A job description explains what the role was supposed to do. A resume should explain what the candidate actually handled and what happened as a result.
Better: “Prepared weekly performance reports for five department leads, reducing manual consolidation time by six hours per week.”
Use an action, add useful context or scale, and include an outcome when one exists. Harvard’s resume guide and action-verb resources emphasize active language and evidence of results.
4. Unsupported Soft Skills
Bad example: “Leadership, communication, problem solving, hard worker, fast learner.”
The reader cannot verify these claims from a list. The strongest place to prove communication or leadership is usually the experience section.
Better: “Coordinated weekly planning across sales, finance, and support teams and maintained stakeholder updates for 12 projects.”
A skills section is most useful for concrete tools, methods, languages, systems, and role-specific capabilities that employers may actively look for.
5. A Wall of Text
Bad example: A six-line paragraph describing every responsibility from a job.
Dense paragraphs hide the strongest details. Recruiters often need to identify relevant information quickly, so structure matters. MIT recommends a clear, consistent format that makes the most relevant information immediately visible. Its resume checklist also emphasizes readability and consistency.
Better: Use a short role description when context is necessary, followed by focused bullets that each communicate one contribution.
6. Too Much Irrelevant History
Bad example: A mid-career operations candidate gives six bullets to a retail job from twelve years ago and two bullets to the current role.
A resume is not a complete employment archive. Older or unrelated roles can be shortened, grouped, or removed when they no longer support the target position.
Better: Give the most space to recent, relevant evidence. Keep older experience concise unless it demonstrates a skill the new role genuinely requires.
7. Education in the Wrong Place
Bad example: An experienced candidate opens with GPA, coursework, and student activities while current professional achievements appear halfway down the page.
Education is not a weakness. The issue is priority. Recent graduates may lead with education because it is their strongest evidence. Experienced candidates usually benefit from showing relevant work first.
Better: Order sections by what best proves your fit for the target role, not by a universal template.
8. Keyword Stuffing
Bad example: “Project management, project manager, Agile project management, stakeholder project management, project delivery management.”
Repeating phrases without context does not make the resume convincing. Recruiters may search for relevant terms, but those terms are more useful when connected to real work.
Better: “Coordinated a 10-person cross-functional project team using Agile planning, risk tracking, and weekly stakeholder reviews.”
Use the employer’s language when it accurately describes your experience. Do not copy an entire job description or insert keywords you cannot support.
9. Design That Competes With the Content
Bad example: Multiple columns, skill charts, decorative icons, text boxes, and important details placed inside graphics.
A visually polished resume can still be difficult to scan or parse. Greenhouse lists graphics, photos, text boxes, tables, headers, footers, and columns among elements that can contribute to unsuccessful parsing in its system. That does not mean every two-column resume fails everywhere; it means complicated layouts add avoidable risk. See Greenhouse’s unsuccessful resume parse guidance.
Better: Use a simple visual hierarchy, readable typography, consistent spacing, and real text. A single-column layout is the safest default when you do not know which system will receive the file.
10. Photos and Unnecessary Personal Details
Bad example: A U.S. resume includes a headshot, date of birth, marital status, full street address, and unrelated personal details.
Resume conventions differ by country. For a typical U.S. application, a photo and sensitive personal details are generally unnecessary and can distract from job-related evidence. Harvard’s resume guidance advises against including a photo in this context.
Better: Usually include your name, professional email, phone number, city or region, and relevant professional links. Follow local conventions and the employer’s instructions.
11. Sloppy Consistency and File Problems
Bad example: Mixed date formats, inconsistent punctuation, several bullet styles, broken links, tiny text, and a filename such as “resume-final-FINAL-v7.pdf.”
Small inconsistencies make the document harder to trust. They also suggest the candidate did not review the final file in the same form the employer will receive.
Better: Use one date style, one bullet style, consistent tense, a professional filename, and a final proofread after exporting. Follow the requested file format first. When no format is specified, PDF and DOCX are commonly supported, but the document should contain selectable text and display correctly after upload. Greenhouse documents its supported candidate upload formats.
What “ATS-Friendly” Should Actually Mean
“ATS-friendly” should not mean writing for a robot, hiding keywords, or chasing a universal score. There is no single ATS behavior shared by every employer.
A practical goal is simpler: reduce avoidable parsing problems and make relevant information easy to find. SAP SuccessFactors notes that resume parsing is not always 100% accurate, which is one reason clear structure matters. See SAP’s resume parsing documentation.
Use standard section names, keep important information in real text, avoid placing critical details only in headers or graphics, and check that copied text appears in the correct order. Then focus on the human decision: does the document make your fit obvious?
A 10-Minute Resume Audit
Before sending your next application, review the document in this order:
Target role: Can someone identify the role you fit within the first few seconds?
Top section: Does the summary or objective add specific information, or is it generic filler?
Recent experience: Does the newest relevant role receive the most attention?
Bullets: Do they show actions, context, scope, outcomes, or evidence?
Skills: Are they concrete and relevant to the job?
Relevance: Can any old, repeated, or unrelated detail be shortened?
Layout: Is the reading order obvious without decorative elements?
Consistency: Are dates, punctuation, capitalization, and tense standardized?
File check: Is the text selectable, are links working, and does the exported file open correctly?
Job match: Does the resume use accurate language from the job posting without copying or stuffing keywords?
You do not need to redesign the entire document every time. Fix the highest-impact problem first: unclear positioning, weak bullets, irrelevant content, or difficult formatting.
How Long Should a Resume Be?
One page is common early in a career, while two pages can be appropriate when the second page contains substantial, relevant evidence. The better rule is to use the shortest length that communicates your fit clearly.
Do not shrink the font or remove useful context just to satisfy an arbitrary page count. Do not keep weak or irrelevant content merely to fill a page. MIT’s guidance allows additional length for extensive experience or advanced qualifications. The target role and the value of the content matter more than a rigid formula.
Apply the Fixes Manually or With Joobee
Every change in this guide can be made manually. Start with a clean base resume, identify the evidence that matters for the role, and revise the sections that create the most friction.
Joobee helps when you need to turn your experience into a structured resume, tailor a version to a particular role, and keep track of which document you submitted with each application. The goal is not to “beat” software. It is to make your experience easier to read, find, and understand.
Frequently Asked Questions
Is a two-page resume bad?
No. A two-page resume is reasonable when both pages contain relevant evidence. A weak second page filled with repetition is a problem; a focused second page for an experienced candidate is not.
Should a resume include a photo?
For a typical U.S. industry resume, usually not. Conventions differ internationally, so use the expectations of the country and industry where you are applying.
Is PDF or DOCX better?
Follow the application instructions. Both formats are commonly supported, but individual employers and systems may have preferences. Confirm that the exported document preserves its layout and contains selectable text.
Does every bullet need a number?
No. Numbers are useful when they honestly communicate scale, speed, volume, money, time, or change. A strong bullet can also show complexity, ownership, audience, or a clear qualitative outcome.
Should I remove every objective?
Remove generic objectives. Keep a targeted objective when it provides necessary context, such as a precise career transition or early-career target that the rest of the resume does not make obvious.
Sources and Further Reading
The Bottom Line
A strong resume does not need to sound impressive in every sentence. It needs to make the right information obvious.
Show where you fit. Replace vague claims with evidence. Give the most space to the experience that matters now. Keep the layout clear enough that neither software nor a busy recruiter has to untangle it.
Your resume is not your entire career. It is the clearest, most relevant argument for the next conversation.
