What recruiters look at first on your resume
The fields a first pass lands on, what gets a resume set aside, and what to change.
The first pass is a skim, not a read
The one eye-tracking study anybody can point to here is TheLadders': 30 professional recruiters in the United States, tracked over ten weeks on real resume-review tasks, first run in 2012 and updated in 2018. It found the first pass lasts about six to seven seconds, and that roughly 80% of that attention goes to a small set of fields: your name, your current title and company, your previous titles, the start and end dates on each role, and your education (source: TheLadders eye-tracking study, 2012 and 2018, n = 30, US only).
Treat that as indicative rather than as law. Thirty US recruiters is a small, old, non-Indian sample, and the study measured where eyes moved, not who got rejected. It is evidence about attention, not about outcomes, so anyone repeating it as a rule about how fast you get turned down has added something the study never said.
What it does support is worth having: the first pass is a skim, it lands on a few structural fields, and when those fields are hard to find you are making a reader work before they have any reason to.
What gets a resume set aside
The recruiter never found it. Before anyone skims anything, someone has to search. If the recruiter searched "Kubernetes" and your resume says "container orchestration", you were never in the result set. This is the failure that costs the most and shows the least: there is no rejection email for a search you did not appear in.
No clear title match. If the role is "Senior Java Developer" and your resume only ever says "Module Lead", a reader has to translate before they can place you, and a title search does not find you at all. Name the target title wherever it is honest to do so.
Length that hides the point. Career sources agree on the shape even where they differ on the exact count: under five years of experience, one page; mid-career, one to two; India-specific guides allow two to three for experienced candidates (sources: scale.jobs and BeamJobs on length by experience, Naukri's own resume length guide for India). The reason is not that long documents get punished. It is that the relevant part gets harder to find.
Walls of text. Bullets get scanned, paragraphs get skipped. Weight your most recent role heaviest, at five to eight bullets, and cut older roles to one or two lines each; roles from more than ten to fifteen years ago can usually go entirely (sources: BeamJobs and rocket-resume on bullets per role and recency weighting).
A summary that says nothing. "A motivated professional with X years of experience looking for a challenging role" gives a reader nothing to act on. Name the domain, the stack, and what you own.
What to do about it
- Put your most relevant experience and skills in the top half of page one.
- Match your summary to the target title and two or three core requirements from the JD.
- Use the JD's exact keyword wording wherever you genuinely have the experience.
- Keep the layout single column and the dates on every role unambiguous.
Tailor your resume to the JD now and see which of the job's keywords you already cover.
FAQ
Does a longer resume hurt my chances?
Length itself is not the problem; burying the relevant part is. Career sources put a mid-career IT resume at one to two pages, and Indian guides allow up to three for experienced candidates. If page three exists because everything you did in 2009 is still on it, cut 2009 rather than shrinking the font.
What if I have a lot of certifications?
List them in a Certifications section. Do not scatter them through your bullets or your summary. A dedicated section is easier to find in a skim and easier for a parser to segment.
Ready to put this into practice?
Tailor my resume, free