Hiring Checklist
A hire should solve a defined problem. Read the checklist, a worked review, and why a role without tasks produces a search without a target.
Hiring often starts with a vague pressure — the team is busy — and turns into a job description before anyone has defined the work. The re:Work hiring material treats hiring as a practice to examine, as O*NET's task descriptions help state what a role involves, as the hiring trade-offs article treats capacity versus clarity, as the decision-memo article requires for a specific question, as the publication standard forbids guaranteed outcomes.
Direct answer:
Define the tasks, the criterion for success, and the evidence you will accept before opening a search.
Google re:Work provides hiring practice, and O*NET provides role definitions. The boundary: this is educational orientation, not legal or HR advice — employment obligations vary by jurisdiction, as the AI HR screening article treats formal duties, as the publication standard forbids guaranteed outcomes.

The checklist
State the problem. What work is not getting done, and why is a person the answer, which the hiring trade-offs article asks, as the decision-memo article requires for a specific question, as Engineering Management: Hiring, Culture, Metrics, and Career Ladders treats capacity, as the value-proposition article argues for clarity, as the rubric article requires concrete criteria.
Define the tasks. What will this person actually do, which O*NET's descriptions help ground, as the re:Work material advises, as the team-culture article warns about implicit norms, as the data-governance article requires for a dated definition, as the rubric article requires for criteria, as the decision-memo article requires for a record.
Choose the evidence. What will predict success in those tasks, which the behavioral-interview article advises, as the rubric article requires for concrete criteria, as the causal-inference article warns about weak proxies, as the AI HR screening article treats formal duties, as the risk article requires residual risk, as the decision-memo article requires for a judgement.
Keep a human decision. A person is accountable and can explain the choice, which the AI HR screening article requires, as the human-in-the-loop article argues for meaningful review, as the governance checklist requires an owner, as the decision-memo article requires for a record.
Check current obligations. Employment rules vary, which the AI HR screening article treats, as the privacy article makes obligations jurisdiction-specific, as the legal article requires a dated check, as the term-sheet article treats formal terms as substantive, as the decision-memo article requires for a record.
Three consequences follow. The criteria come before the search, as the rubric and re:Work material advise, as the decision-memo article requires, as the data-governance article requires dated definitions, as the monitoring article advises for review, as the risk article requires residual risk to be stated, as the hiring trade-offs article treats capacity, as the team-culture article warns about implicit norms.
A worked review
The following is hypothetical and illustrative. A team wants to hire a project manager because deliveries are late.
Three checks decide. First, is the problem capacity or clarity, as the hiring trade-offs and engineering-management articles ask, with the tasks defined, as O*NET-style descriptions support? Second, does the role have criteria that predict those tasks, as the rubric and behavioral-interview articles require, with evidence rather than a proxy, as the causal-inference article warns? Third, can the recurring cost be justified, as the unit-economics and cash-flow articles require, with a recorded decision, as the decision-memo article requires?
Three conclusions follow. Late deliveries may be a scope problem, which the first check reveals. A task-based criterion is testable, as the rubric article requires. And the decision should be recorded with the assumptions, as the decision-memo article requires.
What a checklist cannot do
It cannot create a good candidate pool, which the re:Work material treats as a practice, as the publication standard forbids guaranteed outcomes, as the risk article requires residual risk. It does not remove legal duties, which the AI HR screening and legal articles require, as the privacy article makes obligations jurisdiction-specific, as the governance checklist requires an owner.
The counterargument that a fast hire is better than a slow process is fair when the role is clear and the cost of waiting is high, which the hiring trade-offs article treats as fit, as the decision-memo article argues for proportionality, as the worked review shows.
A decision test
- State the problem, as the hiring trade-offs article advises.
- Define the tasks, as O*NET-style descriptions support.
- Choose evidence, as the rubric article requires.
- Keep the decision with a person, as the AI HR screening article requires.
- Check current obligations, as the legal article requires.
- Justify the cost, as the unit-economics article requires.
- Record the decision, as the decision-memo article requires.
For the trade-offs, see Hiring Trade-Offs; for the management context, see Engineering Management.
References & Further Reading
- Google re:Work, 2026. Google re:Work - Hiring — Research-based guidance on job requirements, interviews and structured hiring practices.
- U.S. Department of Labor, 2026. O*NET OnLine — The standard occupational taxonomy used to compare roles across industries.