ResumeWorld
ResumeWorld
Screening guide
Data resumes converge on the same tool list, which makes keyword screening close to useless for this function. The distinguishing signal is influence: whether the analysis reached a decision-maker and changed something. A candidate who built twelve dashboards nobody opened has a longer resume and a weaker case than one who ran a single analysis that redirected a budget.
Signal
The strongest signal available. Look for analysis that reached someone with authority and changed what they did.
Clean benchmark datasets and messy production data are different skills. Only one of them is your job.
Being handed a question versus finding the right one to ask is the analyst/senior analyst boundary.
Pipeline ownership matters if the role includes it, and is noise if it does not. Decide before you screen.
Analysis that cannot be explained does not get used.
Noise
None of these is disqualifying on its own. Each is a reason to ask a question rather than assume an answer.
A tool list with no accompanying business outcome anywhere
Model accuracy figures with no mention of deployment or use
Projects that are all coursework or competition entries in a senior application
No indication of who consumed the work
Rubric
Write the criteria down before you look at anyone. An undocumented standard drifts, and it cannot be audited afterwards.
Evidence of framing and answering real business questions, not just executing given ones.
Working depth in the query, transformation and visualisation stack the role uses.
Experience with data of comparable messiness, scale and governance to yours.
At least one piece of work whose consequence the candidate can describe.
Evidence of presenting to and persuading non-technical decision-makers.
Next step
Ask the same ones of every candidate. Comparability is the whole point.
FAQ
Put it into practice
Score every application against the role you are actually hiring for, then get a ranked shortlist with the reasoning attached.
ExploreGet a competency signal with the application instead of discovering the gap in the second interview.
ExploreSee where the pipeline is stalling, how your criteria are behaving, and which roles are actually moving.
ExploreOther roles
Separating engineers who shipped something from engineers who were nearby when something shipped.
Read the guideCredentials are checkable, scope is not — and scope is what decides the hire.
Read the guideThe function where job titles mean the least and the actual scope varies the most.
Read the guideGo deeper
Most screening criteria are unfalsifiable. How to turn a job description into five to eight requirements you could actually verify from a document.
Read the guideStructured interviews predict job performance far better than unstructured ones. What structure actually means, and how to implement it well.
Read the guideKeyword matching is largely gone from modern screening. What to do instead of stuffing, and the four places exact wording still counts.
Read the guideDefine the criteria once, screen every application against them, and get a ranked shortlist with the reasoning attached.