ResumeWorld
Screening guide
"Operations Manager" describes a two-person startup generalist and a person running a hundred-strong logistics function equally well. No other function has this much title inflation and deflation at once, which means screening operations resumes on title is close to random. The rubric has to reach past the title to the scope: what moved, how much of it, and who decided.
Signal
Headcount, budget, systems owned and decisions made. The title tells you almost nothing on its own.
Keeping a process running and making it better are different capabilities. Most resumes describe the first and imply the second.
Operations works through other teams. Evidence of influence without authority is the core signal.
Who administered the systems, versus who used them.
Transaction, order or case volumes handled — the closest thing this function has to a comparable metric.
Noise
None of these is disqualifying on its own. Each is a reason to ask a question rather than assume an answer.
Responsibilities listed as a job description with no outcomes
Senior title with a scope description that matches a coordinator role
Process improvements claimed with no before-and-after
No indication of who or what the candidate was accountable for
Rubric
Write the criteria down before you look at anyone. An undocumented standard drifts, and it cannot be audited afterwards.
Headcount, budget and volume in the range the role carries.
At least one process the candidate measurably changed.
Administration-level experience with comparable tooling.
Delivery through teams the candidate did not manage.
Sector exposure where the operational constraints are genuinely sector-specific.
Next step
Ask the same ones of every candidate. Comparability is the whole point.
FAQ
Put it into practice
Turn a pile of applications into a ranked shortlist where every inclusion and every rejection has a reason attached.
ExplorePublish a branded application portal per role so applications arrive structured instead of as inbox attachments.
ExploreSee where the pipeline is stalling, how your criteria are behaving, and which roles are actually moving.
ExploreOther roles
Every project on the resume finished on time. The useful question is what happened on the ones that did not.
Read the guideCredentials are checkable, scope is not — and scope is what decides the hire.
Read the guideHigh-volume applicant pools where the differentiating signal is judgement, not tooling.
Read the guideGo deeper
How to screen hundreds of applications for one role without quality drifting: write criteria first, split the work, use bands, and sample what you reject.
Read the guideNot every job produces a metric. Find honest numbers in your work, use scope when there are none, and avoid inventing figures an interviewer will question.
Read the guideA job description is a screening tool. Requirement inflation, missing salary and vague scope all cost you the candidates you wanted — here is what to change.
Read the guideDefine the criteria once, screen every application against them, and get a ranked shortlist with the reasoning attached.