A little direction changes everything.

A classic AI product sense prompt. The trap is a chat box bolted onto a grid. The strong answer picks a user, runs every job through an AI-fit test, and treats a silently wrong number as the main risk.

The question behind every AI product decision: a repeatable test, applied step by step, and the willingness to say 'a rule does this better' when it does, and 'a model, with a reviewer' when it does not.

A growth prompt with a hard constraint. Three engineers rules out most ideas, and doubling usage also doubles the compute bill. The interviewer wants a funnel diagnosis and two or three bets that fit.

Tenfold growth is not an optimisation problem. The interviewer wants to see you find new users the product does not serve today, and protect reliability and margins while doing it.

The central AI UX question. The interviewer wants patterns that make errors cheap to spot and cheap to fix, sized to what an error costs.

A shared vocabulary for one of the biggest decisions in AI product design: how much the AI does on its own. The interviewer wants the levels, and the rule for choosing among them.

Accuracy and trust are different things. The feature saves no time if people double-check everything, and the fix starts with finding out why experts are cautious.

The strategy question every AI application company faces. 'Better prompts' is not an answer. The interviewer wants a ladder of defensibility and a plan to climb it.

A common dismissal with a two-sided answer. The interviewer wants you to separate what is weak about thin wrappers from what makes many successful software businesses 'wrappers' too.

Platform risk made real. The answer is neither panic nor dismissal: work out which customers are actually at risk, double down on what the provider cannot easily do, and reduce dependence where it matters.

A strategic decision with a clear default and specific reasons to deviate. The interviewer wants a framework grounded in evals, volume, constraints and team capacity.

Recommend an approach to a CEO who needs a product decision. Explain what retrieval and fine-tuning each change, then connect that difference to freshness, reliability and cost.

The first vocabulary word of AI product management. Tokens are the unit of cost, speed and memory, and a PM who can't reason in them can't price, budget or design an AI feature.

Retrieval quality decides most RAG products, and embeddings are where it starts. The interviewer wants the intuition, the failure modes, and the fixes a PM would push for.

A larger context window changes what fits in a request. Decide whether to use it by checking corpus size, freshness, permissions and cost per successful query, including cache misses.

A RAG pipeline is the obvious first sketch. A strong answer starts with permissions instead, because one leaked salary document ends the product.

A full-stack AI system design with scale, money, languages and angry customers. The interviewer wants tiers: cheap triage for everything, an agent where it pays, and humans where it matters, with the cost per day worked out.

A pipeline design question with an automation trap. Writing summaries is the easy part; writing into the system of record that forecasts revenue is where the design needs care.

Every AI product depends on services it does not control. The interviewer wants a degradation plan by feature, written and tested before the outage starts.

Choose the least autonomy that does the job, explain exactly which step deserves a model, and know the one place in onboarding where an agent may genuinely earn its keep.

The compounding arithmetic every agent PM should be able to do in their head. Once you show 0.95 to the tenth power, the interviewer wants to know which of four levers you would pull first.

A runaway agent is a cost problem, a reliability problem and a product problem at once. The answer is part diagnosis, part guardrails, and part design for what happens when a budget runs out.

Money movement is where agent design stops being theoretical. The strong answer never lets the model be the control, and shows exactly where policy, approval and idempotency sit.

Decide which support tasks an agent can safely own. An 82% pass rate needs a denominator, a breakdown of failures and a comparison with today's service.

A RAG answer can fail in the retriever or in the generator, and one accuracy score cannot say which. The interviewer wants two evals, a production loop and a launch bar tied to what a wrong answer costs.

The strongest first move costs nothing and involves no tooling: read the traces. What you do with the notes, and in what order, is the rest of the answer.

95% agreement sounds like a yes. On its own the number says almost nothing, and the thirty-second arithmetic that proves it is what separates a launch gate from a dashboard.

An estimation question that tests commercial judgment. The inference bill is where the arithmetic starts; the number that decides the answer is somewhere else.

Usage counts are the trap. The answer that scores connects quality, behaviour, cost and risk to one business outcome, and says what evidence would change the primary metric.

The cheap option per conversation is the expensive one per customer, until you read how the vendor defines 'resolved'. Two calculations, and the second one is where the offer is decided.

Candidates jump to 'switch to a cheaper model'. The interviewer wants to see you find out why cost per user rose before choosing a lever, then pull the levers in the order that protects quality.

The security question every agent PM must answer well. Anyone can send your user an email, which means anyone can put instructions in front of the model. The strong answer stops trying to make the model resist and limits what a fooled model can do.

The top entry on the OWASP list for LLM applications. A PM should be able to explain it in a minute, distinguish the direct and indirect forms, and explain why it changes how products are designed.

Hiring is one of the clearest high-risk uses under the EU AI Act. The interviewer wants to see you turn obligations into product requirements and a roadmap, with dates stated carefully.

A platform metrics question. Token volume is the obvious answer and the incomplete one. The interviewer wants the developer funnel, reliability, economics and migration health in one coherent set.

A launch question where positioning, pricing, evaluation and capacity all have to line up. The interviewer wants to see you avoid cannibalising the wrong tier and give developers what they need to adopt it.

Deprecations are where platforms earn or lose developer trust. The interviewer wants a timeline, a recommended replacement with evidence, migration tooling, and special handling for customers who cannot move easily.

Rehearse a 40-minute build with time reserved for testing. Choose a small user task, make it work and explain the failures you found before proposing a launch.

A new term for a new skill. The interviewer wants a definition, a sensible use for PMs, and an honest view of where AI-built prototypes stop being trustworthy.

A worked live-round walkthrough. The trap is building a pretty summariser. The scoring path is a narrow extractor with structured output, a small test set that probes the hard cases, and an honest readout.

The part of the prototyping round that separates candidates. Ten minutes is enough for a small, sharp evaluation if you choose the cases well and grade them pass or fail.

An exact Given/When/Then cannot test a model that words things differently every time. The scored answer shows which criteria stay exact and how the rest become measurable.

Interviewers want a workflow, not a tool name. The scored answer shows the instruction file, the plan review, the permissions and the evaluation that make an afternoon's prototype worth trusting.

Explain your role in an AI project's failure, identify the cause and show what changed afterward. A model error alone does not explain the product decisions that exposed users to it.

STAR is the format employers name; adding a learning step and choosing stories with AI-specific judgment is what lifts it. How to structure, time and bank your stories.

A behavioural question with a technical core: how you turned a readiness argument into agreed criteria and shared evidence, what you were wrong about, and whether the relationship survived.