What to Look for in a Resume: A Practical Guide for Hiring Managers

Most resume advice is written for candidates. This guide is for the person on the other side of the table — the hiring manager or recruiter who needs to evaluate 50, 100, or 200 resumes and make defensible decisions about who to interview.

The challenge isn't reading resumes. It's reading them consistently, efficiently, and for the right signals. Here's what actually matters.

The two-pass approach

Trying to do a deep evaluation of every resume is a recipe for fatigue, inconsistency, and wasted time. Instead, use a two-pass approach:

Pass 1 (30–60 seconds per resume): Does this candidate meet the minimum requirements? This is a yes/no filter, not a quality assessment. You're checking for dealbreakers and basic qualification alignment.

Pass 2 (3–5 minutes per resume): For candidates who passed the first filter, do a structured evaluation against your scoring criteria. This is where you assess quality, depth, and fit.

This approach lets you screen 100 resumes in about 2 hours (Pass 1) and deeply evaluate the 20–30 strongest candidates in another 2 hours (Pass 2), rather than spending 5 minutes on every single resume regardless of fit.

What to look for in Pass 1

Relevant experience alignment

The first thing to check: does the candidate's experience align with the core requirements of the role? Not a keyword match — a genuine alignment.

A candidate applying for a data engineering role who has spent 5 years building ETL pipelines is aligned, even if their resume says "data pipeline developer" instead of "data engineer." Conversely, a candidate whose resume mentions "data" heavily but whose actual work was data entry is not aligned, despite the keyword match.

What to look for: Job titles and descriptions that suggest genuine experience in the domain, not just keyword density.

Minimum qualifications

If you've defined 3–5 must-have requirements in your job description (and you should have), check each one:

• Required certification present? ✓/✗
• Minimum experience level met? ✓/✗
• Required technical skills evident? ✓/✗
• Legal requirements met (right to work, license)? ✓/✗

A candidate who doesn't meet a genuine must-have requirement shouldn't advance to Pass 2, regardless of how impressive the rest of their resume looks.

Obvious red flags

In Pass 1, you're not looking for subtle signals — you're looking for clear disqualifiers:

• No relevant experience at all — the resume doesn't connect to the role in any meaningful way
• Critical missing information — no dates, no company names, no descriptions of what they actually did
• Application errors — wrong company name, generic cover letter clearly meant for a different role

Note: short tenures, employment gaps, and unconventional career paths are not automatic red flags. These require context that Pass 2 provides.

What to look for in Pass 2

Impact, not activity

The difference between a good resume and a great one is the difference between activity and impact:

• Activity: "Managed the marketing team"
• Impact: "Built and led a marketing team from 2 to 8 people, increasing qualified leads by 180% over 18 months"

Look for evidence that the candidate achieved something, not just that they were present. Quantified results (revenue, growth percentages, team size, project scale) are the strongest signals, but qualitative impact statements also count: "Led the migration from on-premise to cloud infrastructure, reducing deployment time from 2 hours to 15 minutes."

Warning: Not all roles lend themselves to quantified achievements. A customer support representative may not have "increased revenue by 40%" — but they might have "maintained a 98% customer satisfaction rating across 200+ tickets per month." Evaluate impact in the context of the role.

Progression and growth

Career trajectory reveals ambition and capability:

• Increasing responsibility — promotions within companies, expanding scope, larger teams or budgets
• Skill deepening — evidence of growing expertise in a domain rather than shallow exposure to many domains
• Deliberate career moves — lateral moves that make strategic sense (e.g., moving from a large company to a startup to gain broader experience)

Progression doesn't have to be vertical. A candidate who has deepened their expertise over 10 years at the same level may be more valuable for a specialist role than someone who was promoted quickly through generalist positions.

Relevance of experience

Not all experience is equally relevant. Five years in a directly related role at a comparable company is stronger evidence than ten years in a tangentially related role at a very different type of organisation.

Consider:

• Industry relevance — have they worked in the same or similar industry?
• Scale relevance — have they worked at a similar-sized organisation?
• Technical relevance — have they used similar tools, technologies, or methodologies?
• Customer relevance — have they served a similar customer base?

A candidate who ticks all four is a strong fit. A candidate who ticks one or two may still be strong, but will need more ramp-up time.

Writing quality

The resume itself is a work product. How a candidate presents their experience tells you something about their communication skills, attention to detail, and professionalism.

Look for:

• Clarity — can you understand what they did and what they achieved?
• Conciseness — have they prioritised the most relevant information?
• Accuracy — are there typos, grammatical errors, or inconsistencies?
• Structure — is the resume well-organised and easy to scan?

Writing quality matters more for some roles (communications, management, client-facing) than others (engineering, trades). Weight it accordingly.

What's missing

Sometimes the most telling aspect of a resume is what's absent:

• No metrics for a sales role — a salesperson who doesn't quantify their performance may not have strong numbers to share
• No progression over many years — a candidate with 15 years of experience at the same level may indicate a performance ceiling (or may indicate contentment in a specialist role — context matters)
• Vague descriptions for recent roles — detailed descriptions of old roles but vague descriptions of recent ones may indicate the recent experience isn't strong

Absence of information isn't automatically negative, but it's worth noting for interview follow-up.

Common evaluation mistakes

Overweighting prestigious employers

"They worked at Google" is not a qualification. Large, prestigious companies have thousands of employees across hundreds of roles. The candidate's specific experience and achievements matter more than the logo.

Penalising employment gaps

Employment gaps have dozens of explanations: caregiving, health, study, travel, personal projects, visa transitions, economic downturns. An 18-month gap between roles tells you almost nothing about a candidate's capability. If the experience before and after the gap is strong, the gap is irrelevant.

Confusing length with quality

A longer resume is not a better resume. A concise two-page resume with clear, relevant experience is stronger than a five-page resume padded with every task the candidate has ever performed. Penalise padding, not brevity.

Keyword dependency

Scanning for keywords is the weakest form of resume evaluation. A strong candidate who describes their experience differently from your job description will be missed by keyword scanning. "Led revenue operations" and "managed sales pipeline" describe similar work — keyword matching catches only exact matches.

This is one reason AI screening tools can be more effective than manual keyword scanning — good ones use semantic matching to understand that different words can describe the same experience.

Using AI to support resume evaluation

AI resume screening tools are most valuable for Pass 1 — the initial filter that identifies which candidates merit a deeper look. A tool that can match resumes against your job description using semantic understanding (not just keywords) and produce evidence-backed scores saves hours of manual screening.

The key is transparency. Any AI tool you use should show why it scored each candidate the way it did, linking scores to specific resume content. This lets you verify the AI's reasoning and catch any errors.

HireIQ does this: paste your job description, upload resumes (up to 50 at once), and get a ranked shortlist where every score is tied to specific evidence in the resume. You see the reasoning, not just a number.

It handles Pass 1 in seconds, so you can spend your time on Pass 2 — the deep evaluation that requires human judgement.

The bottom line

Reading resumes well is a learnable skill. The key principles:

1. Use a two-pass approach — filter first, evaluate second
2. Look for impact, not activity — what did they achieve, not just what did they do?
3. Evaluate relevance in context — industry, scale, technical, and customer relevance all matter
4. Watch for what's missing — absence of information is a signal worth noting
5. Be consistent — use the same criteria for every candidate, in the same order

Whether you screen manually or use AI assistance, these principles produce better, more defensible hiring decisions.

Try HireIQ free → — evidence-backed resume screening in seconds.