Product craft and leadership3 min read

Hire for the Work

A structured approach to assessing product judgement, technical fluency and collaboration against the needs of the role.

A hiring table combines recent work evidence, structured assessment and an auditable decision record.
On this page
  1. 1.Start with the role
  2. 2.Ask for the decision trail
  3. 3.Use a bounded working session
  4. 4.Make the decision explainable

A candidate builds an impressive prototype during an interview. Another spends more time asking what the customer needs and how the result will be evaluated. Both may be useful signals. Neither is enough on its own to establish who can do the job.

The assessment should reflect the work the person will actually do and give candidates a fair way to show it.

Start with the role

Describe the outcomes the person will be responsible for and the decisions they must make with others. Use the competency profile to identify the depth needed in customer understanding, strategy, model systems, evaluation, delivery and collaboration.

Set a working technical baseline appropriate to the role. Someone owning an agent with access to customer records needs deeper evidence of evaluation, permissions and recovery than someone using AI for research support. Do not turn production coding into a hidden requirement when the work does not call for it. Equally, do not accept tool vocabulary as evidence that a candidate understands how the system behaves.

Ask for the decision trail

Connected assessment stations form a structured product-builder interview loop.

Use a consistent set of questions and assess the evidence against agreed criteria. Ask a candidate to walk through a real decision:

  • What problem was the team trying to solve, and what evidence did it have?
  • What did the candidate personally choose or change?
  • Which uncertainty did they test, and what happened?
  • How did they assess quality and handle a failure?
  • Where did another discipline change the approach?
  • What would they do differently now?

Offer ways to protect confidential information, including redaction or a reconstructed example. Do not assume that a person with less public work has less relevant experience.

Use a bounded working session

When a work sample adds evidence the interview cannot, provide a realistic problem, enough context and a clear time limit. Tell the candidate what will be assessed and what tools are available. Observe how they frame uncertainty, seek missing information, make trade-offs and check the result.

Do not reward speed at the expense of judgement. A candidate who pauses to identify a permission boundary or asks for customer evidence may be doing the most useful part of the work. Offer reasonable adjustments or an equivalent format, and pay for substantial take-home work rather than using it as free production labour.

Make the decision explainable

Interviewers should record evidence independently before the discussion. Compare observations against the role, investigate contradictions and avoid treating employer reputation, familiarity or presentation polish as a substitute for capability.

A radar profile can help organise a development conversation; it is not an automated hiring score. The hiring decision needs evidence, context and accountable human judgement. Once someone joins, use the profile to agree on development opportunities rather than treating the interview as a final measure of their ability.

v3.1 · Updated Oct 2026