AI Product Manager hiring kit

Every step to hire the product manager who can hold a quality bar on a feature that won't behave the same way twice.

About this kit — the 5Ws

An AI product manager owns a product built on a model: ask it the same thing twice and you can get two different answers. Their job is to decide what counts as a good enough answer, build a way to check that consistently, and plan for the times the model gets it wrong. They still do the core work of any product manager — discovery, setting priorities, keeping stakeholders aligned. What's different is the material: instead of a fixed spec, they're managing something that varies every time it runs, and have to prove it's good enough rather than describe it once.

Calibrated for:: Mid-level to senior product manager — someone who has owned at least one feature whose output wasn't the same every time. Individual contributor or first-line lead.
Timeline:: Set an approval-to-offer target at intake, allowing for panel availability, candidate adjustments, references and any lawful checks.

Who: Hiring managers and recruiters bringing on their first or next AI product manager — often product leaders who have hired classic PMs before but not for a role built around a model that behaves differently every time.
What: Use this kit to test evaluation judgement, user-value decisions and fallback design for model-based features.
When: Start it the moment a probabilistic feature becomes central enough that someone needs to own its quality bar full time — ideally before the first model-driven decision reaches real users.
Where: Product organisations building features whose output is set by a model rather than fixed logic.
Why: The work sample, structured interview questions and scoring rubric let you compare candidates on job-related evidence — how they interpret limited evidence, resist premature automation, defend a build-or-don't-build call and design for the model getting it wrong — rather than on how confidently they talk about 'AI product management'.

The competency model · 7

Use these competencies to compare job-related evidence. Review any apparent gap in a must-have before deciding.

Evaluation design literacyMust-have · 20
Can define what 'good output' means for a probabilistic feature before it ships, and has built or run a working method to measure it.
Probabilistic product judgementMust-have · 20
Scopes what a model should and shouldn't attempt, makes a reasoned build-versus-buy call, and can defend the trade-off out loud.
User value, adoption and prioritisationMust-have · 15
Connects model quality to a real user problem, adoption and business outcomes; can stop or reshape a feature that performs well technically but doesn't create enough value.
Guardrail and failure-mode designMust-have · 15
Decides which actions the model may take on its own, what evidence must exist before it acts automatically, and what the user sees when the system is uncertain or wrong.
Cross-functional communication of model limitsCan learn · 10
Explains what a model can and can't do, in plain language, to stakeholders without a technical background — without overselling or hedging into uselessness.
Delivery and prioritisation under uncertaintyCan learn · 10
Sequences a roadmap and makes trade-off calls when the model's behaviour, cost or reliability might shift mid-project.
Responsible AI and compliance awarenessCan learn · 10
Spots bias, privacy and regulatory exposure in a product decision early enough to change it, without waiting to be told.

What's required and what's optional

Your hiring journey for AI Product Manager. Select a stage to jump to it.

Required for every hire
Optional — use when it adds evidence
AI boost — a big drafting win
Colour = phase

Phase 1
Plan
1. 01Plan the roleRequired
2. 02Agree successRequiredAI boost
Phase 2
Attract
1. 03Write the jobRequiredAI boost
2. 04Find candidatesOptionalAI boost
Phase 3
Select
Phase 4
Decide
Phase 5
Onboard & learn
1. 12Help them settle inRequired
2. 13Measure time to hireRequiredAI boost

AI drafts, people decide: Use AI to draft, rewrite and summarise your own material — never to rank, score, screen out or decide on candidates, and never with a candidate's personal data.

Plan

Attract

Select

Decide

Onboard & learn

Solid = required · dashed = optional · arrow keys move between steps

Stage 1 of 13Required

0 of 3 done

Plan the role

Workforce planning and requisition approval

Who runs it: Hiring manager + finance / HR business partner
Done when: An approved requisition with a written business case, budget and a named decision-maker.

Key tool

Answer these before the role is approved

1Which decisions will this person own where the underlying feature won't behave the same way twice?
2How is the team deciding today whether a model-based feature is good enough to ship?
3Could an existing product manager pick this up with support, rather than a dedicated hire?

AI as an advantage4D framework

Delegate: Hand AI the first draft of the business case and the build / borrow / buy comparison. The decision, the budget and the sign-off stay with people.

Show the prompt and the checks

Describe: You are helping a hiring manager write a business case for an AI Product Manager role. Context: I will paste the problem the hire solves, the work it involves, the capacity we already have and the time we have. Produce: (1) a one-sentence problem statement in business terms; (2) a build / borrow / buy comparison with the strongest argument for each; (3) the questions a finance partner would ask; and (4) a short recommendation with the evidence it rests on. Use British English and plain language. Do not invent figures — leave [brackets] where I need to supply numbers. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check every number and claim against your own notes and strike anything the draft assumed. Make sure 'buy' is argued from ongoing work, not from a job title.
Diligence: The hiring manager owns the final case and the budget request. No candidate information belongs here; AI drafts the case, people decide whether to open the role.

Don't miss: Creating this title to match a competitor's org chart, when no specific feature or decision actually needs a dedicated owner yet.

Framework

Build · Borrow · Buy

Before opening a role, decide whether to build the capability in your current team, borrow it (contractor, agency, partner), or buy it (a permanent hire).

Write the problem the hire solves in one sentence, in business terms — not the job title.
Test Build: could an existing person grow into this within the time you have?
Test Borrow: is the need time-boxed, or does it end once a system is shipped?
Choose Buy only when the work is ongoing, core to the product and nobody inside can absorb it.
Record the decision, the budget and the one person who signs off the final hire.

Why it works: Writing the build, borrow or buy decision down exposes a vague or temporary need before it becomes a permanent requisition — and gives every later stage an anchor to check against.

• Confirm who signs off the final hire — for this role, that's typically the product lead this person will report to, not a committee.

Is this a dedicated role?

Decide whether the work is sustained and substantial enough for a dedicated owner by writing down the workload, the risk, the capacity you already have and the outcomes you expect.

Answer these before the role is approved

1.Which decisions will this person own where the underlying feature won't behave the same way twice?
Listen for: Named features or decisions, not a general sense that 'AI product work' is coming.
2.How is the team deciding today whether a model-based feature is good enough to ship?
Listen for: An honest answer — often 'a few people eyeballing it' — which is exactly the gap the hire closes.
3.Could an existing product manager pick this up with support, rather than a dedicated hire?
Listen for: A named person and a realistic path, or a clear reason the work is too much for one person alongside everything else.
4.Is the need ongoing, or does it end once one feature ships?
Listen for: Ongoing work — a growing set of model-based features, a recurring quality bar to hold — justifies a permanent hire.
5.What does it cost the business each month this role stays open?
Listen for: A concrete consequence: a feature stuck in limbo, wrong outputs reaching customers, a launch nobody will sign off.

Build, borrow or buy?

Build: give an existing product manager a defined AI feature and a mentor with evaluation experience.
Borrow: a specialist consultant to stand up the first evaluation method and hand it over within a quarter.
Buy: a dedicated AI product manager — choose this once several features need a continuously held quality bar.

Watch out for

Confusing this role with a machine learning or AI engineer. Model development and production ML may sit with an MLE, model-backed application engineering with an AI engineer, and product decisions — what 'good enough' means and what happens when the model is wrong — stay jointly owned by product and engineering. State the division explicitly in the vacancy.

Stage 2 of 13Required

0 of 2 done

Agree success

Intake meeting and competency model

Who runs it: Recruiter + hiring manager
Done when: A signed-off competency model: 5–7 competencies, each marked must-have or trainable, with weights.

Key tool

Ask the hiring manager

1Which of the systems or areas this person will own worries you most, and why?
2When something there went wrong recently, how did you find out?
3In 12 months, what will be shipped, fixed or running for you to call this hire a success? Agree two or three measurable outcomes.
4Who will they work with most closely?
5What could a strong candidate learn in their first three months? Those capabilities are 'trainable' — never use them to filter applications.

AI as an advantageAI boost4D framework

Delegate: Hand AI your raw intake notes to turn into a draft competency model. Choosing the must-haves and the weights stays with the hiring manager and recruiter.

Show the prompt and the checks

Describe: You are helping a recruiter and a hiring manager build a competency model for an AI Product Manager role. Context: I will paste the notes from our intake meeting, including the 12-month outcomes and what the hiring manager worries about most. Produce a table of 5–7 observable competencies with, for each: a one-line definition; whether it is a must-have or trainable, with the reason; what evidence of it looks like in real work; and a suggested weight so the weights total 100. Use British English and inclusive wording, avoid years-of-experience or named employers as evidence, and keep every competency job-related. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that each competency is observable and job-related, that nothing describes a type of person rather than the work, and that trainable items haven't been marked must-have.
Diligence: The hiring manager signs off the final model and weights before anyone meets a candidate. No candidate data goes into the prompt; AI drafts, people decide.

Don't miss: Requiring a specific AI framework or tool on the CV. What matters is whether they've had to decide when output was good enough, not which stack they used to get there.

Framework

Competency model (must-have vs trainable)

A short list of the observable capabilities the job needs, split into what the hire must bring on day one and what you will teach.

Start from the 12-month outcomes, then ask which capabilities produce them.
Keep 5–7 competencies. With more, interviewers struggle to score each one separately.
Mark each must-have or trainable. Only must-haves can count against a candidate.
Give each a weight so they sum to 100, agreed before anyone meets a candidate.
Write what evidence of each looks like, so interviewers know what they are listening for.

Why it works: Agreeing the criteria before meeting candidates stops the bar moving from one candidate to the next, and makes it harder for 'I'll know it when I see it' to decide the hire.

Core intake questions (ask for every role)

Book 45 minutes with the hiring manager before anything is advertised, and write the answers down.
Which of the systems or areas this person will own worries you most, and why?
When something there went wrong recently, how did you find out?
In 12 months, what will be shipped, fixed or running for you to call this hire a success? Agree two or three measurable outcomes.
Who will they work with most closely?
What could a strong candidate learn in their first three months? Those capabilities are 'trainable' — never use them to filter applications.
Who is on the interview panel, and is their time held for the next four to six weeks?

Questions specific to this role

1.Does this person also need to make the build-versus-buy call on which model or approach to use, or will engineering own that?
Listen for: A clear split of who decides what — it changes how much weight probabilistic product judgement carries in the scorecard.
2.Is there a specific automated decision — an auto-approval, an auto-reject, a routing call — this person needs to redesign in their first quarter?
Listen for: A named decision with real stakes; it becomes the basis for the work sample.
3.How much of this role is defining evaluation and guardrails for existing features, versus new roadmap and delivery work?
Listen for: The balance shapes how heavily to weight evaluation design literacy against delivery and prioritisation in the scorecard.

What success looks like in 12 months

Every model-based feature this person owns has a working evaluation method that runs before each meaningful change ships.
At least one feature was reshaped or pulled back after failing to create real user value, even though it was technically working.
Stakeholders outside the product team can correctly explain what the feature can and cannot do.
There's a written fallback plan for what happens when the model gets it wrong, for every feature this person owns.

Stage 3 of 13Required

0 of 3 done

Write the job

Job description and pay band

Who runs it: Hiring manager (content) + recruiter (publishing)
Done when: A published job description that states outcomes, the must-haves, how AI tools are used and the pay information the law requires.

Key tool

AI Product Manager

We're looking for an AI product manager to own the quality bar for the model-based features in [product]. You'll decide what a model should and shouldn't attempt, define what 'good enough' means and build the evaluation to prove it, and design what happens when the model gets it wrong — working closely with engineering, data and the teams closest to customers.

What you'll do

•Define and maintain the evaluation method for each model-based feature you own, and run it before any meaningful change ships.
•Decide what a model should and shouldn't be trusted to do, and make the build-versus-buy call on which model or approach to use.
•Define when the model may act on its own, the evidence that supports it, and what the user sees when those conditions aren't met (the fallback).
•Turn model limits into an honest, sequenced roadmap, and re-plan when the model's behaviour, cost or reliability shifts.
•Explain what the feature can and cannot do to engineering, support, sales and customers, in plain language.
•Spot fairness, privacy and regulatory exposure in a product decision early enough to change it.

What you need

•You have owned a product feature or decision where the output was not the same every time, and can show how you defined and measured 'good enough'.
•You can explain how you decided a model should or shouldn't be used for a specific problem, and defend the trade-off.
•You have designed what happens when an automated decision is wrong — an escalation path, a threshold, a fallback — not just the happy path.
•You can show a time you stopped, reshaped or deprioritised a feature that was technically working because it wasn't creating enough user or business value.

Nice to have

•Experience working directly with a data science or machine learning team on evaluation or model selection.
•Experience with a feature that required a human-in-the-loop or escalation design.
•Familiarity with AI-specific regulation such as the EU AI Act or US state AI laws.
•A background in a regulated or high-stakes product area (finance, health, hiring, safety).

How we use AI tools

•In your own work, you're expected to use approved AI tools where policy allows, and to catch it yourself when a tool's output is confidently wrong — the same standard you'll hold the product to.
•For the product itself, you decide which tasks a model should never be trusted with alone, and design what happens instead.
•You're welcome to use any AI tools you'd like for the review-rule exercise — just tell us which ones and how you used them.

Pay

Salary range: [currency, minimum–maximum], plus [equity/bonus/benefits]. The range reflects [location/working pattern]. We place every offer within it using the same pre-set, job-related, gender-neutral factors — level, scope of feature ownership, depth of evaluation and guardrail experience, experience in regulated or high-stakes domains — never previous salary or negotiating style.

AI as an advantageAI boost4D framework

Delegate: Hand AI the first draft of the job description from your signed-off competency model. The must-haves, the pay range and the final wording stay with people.

Show the prompt and the checks

Describe: You are helping write an outcome-based job description for an AI Product Manager role. Context: I will paste the competency model (must-have and trainable, with evidence), the 12-month outcomes, how the team uses AI tools, the location and working pattern, and the pay range. Produce: a summary paragraph that leads with the problem and what the hire will own; 'What you'll do' as outcomes, not tasks; 'What you need' containing only the must-haves; 'Nice to have' for the trainable items; 'How we use AI tools'; and a pay section that states the range. Use British English and inclusive, gender-neutral wording, avoid hype, and replace any 'X years' with the capability it stands for. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that 'What you need' contains only the must-haves, that no degree, employer or years requirement crept in, and that the pay range and location are exactly what was approved.
Diligence: The hiring manager owns the content and the recruiter owns publishing, including the pay information the law requires for each location. AI drafts the advert; people decide what it says.

Don't miss: Asking for 'years of AI product experience' as a headline requirement — the discipline is new enough that this mainly filters for people willing to stretch the truth.

Stage 4 of 13Optional

0 of 3 done

Find candidates

Sourcing strategy

Who runs it: Recruiter / sourcer
Done when: A shortlist-ready pipeline from at least three channels, with outreach tracked.

Use when:: Inbound applications won't give you enough qualified candidates.
Skip when:: Your shortlist already comes from inbound applications or referrals.

Key tool

Search query

("AI product manager" OR "product manager" OR "product lead") AND ("evaluation" OR "model quality" OR "LLM" OR "machine learning") AND ("roadmap" OR "shipped" OR "launched") NOT ("intern" OR "student")

First outreach message

AI as an advantageAI boost4D framework

Delegate: Hand AI the search queries and the first draft of the outreach template. Choosing channels, personalising to a candidate's public work and sending stay with the recruiter.

Show the prompt and the checks

Describe: You are helping a recruiter source candidates for an AI Product Manager role. Context: I will paste the must-have competencies, the kind of work we want evidence of, the channels we are using and the pay range. Produce: (1) one search query per channel, using OR for alternatives, AND for things that must all appear and NOT to exclude, with a one-line note on what each query looks for; and (2) a first-outreach template of under 120 words that opens with a [placeholder for something the candidate built], states the problem we are hiring to solve and the pay range, and ends with a low-pressure question. Use British English and inclusive wording. Do not refer to any specific person. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that the queries search for evidence of the work rather than job titles alone, and that the template claims nothing about the role or the pay you can't back up.
Diligence: The recruiter personalises every message to something the candidate actually built, and sends it. No names or profile data go into the prompt; AI drafts, people decide whom to contact.

Don't miss: Search for evaluation and guardrail decisions across product-manager titles, whether or not the title includes 'AI'.

Framework

Channel mix + evidence-first outreach

Spread sourcing across channels where the work is visible, and open outreach with the problem, not the perks.

Pick channels where candidates show their work, not only where they list job titles.
Write one search query per channel. OR joins alternatives, AND joins things that must all appear, NOT excludes. Keep the version that works best.
Personalise the first line to something the candidate actually built or wrote.
Lead with the problem and the pay range. Save the perks for later.
Track reply rates by channel each week and drop the channel that isn't working.

Why it works: Searching for evidence of the work can surface candidates whose current title differs from the vacancy, or whose CV undersells what they have done.

Sourcing basics

Adapt the search query for each platform — the same words behave differently on each site.
Candidates with adjacent titles may have relevant evidence. Search for the work and outcomes the role needs, not the current title.
Channel activity is a lead, not evidence. Review linked work and examples against the written competencies.

Where to look

Product communities and forums focused on AI features

A public write-up on a probabilistic feature they shipped is reviewable evidence of how they evaluated it.

Your own product and engineering team's referrals

Engineers and designers who shipped a model-based feature with the candidate can describe decisions you can then check in the interview.

Conference talks and write-ups on product evaluation or AI product management

A talk on how a team measured 'good enough' is reviewable evidence of the judgement this role needs.

Product-led growth and analytics communities where PMs discuss measuring feature quality

Discussions here can be checked directly for how someone reasons about measuring feature quality.

Internal transfers from data, analytics or engineering

Someone already close to how the model behaves brings context you can test directly against the competency model, rather than assuming it from their internal tenure.

Boolean search string

("AI product manager" OR "product manager" OR "product lead") AND ("evaluation" OR "model quality" OR "LLM" OR "machine learning") AND ("roadmap" OR "shipped" OR "launched") NOT ("intern" OR "student")

First outreach message

Hi [name] — [specific detail from their write-up or talk] stuck with me. At [company], we still can't reliably tell finance or support when a model-based decision is trustworthy — that's the open problem behind this AI product manager role, paying [range]. Worth a 20-minute call to swap notes on it, hiring or not?

Stage 5 of 13Required

0 of 3 done

Check applications

Application screening

Who runs it: Recruiter
Done when: Every application reviewed against the same written knockouts within five working days.

Key tool

Reject only if one of these is missing

•Can meet the role's work-authorisation requirements by the start date, with sponsorship where the employer offers it. Don't ask for documents at this stage.
•Describes owning at least one feature or decision with a probabilistic or model-based output that reached real users.
•Shows product management experience of any kind — discovery, roadmapping, shipping — in any domain.

AI as an advantage4D framework

Delegate: Hand AI the job of turning your written knockouts into a consistent checklist with reason codes. Reviewing each application stays with the recruiter.

Show the prompt and the checks

Describe: You are helping a recruiter prepare an application-screening checklist for an AI Product Manager role. Context: I will paste the must-have competencies and our written knockout criteria. Produce: (1) each knockout as a yes/no question answerable from an application alone; (2) a short list of reason codes for a 'no'; and (3) a note of any criterion that looks like a proxy — a degree, employer brand or employment gap — rather than a job-related requirement, with a suggested rewrite. Use British English. Do not evaluate any applicant and do not ask for applicant details. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that each question is binary and job-related, and that every flagged proxy has been removed or justified in writing.
Diligence: A person reviews every application against the checklist and records the reason. Never paste CVs or applicant details into an AI tool, and never let a tool screen anyone out — in New York City and the EU that can bring automated-decision rules into play.

Don't miss: Rejecting for no specific AI-titled experience. The skill transfers from any product role with a genuinely uncertain output.

Framework

Knockout criteria

A small set of yes/no requirements, written in advance, applied to every applicant the same way.

Derive knockouts only from must-have competencies and genuine legal requirements.
Keep them binary and answerable from the application itself.
Apply them in the same order to every application and log the reason for each rejection.
Do not use proxies such as university, employer brand or employment gaps as knockouts.
Anything ambiguous gets a second review or moves forward to the skills stage.

Why it works: Early screening rejects people before richer evidence exists, so its criteria need the most care. Written criteria make decisions reviewable — but each one must also be job-related, applied consistently and checked for unjustified adverse impact.

Screening rules

Do not use degrees, employment gaps or certifications as filters unless they are demonstrably job-related and justified for this role.
Judge the claims in a CV, not how polished it is — a well-written CV may or may not have had AI help, and either way it is the evidence that matters.

Knockout criteria

Can meet the role's work-authorisation requirements by the start date, with sponsorship where the employer offers it. Don't ask for documents at this stage.
Describes owning at least one feature or decision with a probabilistic or model-based output that reached real users.
Shows product management experience of any kind — discovery, roadmapping, shipping — in any domain.

Green flags

Describes how they defined and measured 'good enough' for a feature, not just that it shipped.
Describes a decision not to use a model, or to pull one back, with the reasoning behind it.
Links to a write-up, a launch or a demo you can check.

Red flags

CV reads as a list of AI product tags — 'GenAI', 'copilot', 'agentic' — with no feature, metric or decision attached to any of them.
Only side projects or hackathon work, with no production feature behind it (fine for a junior role — not for this level).
Describes 'driving AI strategy' at a company with no shipped model-based feature to point to.

Watch out for

Reading a slickly AI-polished CV as either a green or red flag on its own. Weigh the claims inside it, not how well it reads.

Compliance checkpointNew York CityEU

For a New York City employment decision, work out whether a tool is an 'automated employment decision tool' (AEDT) under Local Law 144 — one that uses covered techniques to substantially assist or replace a discretionary decision. Before using a covered tool, make sure an independent bias audit was completed no more than a year earlier, publish the required summary, and give covered candidates or employees the required notice at least ten business days before use. In the EU, the AI Act (Annex III) lists AI used to recruit, filter applications or evaluate candidates as high-risk, subject to the Article 6(3) exception; the related obligations apply from 2 December 2027 under the amended timetable. A manual screen does not exempt an AI tool used elsewhere in the process.

Sources: NYC DCWP — Automated employment decision tools · EU AI Act — consolidated Regulation (EU) 2024/1689 · checked 2026-09-25

Stage 6 of 13Optional

0 of 3 done

Recruiter call

Recruiter screen

Who runs it: Recruiter
Done when: A 20–30 minute call that confirms logistics, motivation and one or two must-have signals.

Use when:: You are hiring at volume, or pay and logistics need confirming early.
Skip when:: You have only a handful of applicants — fold the pay and logistics questions into application screening instead.

Key tool

Ask every candidate, in this order

1Tell me about the most recent feature you owned where the output wasn't the same every time. Who used it?
2How did you know it was good enough to ship?
3Tell me about a model or approach you decided not to use for a feature. What made you say no?
4Describe a time you had to explain to a non-technical stakeholder why a feature couldn't do what they wanted. How did that go?
5Our range for this role is [range]. Does that work for you?

AI as an advantage4D framework

Delegate: Hand AI the first draft of the screening-call script and its evidence anchors. Running the call and taking the notes stay with the recruiter.

Show the prompt and the checks

Describe: You are helping a recruiter write a 20–30 minute structured screening call for an AI Product Manager role. Context: I will paste the must-have competencies, the logistics we need to confirm (location, working pattern, notice period) and the pay range. Produce: an opening that explains the process, the timeline and the pay range; 4–6 questions in a fixed order, each with one line on what a strong answer contains; and a closing that asks whether the published range works. Use British English and inclusive wording. Do not include questions about salary history, age, family, health or any other protected characteristic. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that every question is job-related and lawful, that the pay question asks whether the range works rather than for history, and that the anchors describe evidence, not impressions.
Diligence: The recruiter asks the same questions of everyone and writes the notes. No candidate details go into the prompt; AI drafts the script, people run the call and decide.

Don't miss: Expecting the recruiter to score evaluation design literacy or probabilistic judgement from this call. The screen only confirms the candidate can name a real feature and describe their own part in it plainly; depth comes later.

Framework

Structured screening call

The same short set of questions for every candidate, with notes taken against what a strong answer contains.

Open by explaining the process, timeline and pay range. No surprises later.
Confirm logistics: location, working pattern, notice period and whether the range works for them.
Ask the same 4–6 questions in the same order, and note evidence, not impressions.
Leave time for the candidate's questions. Don't score their questions unless they test a written, job-related competency.
Decide within 48 hours and tell the candidate either way.

Why it works: Using the same questions and written evidence anchors makes answers easier to compare, and a short, predictable call respects the candidate's time.

Screening call basics

Set the decision timetable before sourcing and tell candidates when to expect each update.
Ask every candidate what draws them to this particular role, and listen for interest in the work described rather than the title.
Confirm notice period and whether they are in other processes, so you can plan the timetable.
End every call by asking whether the published pay range works — never ask for salary history.

Recruiter screen questions

1.Tell me about the most recent feature you owned where the output wasn't the same every time. Who used it?
Listen for: A named feature with real users, and specifically the candidate's own role in deciding what counted as good enough — not their team's.
2.How did you know it was good enough to ship?
Listen for: Any structured method — even a simple review checklist counts at this stage.
Red flag: 'It looked fine in testing' or 'nobody complained'.
3.Tell me about a model or approach you decided not to use for a feature. What made you say no?
Listen for: A specific decision and reasoning, not a general view that models are risky.
4.Describe a time you had to explain to a non-technical stakeholder why a feature couldn't do what they wanted. How did that go?
Listen for: Plain language, a concrete example, and whether the relationship survived the conversation.
5.Our range for this role is [range]. Does that work for you?
Listen for: A clear answer on whether the published range works. Don't ask for salary history — this process sets pay from the published band and pre-set, job-related factors.

Compliance checkpointUS (state and city)EU

Don't ask for salary history. In the EU, national laws implementing Article 5(2) of Directive (EU) 2023/970 must prohibit the question. US rules vary, but jurisdictions including California and New York prohibit employers from seeking salary history. Ask whether the published range works instead.

Sources: EU Pay Transparency Directive 2023/970, Article 5 · California Labor Commissioner — salary history · New York State DOL — salary history ban · checked 2026-09-25

Stage 7 of 13Required

0 of 2 done

Work sample

Skills assessment / work sample

Who runs it: Hiring manager (design) + recruiter (logistics)
Done when: Every shortlisted candidate completes the same job-shaped task, marked against criteria written in advance.

Key tool

Set the review rule and write the brief

You're given anonymised data from a live feature: a model gives each incoming expense report a decision score and auto-approves the ones above a threshold, routing the rest to a person. Finance says too many wrong approvals are getting through. You have 25 anonymised reports, each with the model's decision score, its decision, and the correct decision worked out afterward. Treat this as an exploratory sample, not enough on its own to set a production threshold. Check how well the decision score actually separates the right decisions from the wrong ones, and recommend a temporary human-review rule for this feature rather than a permanent threshold. State what the small sample can't tell you, and specify what further data and calibration work you'd want before any threshold is used to automate approvals. Write the evaluation criteria you'd track for this feature going forward, and a short brief for the finance stakeholder explaining what you'd change and why.

Planned for up to three hours (adjustments available on request). At the agreed stopping time, write a short note on what you would examine next, and what you deliberately left out.

AI as an advantage4D framework

Delegate: Hand AI the first draft of the work-sample brief and its marking sheet. Choosing the task, setting the timebox and marking stay with the hiring manager.

Show the prompt and the checks

Describe: You are helping a hiring manager design a work sample for an AI Product Manager role. Context: I will paste the competency model, a real problem the team solved recently with anything confidential removed, the timebox, and our AI-tool policy for candidates. Produce: a candidate-facing brief (what to do, what to hand in, the time cap, how to request an adjustment, which AI tools are allowed and how to report their use); and a marking sheet with 4–6 criteria tied to named competencies, each with what a 1, a 3 and a 5 look like. Use British English and plain, inclusive wording. Do not design anything that needs more than the stated time. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that the task fits the timebox, that every criterion maps to a competency, and that the brief gives all candidates the same starting materials.
Diligence: The hiring manager owns the task and the criteria, and people mark every submission. Do not paste candidate submissions into an AI tool for scoring; AI drafts the brief, people mark and decide.

H-EvaluateH-Evaluate can generate a job-specific assessment from your job description, so you don't have to build the task by hand.How H-Evaluate helps →

Don't miss: Setting an open-ended 'design an AI feature' task. It measures free time and storytelling, not judgement.

Framework

Work-sample test

A small, realistic slice of the job, marked against criteria written in advance. Give candidates equivalent materials and arrange reasonable adjustments where required.

Take a real problem the team solved recently and shrink it to fit the timebox.
Write the marking criteria first, tied to the competency model.
Timebox honestly — for take-home work, a few hours at most — and say so in the brief.
State the AI-tool policy in writing. Where the job permits these tools, use equivalent conditions in the assessment and evaluate how candidates verify their output.
Mark without CV details where you can, and have two people mark borderline submissions.

Why it works: A well-designed work sample gives direct evidence of job-relevant skill rather than a proxy for it, and gives candidates a realistic preview of the work.

Assessment rules for every candidate

State the planned time cap and how to request an adjustment. At the agreed stopping time, ask candidates to note what they would examine next and what they left out — never reward unpaid overtime.
Give every candidate the same starting materials, and use a second marker for borderline submissions.
Say in writing which AI tools are allowed and ask candidates to tell you how they used them.
Invite every candidate to ask for adjustments, and answer each request promptly.
Pay for anything the task costs the candidate to run, such as model or cloud usage.

The work sample

Set the review rule and write the brief

Timebox: Planned for up to three hours (adjustments available on request). At the agreed stopping time, write a short note on what you would examine next, and what you deliberately left out.

What the candidate hands in

Your recommended temporary human-review rule (not a permanent threshold) and the reasoning — including the trade-off you're accepting and how reliable you judge the decision score to be, given the sample size.
The evaluation criteria you'd track for this feature after the change.
A short written brief for the finance stakeholder, in plain language.

Marking criteria (write these first)

The recommendation (a temporary human-review rule, not a permanent threshold) names the real trade-off between wrong approvals and delayed reviews.
The candidate checks how well the decision score actually separates right decisions from wrong ones before relying on it, and says what further calibration would be needed.
The evaluation criteria reflect the actual cost asymmetry of this feature, not a generic accuracy score.
The brief is written for a non-technical stakeholder: plain language, honest about the trade-off, no jargon.
At least one specific pattern in the data is noticed and named, not just an overall number.
The candidate says what ongoing monitoring they'd want, not only the one-off decision.

Adjustments: Candidates can ask for more time or a live, talk-through version instead. Reasonable adjustments are available on request.

Watch out for

Banning AI tools outright, or assuming the role uses them constantly. Where policy permits, judge whether the candidate verifies and takes responsibility for what the tools produce, not whether they used one at all.

Compliance checkpointUSGreat BritainEU

In the US, covered employers must provide a reasonable accommodation to a qualified applicant with a disability unless it would cause undue hardship (ADA). In Great Britain, the Equality Act 2010 requires reasonable adjustments in recruitment. In the EU, the duty comes from national equality law. Don't ask for more medical information than the law allows.

Sources: EEOC — prohibited practices · Equality Act 2010 · checked 2026-09-25

Stage 8 of 13Required

0 of 3 done

Structured interviews

Structured interview loop

Who runs it: Interview panel (named in advance)
Done when: Every competency has a lead interviewer and at least one second source of evidence, with the same questions for every candidate.

Key tool

Interview questions by pillar

Free in this kit: Domain questions for every round. The other three pillars and the AI-fluency check are measured by H-Evaluate.

Free in this kit

Senior product manager or product lead who reviewed the work sample · Evaluation design literacy · Probabilistic product judgement · User value, adoption and prioritisation

1.Walk me through an evaluation method you built for a feature whose output wasn't simply right or wrong. What specifically counted as 'good', and what user or business consequence was it protecting against?
Evaluation design literacy
Good answerNames a concrete metric or rubric tied to a real user or business consequence, explains how it was measured repeatedly or before each change shipped, and states openly where it fell short.
Weak answerDescribes only manual spot-checking with no repeatable method, or can't connect 'good' to any real consequence.
2.A team wants to replace a fixed-rules check with a model. Walk me through how you'd decide whether that's the right call — what would the model need to do better than the rules, and what would it cost you if it's wrong?
Probabilistic product judgement
Good answerNames the conditions where a model earns its place — the rules can't keep up, the input space is too wide — quantifies the cost of a wrong model decision against the cost of a wrong rule decision, and is willing to say 'no, keep the rules' when that's true.
Weak answerAssumes a model is automatically the better choice, or can't name a concrete cost of being wrong.
3.Pick a model-backed feature you'd want to ship. What user outcome, operating metric and failure measure would you put in its launch brief — and why those three?
User value, adoption and prioritisation
Good answerLinks a real user need to a measurable outcome metric, names a failure or quality signal that's distinct from the outcome metric, and explains why each belongs in the brief.
Weak answerNames adoption or model accuracy alone, with no distinct failure signal, or can't explain why the metrics belong together.

Optional follow-ups (2)

4.Your evaluation set shows a flat score for a new model version, but early users say it 'feels better'. How would you reconcile that before deciding whether to ship?
Evaluation design literacy
Good answerInvestigates the specific cases behind the qualitative impression, checks whether the evaluation set covers them, updates the evaluation if it doesn't, and reconsiders the release decision using the fuller evidence — rather than defaulting to either the measurement or the impression.
Weak answerDefers to the qualitative impression and ships anyway, or dismisses it without checking.
5.In your work sample you recommended a temporary human-review rule rather than a fixed threshold. Walk me through why you didn't just pick a threshold number, and what would need to be true before you did.
Probabilistic product judgement
Good answerExplains the sample-size limitation precisely, defends the human-review rule as the right call given that limitation, and names concretely what evidence — volume, calibration — would justify moving to a fixed threshold.
Weak answerCan't explain why a threshold wasn't appropriate yet, or gives a generic 'more data would help' with no specifics.

AI as an advantageAI boost4D framework

Delegate: Hand AI the drafting of probe questions and strong / weak anchors for one competency. Asking, listening and scoring stay with the interviewer.

Show the prompt and the checks

Describe: You are helping an interviewer prepare a structured technical interview for an AI Product Manager role. Context: I will paste one competency, its evidence description and the core question we ask every candidate. Produce: four probes in this fixed order — what would you do, why that choice, what else did you consider, how would you know it worked — tailored to the question; a one-line description of a strong answer and of a weak answer; and two follow-ups to use only if time allows. Use British English and inclusive wording. Keep everything about the work, nothing about the person. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that the probes test the named competency rather than trivia, that the anchors describe observable evidence, and that no question touches a protected characteristic.
Diligence: Interviewers ask the same core questions of every candidate and score alone against the rubric. Interview notes and candidate names never go into an AI tool; AI drafts the questions, people interview and decide.

H-EvaluateH-Evaluate can add evidence on Cognitive, Situational judgement, Behavioural and AI fluency for your panel to review alongside these interviews.How H-Evaluate helps →

Don't miss: Scoring 'probabilistic product judgement' on how enthusiastic a candidate is about AI, rather than probing their reasoning until you hear their own call on what a model should and shouldn't attempt.

Framework

Structured technical interview

Every candidate gets the same job-specific questions, each interviewer leads on specific competencies, and every answer is probed with the same four follow-ups: what would you do, why, what else did you consider, and how would you know it worked.

Give each competency a lead interviewer, plus a second source of evidence — the work sample, another round or an independent marker. Avoid asking the same thing twice, but never let one person's view be the only evidence for a critical competency.
Ask the three core questions for your round, in order, for every candidate. Use an optional follow-up only if there is time.
Probe each answer: why that choice, what else they considered, and how they would know it worked — until you hear the candidate's own technical decision.
Take notes on evidence during the interview. Don't rate until it's over.
Fill in your interviewer sheet and submit it before you talk to any other interviewer.

Why it works: Structured interviews make answers comparable: every candidate faces the same job-related questions and is scored against the same anchors.

Interview rules

Use the same core questions in the same order for every candidate.
In the work-sample review, understand the candidate's decisions against the rubric — don't turn it into a debate about your preferred solution.
Avoid trivia disconnected from a real job decision. Use a realistic debugging, design or evaluation problem instead.

Watch out for

Treating a candidate's familiarity with one vendor's model or API as evidence of product judgement — it isn't.

Compliance checkpointUSUKEU

Don't ask about protected characteristics — such as age, disability, pregnancy or family plans, religion, race or nationality — unless applicable law permits the question for a specific, necessary, job-related purpose, and HR or counsel has confirmed that basis beforehand. Ask only whether the candidate can meet the role's work-authorisation requirements. If a candidate volunteers protected information, don't probe; record only what is lawfully needed, keep it separate and restrict access.

Sources: EEOC — prohibited practices · Equality Act 2010 · checked 2026-09-25

Where to find more interview questions

Use web question banks for inspiration only: ask every candidate the same job-related questions, check each one against this kit's competencies, and never ask about protected characteristics. Don't reuse this kit's work sample from a public bank — candidates can find questions that circulate online, so a widely posted question tests preparation more than skill.

Show 7 sites

US OPM — Structured interviews(opens in a new tab)
US federal guidance on building structured interviews, with a guide, training material and sample questions with rating scales.
FreeFor interviewers
Acas — Interviewing job applicants(opens in a new tab)
UK public guidance on preparing fair interviews, asking applicants the same questions and avoiding discriminatory ones.
FreeFor interviewers
Workable — Interview questions library(opens in a new tab)
Sample interview questions for employers, listed by job role, including machine learning, data and engineering roles.
FreeFor interviewers
Indeed for Employers — Interview questions(opens in a new tab)
Sample interview questions for employers by job title and skill, with notes on what to look for in answers.
FreeFor interviewers
Tech Interview Handbook(opens in a new tab)
Open-source software-engineering interview preparation: coding, system design and behavioural questions.
FreeFor candidates and interviewers
Chip Huyen — Machine Learning Interviews Book(opens in a new tab)
Free online book with knowledge questions on maths, computer science and machine learning, grouped by difficulty.
FreeFor candidates and interviewers
Blind — Interview questions channel(opens in a new tab)
Anonymous posts by tech workers about questions they report being asked. Unverified; some content needs sign-in.
Free, some content needs sign-inCandidate reports, unverified

Links checked 2026-10-05. External sites; we don't control their content.

Stage 9 of 13Required

0 of 2 done

Compare evidence

Scoring, calibration and debrief

Who runs it: Hiring manager (chairs) + panel
Done when: A documented hire / no-hire decision traceable to scored evidence against the competency model.

Key tool

Interactive scorecard

Score one candidate against the rubric. Everything stays in your browser. Download it as a spreadsheet for your records.

Evaluation design literacy Must-have

Weight

What do 1, 3 and 5 look like?

1: Can't say what 'good' means for the feature beyond 'it looks right'; no way to know if a change helped.
3: Builds an evaluation method when asked; catches the obvious failure mode but misses edge cases.
5: Defines and builds the evaluation before being asked, ties it to real user or business harm, and reports honestly when a change makes things worse.

Probabilistic product judgement Must-have

Weight

What do 1, 3 and 5 look like?

1: Treats every problem as a model problem; can't articulate when a model isn't the right tool.
3: Can name the trade-offs between a model and a fixed rule when prompted, and makes a reasonable call most of the time.
5: Scopes what the model should and shouldn't attempt unprompted, and defends a build, buy or 'don't build' call with evidence.

User value, adoption and prioritisation Must-have

Weight

What do 1, 3 and 5 look like?

1: Ships whatever is technically buildable without checking it solves a real user problem or gets adopted.
3: Connects most decisions to user value when asked, but sometimes defers to technical elegance over adoption.
5: Continually ties model quality to user outcomes, and is willing to stop or reshape a feature that works technically but isn't valued or used.

Guardrail and failure-mode design Must-have

Weight

What do 1, 3 and 5 look like?

1: Designs only the successful path; the failure case is 'show an error'.
3: Designs a fallback for the obvious failure mode when asked.
5: Designs escalation, confidence thresholds and fallback behaviour up front, matched to the specific stakes of the feature.

Cross-functional communication of model limits Can learn

Weight

What do 1, 3 and 5 look like?

1: Can't explain model behaviour without jargon, or promises more certainty than the model can deliver.
3: Clear explanations when asked directly; sometimes hedges into vagueness.
5: Explains limits honestly and plainly to any audience, and turns the explanation into a workable alternative.

Delivery and prioritisation under uncertainty Can learn

Weight

What do 1, 3 and 5 look like?

1: Treats the roadmap as fixed regardless of what the model is actually doing.
3: Re-plans when a problem is pointed out, with reasonable trade-offs.
5: Watches for signals that the plan needs to change, re-sequences early, and communicates the change clearly.

Responsible AI and compliance awareness Can learn

Weight

What do 1, 3 and 5 look like?

1: Doesn't consider fairness, privacy or regulatory exposure unless told to.
3: Names the main fairness or privacy risk once a colleague points to it, but doesn't surface it unprompted.
5: Spots risk unprompted, quantifies it, and treats it as a priority rather than a footnote.

Weighted score– / 5

AI as an advantage4D framework

Delegate: Hand AI the drafting of a blank debrief worksheet and agenda from the competency rubric alone. People add the evidence locally; the scores and the decision stay with the panel.

Show the prompt and the checks

Describe: You are helping a hiring manager prepare a debrief for an AI Product Manager role. Context: I will paste the competency rubric only — the competencies, their weights and their 1, 3 and 5 anchors. Produce: (1) a blank debrief worksheet with one row per competency and empty columns for each interviewer's independent score, the evidence they cite, the spread of scores and an 'evidence gap?' box; (2) a 45-minute agenda: confirm every scorecard is in and reveal all scores at once, discuss the widest spreads using evidence only, review any must-have scored 1, then look at the weighted total and decide (hire, no hire or one targeted follow-up), and record the reasons; and (3) neutral questions the chair can ask to draw out evidence rather than adjectives. Leave every evidence and score cell empty. Do not suggest a score, a rating or a recommendation. Use British English. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that the worksheet follows your rubric exactly — same competencies, weights and anchors — and that the agenda keeps independent scores hidden until the reveal.
Diligence: Interviewers fill in the evidence and scores locally, alone, before the debrief, and the panel decides together. Candidate notes and personal data never go into an AI tool; AI never scores, ranks or compares candidates.

H-EvaluateH-Evaluate gives you a report on each candidate's assessment evidence to bring into this debrief.How H-Evaluate helps →

Don't miss: Scoring 'probabilistic product judgement' on how confidently a candidate talks about models, instead of the specific build, buy or 'don't build' decision they actually defended in the interview.

Stage 10 of 13Optional

0 of 2 done

Check references

References and background checks

Who runs it: Recruiter (references) + HR (checks)
Done when: At least two references that test specific competencies, plus only the checks that are lawful and relevant to the role.

Use when:: It is lawful where you hire, and specific evidence from a referee would change the decision.
Skip when:: Local law or company policy rules it out.

Key tool

Ask each referee

1What did [candidate] ship that the team still relies on?
2When a change to one of their features moved the evaluation numbers, how did they check it also worked for the people using it?
3How did engineers and data people find working with them?

AI as an advantage4D framework

Delegate: Hand AI the drafting of reference questions aimed at the competency the panel was least sure about. Choosing referees, making the calls and interpreting the answers stay with the recruiter.

Show the prompt and the checks

Describe: You are helping a recruiter write competency-based reference questions for an AI Product Manager role. Context: I will paste the competency model and the one or two competencies where our evidence is thinnest — no candidate details. Produce: 3–4 questions per competency that ask for specific examples ('tell me about a time…') rather than ratings; an opening question about how the referee worked with the person and for how long; and a closing question about what their next manager could do to help them do their best work. Use British English and inclusive wording. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that the questions ask for examples rather than opinions, that they stay on job-related competencies, and that none asks about health, family or other protected matters.
Diligence: References are taken with the candidate's consent and interpreted by people. Referee answers and candidate details never go into an AI tool; AI drafts the questions, people decide.

Don't miss: Treating a bare 'yes' to 'would you hire them again?' as evidence by itself, with no example behind it.

Framework

Competency-based referencing

Treat references as a last structured conversation about the candidate's work, aimed at the competencies where your evidence is thinnest.

With the candidate's consent, ask for two people who saw their relevant work directly — ideally a former manager and a peer.
Accept suitable alternatives if a manager or peer isn't available, and never penalise a candidate for a former employer's no-reference policy.
Aim your questions at the one or two competencies the debrief was least sure about.
Ask for examples, not ratings. 'Tell me about a time they…' works here too.
Set the timing of each background check by the law and policy that apply.

Why it works: Generic reference questions tend to produce little job-related evidence. Asking for specific examples tied to the role's competencies turns referencing into something you can use.

Core reference questions and checks

Open with: 'How did you work together, and for how long?' — it tells you how much weight the rest can carry.
Ask: 'Tell me about a time something they owned went wrong. What did they do?'
Close every reference with: 'What should their next manager do to help them do their best work?'
Verify only claims that were material to the decision — don't verify a degree the role never required.
Run criminal-record checks only where the role justifies them and local law allows; many roles don't need one.
Schedule formal work-authorisation checks at the legally required time: before employment starts in the UK; for US Form I-9, Section 1 by the first day of paid work and Section 2 within three business days.

Reference questions specific to this role

1.What did [candidate] ship that the team still relies on?
Listen for: Concrete, lasting work, not general praise.
2.When a change to one of their features moved the evaluation numbers, how did they check it also worked for the people using it?
Listen for: Independent confirmation that they connect measured quality to actual user value, not just a passing score.
3.How did engineers and data people find working with them?
Listen for: Examples of clear scoping or productive pushback, not just being 'easy to work with'.

Compliance checkpointUS

If a consumer reporting agency provides a background report, the Fair Credit Reporting Act requires a clear, stand-alone written disclosure and the candidate's written authorisation before you order it. Before rejecting someone because of the report, give them a copy and the FCRA summary of rights and a reasonable opportunity to review and dispute it before any adverse action; if you still reject, send a final adverse-action notice. State and local 'fair chance' laws may delay criminal-history questions or checks until after a conditional offer.

Sources: FTC — Background checks: what employers need to know · FTC — Using consumer reports: what employers need to know · checked 2026-09-25

Stage 11 of 13Required

0 of 2 done

Agree the offer

Offer, negotiation and close

Who runs it: Hiring manager + recruiter
Done when: An accepted written offer within the approved band, with a start date.

Key tool

Build the offer around

•The problem: they'll own the quality bar for features real customers depend on.
•Ownership: a named feature or feature area from day one, not a shared backlog.
•Learning: budget and time to work directly with the data or machine learning team on evaluation.
•Growth path: explain why they're slotted at this level, and what evidence would move them to the next one.

AI as an advantage4D framework

Delegate: Hand AI the first draft of the offer message built around what the candidate said matters to them. The figure, the approval and the conversation stay with the hiring manager.

Show the prompt and the checks

Describe: You are helping a hiring manager draft an offer message for an AI Product Manager role. Context: I will paste three general priority categories (for example: learning, flexibility, scope) — not the candidate's words, notes or personal details; the parts of the offer; and the start-date options — without the salary figure. Produce: a warm, plain-English message that links each part of the offer to one of their priorities, says what happens next and when the written offer follows, and invites questions. Use British English and inclusive wording, and leave [brackets] for figures and names. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that nothing promised is outside policy or the approved band, that every claim about the role is true, and that the message reads as personal rather than templated.
Diligence: The hiring manager places the offer in the band using the same pre-set factors for everyone and makes the verbal offer personally. Figures and personal details are filled in by people, never pasted into AI.

Don't miss: Leaving band approval unresolved until after the final interview, rather than obtaining it beforehand.

Framework

Close plan (motivators → offer → objections)

Build the offer around what the candidate told you they care about, anticipate their objections, and make sure the verbal and written offers match.

List the candidate's top three motivators from your notes at every stage.
Make the verbal offer personally, and link each part of it to a motivator.
Ask what else they are weighing and when they have to decide.
Place the offer in the band using the same pre-set, job-related factors for everyone, and record why.
Send the written offer promptly after the verbal one.

Why it works: A close plan ties the offer to the candidate's stated priorities and makes approvals explicit before the final interview.

Offer checklist and negotiation

Stay inside the approved band. If the candidate is worth more, re-level them with evidence rather than stretching the band.
Trade in things that cost less than salary where policy allows: start date, learning budget, working pattern.
Before the written offer, ask: 'What would make this an easy yes?'
Agree approval and the pay band before the final interview, so the offer isn't held up.
The hiring manager makes the verbal offer; the written offer follows within a working day.
Record which pre-set factors placed the offer where it is in the band.
Tell unsuccessful finalists personally, without avoidable delay, with brief feedback.

What will close this candidate

The problem: they'll own the quality bar for features real customers depend on.
Ownership: a named feature or feature area from day one, not a shared backlog.
Learning: budget and time to work directly with the data or machine learning team on evaluation.
Growth path: explain why they're slotted at this level, and what evidence would move them to the next one.

Compliance checkpointEUUS

Use objective, gender-neutral, pre-agreed factors to place candidates within the band, apply them consistently and record the decision as an internal pay-equity control. Check the national law implementing Directive (EU) 2023/970 and any local record-keeping rules; this recommendation is good practice, not a universal statutory documentation rule.

Sources: EU Pay Transparency Directive 2023/970 · checked 2026-09-25

Stage 12 of 13Required

0 of 2 done

Help them settle in

Pre-boarding and 30-60-90 onboarding

Who runs it: Hiring manager + buddy + HR
Done when: A new hire who has worked through a written 30-60-90 plan tied to the 12-month outcomes, with a check-in at each milestone.

Key tool

Before day one
Laptop, accounts and access to the product, data and evaluation tools ready before day one.
Days 1–30: learn
Meets engineering, data, support and legal colleagues who touch the model-based features.
Days 31–60: contribute
Builds or hardens the evaluation method for the highest-stakes feature they own.
Days 61–90: own
Owns the quality bar for one feature end to end, with an evaluation method running before changes ship.

AI as an advantage4D framework

Delegate: Hand AI the first draft of the 30-60-90 plan from the 12-month outcomes. Agreeing the plan with the new hire stays with the manager.

Show the prompt and the checks

Describe: You are helping a hiring manager draft a 30-60-90 day onboarding plan for a new AI Product Manager. Context: I will paste the 12-month outcomes from the intake meeting, the systems and people the hire will work with, and anything they will need before day one. Produce: a pre-boarding checklist (equipment, access, a named buddy, a first-week schedule); then three sections — days 1–30 learn, days 31–60 contribute, days 61–90 own — each with 3–4 concrete, checkable expectations and one milestone check-in question. Use British English and plain wording. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that each expectation is realistic for a new starter, ties back to a 12-month outcome, and offers the hire support rather than a test.
Diligence: The manager agrees the plan with the new hire in week one and owns the check-ins. The new hire's personal details stay out of the prompt.

Don't miss: Handing them a green-field feature in week two, before they've sat through a single evaluation review for something that's already shipped.

Framework

30-60-90 day plan

Three phases — learn, contribute, own — with written expectations for each, agreed with the new hire in week one.

Before day one: equipment, access, a named buddy and a first-week schedule.
Days 1–30, learn: systems, people and the current state of the work.
Days 31–60, contribute: a first scoped piece of work shipped with support.
Days 61–90, own: an area of responsibility with clear outcomes.
Hold a check-in at each milestone against the written plan.

Why it works: Hiring doesn't end at the signature. A written onboarding plan makes expectations and support visible to the new hire and their manager.

Before day one
- Laptop, accounts and access to the product, data and evaluation tools ready before day one.
- A named buddy from the product or engineering team.
- A reading list: the current state of every model-based feature, and any known incidents.
Days 1–30: learn
- Meets engineering, data, support and legal colleagues who touch the model-based features.
- Maps every feature they'll own and how 'good enough' is currently decided for each, if at all.
- Sits in on one live incident or escalation, even as an observer.
Days 31–60: contribute
- Builds or hardens the evaluation method for the highest-stakes feature they own.
- Identifies one feature that's technically working but not delivering the value it was built for, and proposes what to do about it.
- Drafts the fallback design for one feature that doesn't already have one.
Days 61–90: own
- Owns the quality bar for one feature end to end, with an evaluation method running before changes ship.
- Delivers one measured improvement with a before-and-after comparison.
- Presents findings to a non-technical stakeholder group in plain language.

Compliance checkpointUSUK

US: the employee completes Form I-9 Section 1 no later than their first day of paid work, and the employer completes Section 2 within three business days after that day (on the first day if the job lasts less than three business days). UK: complete the prescribed right-to-work check before employment starts, and apply it the same way to everyone.

Sources: USCIS — Form I-9 instructions · GOV.UK — Check a job applicant's right to work · checked 2026-09-25

Stage 13 of 13Required

0 of 3 done

Measure time to hire

Measure the process: mean time to hire

Who runs it: Recruiter / talent lead + hiring manager
Done when: A stage-by-stage timing record for this hire, the slowest step named, and one change agreed before the next requisition opens.

Key tool

Record when the hire accepts

•Time to hire: days from the successful candidate entering the pipeline (application or first contact) to the accepted offer. Average it across hires for mean time to hire.
•Time to fill, recorded separately: days from requisition approval to the accepted offer.
•Days per stage, from the stage's first action to its last — and whether the time was spent waiting or working.
•Offer-acceptance rate: offers accepted divided by offers made.
•Where candidates dropped out, and the reason you were given.
•Days between the final interview round finishing and every panellist actually submitting a score, given how many stakeholders sit on this loop.

Check in at 90 days whether the hire is meeting the outcomes in the job description — that tells you whether the process picked well.

Read: mean time to hire Read: time to hire vs time to fill

AI as an advantageAI boost4D framework

Delegate: Hand AI the job of building a blank timing worksheet and the instructions for reading it. Entering dates, working out the timings and deciding what to change stay with the recruiter and the hiring manager.

Show the prompt and the checks

Describe: You are helping a recruiter and a hiring manager set up a timing review for an AI Product Manager hire. Context: I will list the stage names we used, in order (for example requisition approved, sourcing, screening, recruiter call, work sample, interviews, debrief, references, offer accepted). Produce: (1) a blank worksheet with one row per stage and columns for start date, end date, days in stage, days spent waiting (scheduling, approvals, no reply) and number of candidates who entered and left; (2) step-by-step instructions for us to work out, from our own records, time to hire (the successful candidate's entry to the pipeline, by application or first contact, to the accepted offer; average it across hires for mean time to hire) and, separately, time to fill (requisition approval to the accepted offer); (3) five questions we should ask about the slowest stage, separating waiting from working; (4) a short template for recording one change to make before the next hire. Use British English. Do not include benchmarks or example figures. Ask me questions if anything is missing. Rule: do not ask for, and I will not paste, candidate names, interview notes, CVs, submissions or any other personal data. If any appears, stop and tell me to remove it.
Discern: Check that the worksheet covers every stage you actually ran, that the two definitions are not mixed up, and that the questions point at the process rather than at any person.
Diligence: People fill in the dates and do the arithmetic from their own records, choose the one thing to fix and write it down. No dates, names or details about any candidate go into the prompt.

Don't miss: Letting a large panel become the default excuse for delay without checking whether the debrief itself was the stage that actually dragged.

Framework

Mean time to hire, by stage

Time to hire is the number of days from the successful candidate entering your pipeline (their application or your first contact) to their accepted offer; mean time to hire is that figure averaged across hires. Time to fill — requisition approval to acceptance — is a separate measure. Record both per stage, so you can see where the time went rather than only the total.

When the hire accepts, write down the date each stage started and ended, and the day the successful candidate entered the pipeline.
Work out the days per stage, the time to hire and the time to fill, and mark the slowest stage.
Note the offer-acceptance rate and the stage where most candidates dropped out.
Separate waiting time (scheduling, approvals, silence) from working time, and decide which one to shorten.
Fix one thing before the next hire, and write down what you changed.

Why it works: A single total hides where the delay sits. Per-stage timing points at the one step to fix, and the acceptance rate and drop-out points show whether candidates kept pace with the process.

Record for every hire

Time to hire: days from the successful candidate entering the pipeline (application or first contact) to the accepted offer. Average it across hires for mean time to hire.
Time to fill, recorded separately: days from requisition approval to the accepted offer.
Days per stage, from the stage's first action to its last — and whether the time was spent waiting or working.
Offer-acceptance rate: offers accepted divided by offers made.
Where candidates dropped out, and the reason you were given.
Check in at 90 days whether the hire is meeting the outcomes in the job description — that tells you whether the process picked well.

What to log for this role

Days between the final interview round finishing and every panellist actually submitting a score, given how many stakeholders sit on this loop.
How long it took to get the debrief itself onto the calendar once scores were in.
Whether the people scoring the evaluation-and-judgement round and the design-and-delivery round had read the work sample closely, or skimmed it right before the call.

Where this role's hiring slows down

Watch for the debrief slipping because it needs more calendars aligned than any other stage in this process.
Watch for one stakeholder's score arriving late and holding up the whole decision.
Watch for the hiring-manager round being treated as a formality once the other two rounds have already settled the outcome.

Compliance checkpointUKEU

Under the EU and UK GDPR, tell candidates how long you will keep their data, or the criteria used to decide. Give that notice when you collect data from them directly, or within the Article 14 time limit when it comes from another source (such as a referral or a sourcing tool). Delete or anonymise data when it is no longer needed, keeping only what a documented lawful purpose still requires.

Sources: GDPR — Regulation (EU) 2016/679, Articles 5, 13 and 14 · ICO — UK GDPR guidance · checked 2026-09-25

General information, not legal advice. Rules depend on the employer, the role and where the work is done — confirm what applies with HR or counsel.

Frequently asked questions

What does an AI product manager do?

An AI product manager owns a product whose behaviour is probabilistic rather than fixed. They decide what a model should and shouldn't attempt, define what 'good enough' output means and build a way to measure it, make the call on which model or approach to use, and design what happens when the model gets it wrong. It's classic product craft — discovery, prioritisation, stakeholder alignment — applied to a component that won't behave the same way twice.

How is an AI product manager different from a regular product manager?

The underlying product craft is the same: discovery, prioritisation, delivery and stakeholder alignment. AI product work adds explicit evaluation of variable model output, error trade-offs and the user experience when the model is uncertain or wrong.

What should I test for when interviewing an AI product manager?

Test for evaluation design literacy first — can they define and measure 'good enough' for output that isn't fixed? Then probabilistic product judgement (knowing when a model is and isn't the right tool) and guardrail design (what happens when it's wrong). A realistic work sample that asks the candidate to examine limited evidence, recommend a temporary human-review rule and write a stakeholder brief reveals more than a portfolio walkthrough.

Can candidates use AI tools during the work sample?

Yes. Say so in the brief, and where company policy permits these tools for this role, ask candidates to describe how they used them. Judge whether they verified the output and took responsibility for it, not whether they used a tool at all.

How many interview rounds does an AI product manager need?

One work sample plus three structured rounds — an evaluation and judgement deep-dive, a design and delivery round, and a hiring-manager round — cover the competencies in the model. Add a further round only when it tests a distinct, job-related criterion not already covered.

When does an AI feature need its own dedicated product manager, rather than folding into an existing PM's plate?

Look at the model-based features on your roadmap, how many product decisions they need about quality and failure, and who makes those calls today. If nobody has the time to own them, that is the case for a dedicated AI product manager.

Go deeper

Related hiring kits

Guides

Skills tests

See your first AI-generated assessment in 5 minutes

No credit card. No question library to learn. Paste a job description and watch H-Evaluate build.

Request early access