The hardest part of a stalled job search is that nobody tells you why. You apply, you wait, you hear nothing, and you assume the market is brutal or you are underqualified. Usually it is neither. The resume just describes the work badly enough that no one can tell you did it well. Even Harvard's research on hiring found that 88% of employers admit their systems screen out qualified people, often over exactly the avoidable resume issues below.
These are the seven mistakes I see most, roughly ordered by how much they hurt. None of them is about your ability. All of them are fixable in an afternoon.
1. No numbers
The worst offender by a wide margin. "Improved performance," "built features," "managed the database", every one of these describes a person who was present, not one who delivered. They are also indistinguishable from what every other applicant wrote. Add a real figure to most bullets: "cut report generation from 45s to 3s," "shipped 8 features used by 15K users." If you do not have exact data, estimate honestly; "around 50K users" carries infinitely more weight than silence. This single change moves your interview rate more than anything else on this list.
2. Weak opening verbs
"Responsible for," "worked on," "helped with" are dead weight, and they sit in the worst possible spot, the first word of each bullet, which is exactly what a skimming recruiter reads. Swap them for verbs that name an action: built, designed, cut, migrated, automated, led. The verb sets the tone for the entire line, and "responsible for the payment system" reads as a job description while "rebuilt the payment system" reads as a person.
3. A 40-tool skills dump
A comma-separated wall of every technology you have ever touched signals the opposite of competence; it signals that you cannot tell what matters. Categorize your skills, lead each category with the tools the role actually wants, and drop the filler nobody is impressed by, Microsoft Word does not belong next to Kubernetes. Applying for a Python role? Python is the first word in your languages line.
4. Same resume everywhere
One generic resume blasted at every posting is the slow road to silence. Tailoring lifts callback rates by about 30%, and it takes ten minutes: pull the top required skills from the posting, make sure they appear in your resume in the posting's exact words, and reorder your bullets so the most relevant experience leads. The ATS matches literally, so "REST APIs" and "web services" are different strings to it even though they are the same thing to you.
5. Filler nobody reads
"References available upon request" (assumed), generic hobbies, skill self-ratings like "Python: 8/10," high-school details a decade out of date. Every line on the page is competing for a recruiter's seven seconds, so each one has to answer a single question: does this make them likelier to call me? If the answer is no, it is stealing space from something that would, and it should go.
6. Formatting the parser chokes on
Multi-column layouts, tables, text boxes, contact details stranded in the header, infographic templates, all of these can scramble when an ATS flattens your resume to text. A two-column layout alone can drop roughly half your skills section in parsing. The fix is boring and reliable: single column, a standard font, contact information in the body of the document, saved as a clean PDF unless the posting asks for Word.
7. Typos in tech names
"Pyhton," "Javascipt," "PostgeSQL." A single one looks careless; three tell the reader you never proofread your own most important document, which is a brutal signal for a job that demands attention to detail. Run a spellchecker, ask a friend to read it, and read it once yourself from the bottom up so your brain stops autocorrecting what it expects to see.
| Mistake | Damage | Fix time |
|---|---|---|
| No numbers | High | 30 min |
| Weak verbs | High | 15 min |
| Skills dump | Medium | 10 min |
| No tailoring | Medium | per app |
| Filler | Low | 10 min |
| Formatting | Medium | 20 min |
| Typos | Fatal | 10 min |
The whole table adds up to an afternoon of work, and most of it is one-time. Fix the base resume once, then the only per-application cost is the ten minutes of tailoring, which is the highest-return ten minutes in the entire job search.
Key takeaways
- A stalled search is usually a communication problem, not a qualification one.
- Numbers and strong verbs are the biggest, fastest wins; start there.
- Tailoring per posting lifts callbacks about 30% and takes ten minutes.
- A single tech-name typo can sink an application; proofread from the bottom up.
FAQ
Why am I not getting interviews despite being qualified?
Most often the resume is hiding your qualifications behind duty bullets with no numbers, weak opening verbs, and no tailoring to the posting. Even Harvard's research found 88% of employers admit their systems screen out qualified people. The fixes take an afternoon and matter more than adding another skill to the pile.
What is the single most damaging resume mistake?
No quantified impact. Bullets without numbers read as generic and are indistinguishable from every other applicant's. Adding a real metric to most of your bullets is the highest-leverage change you can make, and it moves your interview rate more than anything else.
How much does tailoring to each job actually matter?
A lot. Tailored resumes see roughly 30% higher callback rates, and the work is small: pull the posting's top keywords, make sure they appear in its exact wording, and reorder your bullets so the relevant experience leads. Ten minutes per application is usually enough.
Do I really need to fix formatting if my resume looks nice?
Yes, because "looks nice to a human" and "parses cleanly for an ATS" are different things. Multi-column layouts and tables can lose half your skills section when the parser flattens the file. A single-column PDF with standard headings looks professional and survives parsing, which is the combination you want.
Want to know which of these your resume makes? Get a Resume Roast for blunt section-by-section feedback, or run an ATS check.