DEV Community

Cover image for Your Resume Gets About 7 Seconds. Here's What Gets Read.
Prasuk
Prasuk

Posted on Originally published at Medium

Your Resume Gets About 7 Seconds. Here's What Gets Read.

A recruiter with 300 applications doesn't read your resume. They scan it. An eye-tracking study by a large job site found the first screen got about 7 seconds on average. Studies differ on the exact number, but every one agrees on the shape: a fast skim of the top, then a decision.

So the question isn't "is my resume good?" It's "what can someone learn about me in 7 seconds?"

In 30 seconds

  • The top third of page one decides almost everything
  • Lead with what you built and the result, not adjectives
  • One page if you have under 5 years of experience
  • Use the 10-minute fix below before your next application

Where the eyes actually go

In 7 seconds, a scanner reads roughly:

  1. Your name and current title
  2. Your latest role: company, title, dates
  3. The first one or two bullet points
  4. Your skills line, if it's near the top

Everything below the fold is read only if the top earned it.

The before-and-after (an example)

Before (what most resumes look like):

Results-driven and passionate software developer with strong problem-solving skills and a team-player attitude, seeking a challenging role in a dynamic organisation.

  • Responsible for backend development
  • Worked on various APIs
  • Participated in code reviews

After:

Backend developer · Node.js, Postgres · 2 years at an early-stage startup

  • Built the order API that handles ~3,000 orders a day; cut average response time from 900 ms to 180 ms
  • Moved payments to a queue, ending double-charges during traffic spikes
  • Shipped a WhatsApp bot for order updates; 40% of customers now use it instead of calling

Same person. Same job. The second one gets a call.

The pattern: verb + what you built + a number or result.

The 10-minute fix

Minute Do
0 to 2 Delete the "objective" paragraph. Replace with one line: role · main skills · years/stage
2 to 6 Rewrite your top 3 bullets: verb + what you built + result
6 to 8 Move skills to the top third. Cut to the 8 to 10 you'd be happy to be tested on
8 to 9 Add one link: a live project, repo or write-up
9 to 10 Export as a PDF named Firstname-Lastname-Role.pdf

Freshers: what to put at the top

No work experience? Your top third should be projects, not your school marks.

  • 1 line: "Final-year CSE student · React, Node · 3 shipped projects"
  • Best project first: what it does, who uses it, one number ("used by 120 students in my college")
  • Hackathon results in the top half, if you have any
  • Education goes below projects. Include CGPA only if a company asks for it or it's strong

7 things to cut today

  • ❌ "Objective" paragraphs
  • ❌ "Results-driven", "passionate", "hard-working"
  • ❌ A photo, date of birth, marital status (most tech companies don't need them)
  • ❌ Skill bars ("Java ●●●●○"). Nobody knows what 4 dots means
  • ❌ 25-item skill lists
  • ❌ "References available on request"
  • ❌ Two pages when you have under 5 years of experience

Save this: top third = role line + 3 result bullets + skills + one link. Everything else is supporting detail.

The resume is the trailer. Your work is the film.

A great resume gets you the call. What gets you the job is proof: projects people can open, write-ups that show how you think.

Disclosure: we build InfiniteInterfaces, a free builder network. Your profile, posts, blogs and hackathon results go with every application, so the recruiter sees the film, not just the trailer. There's also an AI resume builder and polish tool, cover letters and AI interview practice. Candidates never pay.

👉 Build your profile free and attach your work to every application.


The 7-second figure comes from a 2018 eye-tracking study by a large job site (average initial screen time about 7.4 seconds). Treat it as a rough guide, not a rule.

Top comments (1)

Collapse
 
ayushdhanani369 profile image
Ayush Dhanani •

Your before-and-after is the strongest part. The 900 ms to 180 ms line does more work than the whole objective paragraph it replaced. One thing I would add: the top third should not be the same for every application. A posting that asks for payments work and a posting that asks for API performance want different bullets first. I build Aladdin, a job agent, and the resumes that get read are the ones where the top bullets match the specific posting. Same person, same facts, different order.