Resume Mistakes That Get You Rejected in Seconds: Noise, No Impact, Irrelevant Experience
Shreya has worked as a senior HR professional at Amazon, Microsoft and TikTok. At her current company she has reviewed more than 500 resumes, and she shared the resume mistakes that get you rejected at a glance.
It usually isn’t a lack of ability. It’s focusing on the wrong things and never making your impact clear.
Resume mistake 1: an opening full of noise, with no clear focus
One example she saw opened with two degrees, fifteen courses and thirty tools. It looks like a lot at first, but there’s nothing to focus on.
Her advice: write one summary paragraph that names your technical skills and a concrete impact.
What I usually suggest on this point: pick the 3 to 5 tools you’re strongest in and put them in the top right corner of your resume.
If you already have enough experience, you don’t necessarily need a summary.
What matters is a clean layout, and experience that shows your expertise on its own.
Resume mistake 2: listing duties without results
She gave the example of someone who wrote “Worked with IT to maintain network security.” And then what? Did performance improve? Did risk go down?
Shreya’s message: go back to impact.
Her suggested version: “Updated systems, reducing downtime by 35%.”
For many people the hard part isn’t that they had no results. It’s that they never kept the numbers. Here is what I usually suggest you start doing now:
- Review your work at a fixed time every month and write a monthly achievements report.
- Ask the people who own the metrics (finance, PMs, for example). Better yet, find out at the very start of a project. It changes how much control you have over the project.
- For every project, identify the part you contributed. You don’t need to inflate it on your resume, but you don’t need to be overly modest either. Own your contribution, no more and no less.
Resume mistake 3: including experience unrelated to the role
One resume Shreya used as an example listed “Amazon shopper.”
It’s a deliberately extreme case, but her point stands: unless you’re applying for a related role and can make a solid case for it (UX, customer service or logistics, for example), this kind of experience doesn’t belong in the main body of your resume.
You can also group less relevant experience in an “Other Experience” section. For that experience, keep only the transferable skills, such as teamwork and project management, and keep it short.
I’d add one more common problem on top of this: order. If you’re changing careers, put the least relevant experience further down.
To a company, “I’m a professional with diverse experience” is a far more appealing story
than “I’m a career changer who has held different roles and is new to this field.”
When your resume gets accepted, that is recognition of your experience.
Further reading: A good resume is one that gets a response
Resume mistake 4: an impressive-sounding project with no clear goal
Her example: “Built an AI model for sentiment detection.” It sounds strong, but how accurate is it? Did it ship? What problem did it solve?
What she wants to see is a sentence like this:
“Improved sentiment detection accuracy by 20% and cut processing time by 15%.”
Remember: a project with an impressive name isn’t enough. What counts is that you can quantify the change.
Shreya puts it bluntly:
“People don’t get rejected for lacking skills. They get rejected for not making clear what impact they created.”
Why these resume mistakes still get you rejected
A lot of this sounds like advice you’ve heard many times. But when you’re actually writing your resume, it’s still easy to fall into these traps.
Job hunting isn’t easy, and these lessons can help you make a few fewer mistakes.
Original post: linkedin.com/feed…