← Back to Blog
guideAuthor: DeepResume TeamRead: 8 minPublished: 2026-05-11

HR Only Spends 10 Seconds on Your Resume? 5 Mistakes That Get Your Resume Instantly Rejected

Yes, HR really does spend very little time on each resume. Not because they don't care, but because most of the information on a resume at the initial screening stage is noise. This article breaks down the screening logic from an HR's perspective, showing you which mistakes will knock you out the moment they're spotted.

#HR#Resume Screening#Application Tips#Resume Optimization

The saying "HR only spends 10 seconds on a resume" gets thrown around a lot. The reality is a bit more nuanced—

Yes, at the initial screening stage, HR genuinely doesn't spend long on each resume—typically somewhere between 30 seconds and a minute. But that's not because they're not thorough. It's because: a single role might get over 200 applications, and the goal of initial screening is to identify "people worth moving forward," not to "fully assess who you are."

At this stage, the objective is completely different. HR is hunting for "match signals," not doing a comprehensive evaluation. If you're not sending the right signals, even the best experience won't make it past the first gate.

Here are the 5 mistakes that most frequently cause HR to pass on a resume during initial screening. Not "might lose you some points"—I'm talking "see it, next resume."


Mistake 1: Match Signals Are Completely Off

This is the most fatal—and the most common—problem.

HR has a JD (job description) with clear "hard requirements." The first thing they do in screening is keyword matching.

Example. The JD requires:

  • 3+ years of B2B product experience
  • Proficient in SQL and data instrumentation
  • Experience with growth experiments

Your resume:

  • 4 years of experience listed, but doesn't distinguish B2B vs B2C
  • No mention of SQL
  • Mentions "ran A/B tests" but doesn't say "growth experiments"

From HR's perspective: three hard requirements, you've clearly hit one (years of experience), and the other two are uncertain. In a pool of 200 resumes, there are other candidates who clearly hit all three—your resume gets set aside.

This doesn't mean you're not qualified. It means you didn't send the signal.

How to avoid this: Before applying to any role, circle every hard requirement in the JD, then find the corresponding experience in your resume and align it. Not fabricating—just making sure the information actually gets seen. If you genuinely used SQL but didn't write it down, that's the equivalent of having water in your cup but not being able to pour it out.


Mistake 2: The Top Half of Your Resume Has Zero Useful Information

When HR opens a resume, their eyes naturally land on the top half of the first page (on mobile, the first two screens). If that space doesn't answer "who is this person" and "are they worth reading further," the odds of them scrolling down drop off a cliff.

Here's a classic example of "wasting the top half":

Name | Address | Phone | Email | Personal Website | GitHub
Education: XX University
Skills: Python / Java / SQL / HTML / CSS

It's not that this information is wrong. It's that the entire top half is "basic info" with zero material for making a judgment call. HR has no idea what direction you work in, what level you're at, or what you've accomplished.

How to avoid this: If you have less than 3 years of experience, the top half should show Education + Core Skills + a one-line positioning statement (e.g., "Backend engineer with 3 years of experience, familiar with microservices architecture"). If you have 3+ years, lead directly with a summary of your most recent role's key achievements.


Mistake 3: Experience Descriptions Are All Duties, No Outcomes

This one is everywhere, across all experience levels.

Responsible for daily operations and incident handling of the XX system.
Participated in requirements review and technical design discussions.
Completed other tasks as assigned by leadership.

Read these three lines back. HR has absolutely no way to assess your capability level. They describe the basic duties of a role, not what you achieved in that role.

Duties are what anyone in the position could write. Outcomes belong to you.

Compare:

Responsible for XX system operations → Led daily operations of the XX system, reduced mean time to recovery (MTTR) from 2 hours to 30 minutes, and documented 12 incident handling SOPs.

The second version contains at least 5x the information. HR can instantly gauge this person's ability and level.

How to avoid this: After writing each bullet point, ask yourself one question: "Could someone else in the same role write this exact line?" If the answer is "yes, they could," your description is too generic. Add specific outcomes and numbers.


Mistake 4: Resume Is Too Long—a Little Bit of Everything

Resumes over 2 pages see a significant drop in initial screening pass rates. The reason is simple: HR didn't find enough "usable information" within those 30 seconds.

The most common causes of bloat:

  • High school and college experiences (unless you're a new grad, cut everything before university)
  • Ancient projects from 7–8 years ago (keep only the valuable ones from the last 5 years)
  • 3–5 bullet points per project (compress to the 2–3 most critical ones)
  • Skills list with 20+ items (reads as "knows a little about a lot = deep in nothing")

How to avoid this: Learn to cut. New grads: keep it to 1 page. 1–3 years: 1 page. 3–5 years: 1–1.5 pages. Kill the oldest projects, drop the weakest skills, remove anything that's just padding.


Mistake 5: Formatting Hurts Readability

This shares the same underlying logic as ATS friendliness—HR at the screening stage is also speed-scanning, not reading every word.

These formatting issues significantly lower reading efficiency:

  • Font too small (below 10pt)
  • Line spacing too tight (feels like a wall of text)
  • Not enough separation or whitespace (sections crammed together)
  • Using paragraph indentation instead of section headers (HR can't find what they're looking for during a quick scan)

The safest formatting approach: Font 11–12pt, line spacing 1.15–1.5x, clear separation between sections, bullet points instead of indented paragraphs.


Summary: What HR Is Actually Looking for at Initial Screening

Here it is in one sentence: HR is looking for the candidate they can match in 10 seconds—not because you're exceptional, but because your resume wears its value on its face.

At the screening stage, HR wants to find:

  1. This person's work aligns with the direction we're hiring for (experience match)
  2. This person's capability level matches what we expect (seniority fit)
  3. This resume reads smoothly with no extra effort required to parse it (good information accessibility)

Nail these three, and even if your experience isn't the shiniest in the pile, you've at least made it into the "worth spending 5 minutes on" pool.

DeepResume's free diagnosis scores your resume across four dimensions: quantified achievements, keyword coverage, ATS friendliness, and content completeness. If you're not sure how your resume looks through an HR lens, give it a try.

→ Get Your Free Resume Diagnosis