Written by the MiraHire team · Last updated July 2026
Resume Screening Checklist: Copy It, Use It on Your Next Role
A resume screening checklist does one job: it makes you judge every candidate against the same criteria, in the same order, before your gut gets a vote. Here is a complete one you can use today — criteria, red flags, a scoring rubric, and the step-by-step passes.
Why write the checklist before you open a single resume
Most small teams screen resumes from memory: read a few, form an impression, and let that impression drift as the pile grows. The result is that resume #4 and resume #74 get judged by different standards — and with application volumes having surged in recent years, the pile grows fast. Writing your criteria down first fixes three things at once: it keeps your bar consistent, it makes your decisions explainable to co-founders and candidates, and it stops the most polished resume from beating the most qualified one.
Step 1: Split criteria into must-have vs nice-to-have
Before screening, write two short lists. Be strict about which list each item belongs to.
- Must-haves (3–5 maximum). Requirements the hire genuinely fails without. Each one should be observable on a resume — “has shipped a production web app” works; “is a self-starter” doesn’t. If a candidate is missing one, they’re out, no matter how good the rest looks.
- Nice-to-haves (up to 5). Things that make a candidate stronger: a specific tool, industry exposure, a relevant side project. These add points but should never eliminate anyone.
- The honesty test. For each must-have, ask: “Would I really reject an otherwise great candidate over this?” If the answer is no, move it to nice-to-have. Bloated must-have lists are one of the most common ways good candidates get screened out.
Step 2: First pass — the 2-minute knockout scan
Go through every resume once, quickly. You’re only answering yes/no questions:
- Eligibility basics. Location, time zone, or work authorization — whichever actually apply to this role.
- Must-haves present? Check each of your 3–5 must-haves. Missing one = out. Unclear = keep for the second pass and note the question.
- Seniority roughly right? Not exact years — just whether the scope of their past work is in the neighborhood of what this role demands.
- Aimed at this role? The resume should plausibly connect to the job you posted. A generic blast with zero relevant experience is an easy no.
Don’t rank anyone yet. The first pass exists only to shrink the pile without burning judgment on candidates who were never viable.
Step 3: Second pass — the evidence check
Now spend 5–10 minutes on each survivor, looking for proof rather than claims:
- Concrete outcomes. Numbers, shipped products, revenue, users, deadlines met — anything measurable that they personally moved.
- Scope and ownership. “Led,” “built,” and “owned” backed by detail beat “participated in” and “was responsible for.”
- Transferable skills. A candidate from an adjacent industry or stack who solved the same class of problem is often stronger than a keyword-perfect match. Look for the underlying skill, not the label.
- Trajectory. Growing responsibility over time, even across different titles or companies, is one of the most telling signals a resume offers.
Red flags (and how to treat them)
- Claims without evidence. Senior titles with no concrete accomplishments underneath. This is the most reliable red flag on any resume.
- Buzzword density. Long skills lists and adjectives with no numbers, projects, or artifacts to back them up.
- Title/responsibility mismatch. A “Head of” title describing individual-contributor work, or vice versa. Worth a direct question if they otherwise clear the bar.
- Timeline inconsistencies. Overlapping roles or dates that don’t add up. Usually sloppiness, occasionally worse — either way, ask.
- Handle with care: gaps and short tenures. These are questions, not verdicts. Layoffs, caregiving, and bad-fit companies are common and say little about ability. Auto-rejecting on them costs you real candidates.
A simple scoring rubric
You don’t need a complicated model. This rubric takes seconds per resume and produces a rankable number:
- Each must-have: 0, 1, or 2. 0 = absent (candidate is out), 1 = present but thin evidence, 2 = present with strong evidence.
- Each nice-to-have: 0 or 1. Present or not. No partial credit — it keeps you fast and consistent.
- Total and rank. Sum the points and sort. With 4 must-haves and 4 nice-to-haves, top score is 12; interview from the top down.
- One-line rationale. Next to each score, write one sentence on why. Future-you (and your co-founder) will need it.
The rubric’s value isn’t precision — it’s determinism. The same resume should get the same score no matter what mood you’re in or where it sat in the pile.
Running the process end to end
- Calibrate on the first ten. Screen ten resumes, then re-read your criteria. If a must-have is knocking out everyone or no one, fix the criterion — not your standards mid-stream.
- Batch, don’t trickle. Screening in one or two sittings keeps your bar level. Trickle-screening as applications arrive quietly favors whoever applied first.
- Log every decision. A spreadsheet with name, score, and the one-line rationale is enough. It’s your defense against re-litigating the same resumes twice.
- Move fast on the top of the list. The candidates who score highest with you are scoring highest elsewhere too.
Where the manual checklist breaks — and what to do about it
This process works beautifully at 30 applicants. At 150 or more, the first pass alone can swallow a working day or two, and consistency erodes exactly when it matters most (see what to do when you have too many applicants).
This is the specific gap MiraHire was built for — and it starts one step earlier than the resume pile. A short guided conversation about what you’re building turns into a concrete role profile: your must-haves and nice-to-haves, written down properly, before you screen anyone. Then it applies that resume screening checklist to every candidate with explainable, evidence-based scoring: matching evidence, transferable skills, and risk signals shown next to each score, ranked by fit. It’s deterministic — the same resume always produces the same result — and human-in-the-loop: it informs, your team decides. Candidates come in via a shared apply link or one-click import, and every resume is parsed into the same structured profile so you compare like with like.
It’s free to start on one real role, no credit card, and paid plans start at $39/month.
Free on one role · no credit card · your data is hosted in the US.
FAQ
How long should resume screening take per resume?
Plan on 2–3 minutes per resume for a first knockout pass against your must-have criteria, and 5–10 minutes for a second evidence pass on the candidates who clear it. If you have hundreds of applicants, screening software can run the first pass for you so you spend your time on the shortlist.
What is the difference between must-have and nice-to-have criteria?
Must-haves are the 3–5 requirements the hire genuinely fails without — if a candidate is missing one, they are out regardless of everything else. Nice-to-haves make a candidate stronger but should never eliminate anyone. Most screening mistakes come from treating nice-to-haves as must-haves.
What are red flags when screening resumes?
The most reliable red flags are claims without evidence: big titles with no concrete outcomes, buzzwords with no numbers or artifacts, and responsibilities that don’t match the seniority claimed. Treat things like short tenures or employment gaps as questions to ask, not automatic rejections.
Can AI apply a resume screening checklist for me?
Yes. Tools like MiraHire turn a short conversation about your role into concrete criteria, then score every resume against them with matching evidence, transferable skills, and risk signals shown next to each score. The same resume always gets the same result, and your team makes the final call.