How Recruiters Actually Read Your Resume (In Order)

Your resume gets read twice before anyone decides to call you: once by software, once by a human who's given it about seven seconds. Most job seekers write for neither. They write a document meant to be read slowly, top to bottom, by someone with nothing else to do. That person doesn't exist.

Pass One: The ATS Isn't Reading, It's Parsing

If you're applying through Naukri, LinkedIn Easy Apply, or a company's own portal (Workday, Greenhouse, Lever — common at Indian startups and MNCs alike), your resume doesn't reach a person first. It gets parsed into fields: name, phone, email, company names, job titles, dates, skills, education. The system then ranks or filters candidates based on keyword matches against the job description.

This isn't a sophisticated reading of your experience. It's pattern matching. A recruiter searching for 'Python' and 'SQL' in the ATS database will surface your profile only if those exact words appear in your resume text — not 'programming languages' or 'database management.'

What Breaks the Parse

• Text inside tables or text boxes — many ATS parsers skip these entirely
• Skills or job titles embedded in images, icons, or graphics
• Two-column layouts, which often get read left-to-right across columns instead of down each one, scrambling your job history
• Headers/footers containing your contact details — some systems don't scan these fields
• Unusual fonts or symbols used as bullet points instead of standard dashes or dots
• Dates written as 'Jan '22 - Present' instead of a parseable 'January 2022 - Present'

If your resume looks like a Canva template with sidebars and colour blocks, there's a real chance your last two jobs never make it into the system's database at all.

Pass Two: What a Human Recruiter Scans For, In Order

Once your resume clears the ATS filter or a recruiter searches the database and opens your profile, you get a skim — not a read. Recruiters who screen 150-200 applications for a single role aren't evaluating you fairly. They're eliminating you quickly. Here's the actual sequence, based on how eye-tracking and hiring research consistently describe resume scanning behaviour and how recruiters themselves describe their own process.

• 1. Current or most recent job title and company — is this person even in the right league (a Senior Analyst at Deloitte reads differently than an Analyst at a 20-person firm)
• 2. Career trajectory — are titles and responsibilities moving up, sideways, or nowhere over the last 3-5 years
• 3. Total years of experience against the job's stated requirement (2-4 years, 5-8 years, etc.)
• 4. Education — degree, institution, and whether it clears any filter (some companies still screen for specific universities or a minimum percentage/CGPA for early-career roles)
• 5. Keyword and skill match against the job description — tools, technologies, certifications
• 6. Employment gaps or short stints — anything under 12 months triggers a mental flag
• 7. Only then, if you've survived all of the above, do they read your actual bullet points

Notice what's not on that list until step seven: your carefully written accomplishment statements. Most candidates put all their effort into bullet-point wording and none into making the first six data points easy to find.

What This Means for How You Build the Resume

Put the scannable data where it gets scanned

• Job title and company name in bold, on the same line, top of each entry — not buried in a paragraph below
• Dates in the right margin or right after the company, in a consistent MMM YYYY format
• A one-line 'header' under your name with current title and total experience — e.g., 'Senior Product Manager | 6 years | B2B SaaS' — so trajectory is obvious in under two seconds
• Education section with degree, institution, and year, never buried at the bottom in tiny font if you're under 5 years into your career

Mirror the job description's exact language

If the JD says 'stakeholder management,' don't write 'worked with cross-functional teams.' If it says 'GST compliance,' don't write 'tax filings.' The ATS and the recruiter's own search bar both reward exact phrase matches, not synonyms you think sound better.

Format for parsing, not for design awards

• Single column, standard fonts (Calibri, Arial, Georgia)
• Save as .docx unless the application explicitly asks for PDF — some older ATS versions still parse Word files more reliably
• Use standard section headers: 'Work Experience,' 'Education,' 'Skills' — not 'My Journey' or 'What I Bring'
• Test it yourself: copy-paste your entire resume into a plain text file. If the job titles, dates, and companies still make sense in that stripped-down version, it'll survive most parsers

A resume that reads well to a human but confuses the ATS never reaches the human. One that parses cleanly but buries your best work under generic phrasing gets discarded in the seven-second skim. You need to build for both passes at once, in the order recruiters actually use — not the order you'd prefer to be judged in.