Interviewers ask scenario questions to see how you decide, so prepare decisions, not definitions. Learn six common situations, practise a five-step answer (read, name the bound, check the source, decide, record), and rehearse aloud with sample cases until you can give a clear, reasoned answer in under two minutes.
Why do interviewers use scenarios for agent roles?
Because definitions are easy to memorise and tell them little. Anyone can learn that depth 2 means an agent drafts and a person sends. What an interviewer needs to know is whether you will stop a polished payment that rests on an emailed instruction, or approve a refund just above a limit because the customer is upset. Scenarios surface that. The page on what a scenario-based interview is explains the format; this playbook is about preparing for it.
The guide to AI skills for job seekers sets out the skills employers want to see. Scenario questions are where you show them.
Which situations come up, and what are they testing?
| Scenario type | What it is testing | A strong answer includes |
|---|---|---|
| A payment to new bank details from an email | Source judgement; red lines | That an external claim cannot authorise a payment; holding and confirming via a sealed or signed source |
| An action just above the customer's limit | Respect for limits; escalation | Checking the justification, then sending to the named approver rather than approving |
| A request for personal data from someone unverified | Data protection; identity | Holding until identity is confirmed; checking purpose |
| An urgent request from a "senior manager" | Resistance to pressure | That seniority does not change provenance; confirming through a known channel |
| Refusals rising after a policy change | Reading the workspace | Checking whether the agent's sources were updated; raising it |
| An agent that has just failed a certification run | Understanding depth and certification | That it keeps only the depth it cleared, or drops to depth 1 the same day if it cleared none; expecting more held actions |
What is a good way to answer?
Use five steps, in order, and say them out loud.
- Read the situation back. One sentence: what the agent proposed and what the verdict was. It shows you listened and buys a few seconds.
- Name the deciding bound. Every action meets five bounds at once: role scope, certificate, sources, the customer's own limits and the platform guardrails. The lowest wins. Say which one decides here.
- Check the source. Name the key fact and its provenance: sealed, signed, declared or external.
- Decide. Approve, correct, hold, escalate or refuse, and say who you would pass it to if it is above your authority.
- Record. Give the one-line reason you would write.
If the interviewer pushes back ("but the customer is very upset", "the director is waiting"), hold your position and explain why the source or limit has not changed. Pressure is often the point of the follow-up.
What does a worked answer sound like?
Scenario: "An agent has drafted a refund of 450 to a long-standing customer but may not make it. The customer says the item arrived broken. Our limit for refunds without approval is 300. What do you do?"
A strong answer: "The agent drafted a refund and it was refused, so a person must make it. The deciding bound is the customer's own limit, because 450 is above 300. I would check the evidence: is there a sealed order record and anything signed, such as a courier damage report, or only the customer's own statement? If the evidence supports it, I would send it to the named approver with the facts, not approve it myself. I would record: 'Refund justified by order record and damage report; above 300 limit; escalated for approval.'"
That answer takes about a minute and shows limits, sources, escalation and a record.
How should you practise?
- Write ten scenarios from the table, using sample values and your own industry.
- Answer each aloud, timing yourself. Aim for under two minutes.
- Record yourself and listen for the five steps. Which did you skip?
- Add a pushback to each scenario and answer it.
- Practise with someone who can play a sceptical interviewer.
Scenario-based learning builds exactly this habit; the page on what scenario-based learning is explains why it works. Module tests in the Operator track at Pryme Intelligence Academy are set in your own industry and role and use the same kind of situation, which makes them useful practice.
How do scenario questions differ from behavioural questions?
Behavioural questions ask what you did in the past ("tell me about a time"). Scenario questions ask what you would do now. Prepare both. For behavioural questions, use real decisions from your work or a practicum, structured with the STAR answer template for AI agent interview questions. For scenarios, use the five steps above. Many interviews mix them.
What should you measure?
Whether each practice answer includes all five steps. How long it takes. How often you hold your position correctly under pushback. If you consistently skip the source check or the record, drill those steps alone.
Where do candidates usually go wrong?
They define terms instead of deciding. They approve to please the imagined customer. They forget to say who they would escalate to. They give no reason. And they cave when pushed. A calm, reasoned "no, and here is why" often impresses more than a fast "yes".
For the rest of the interview, see how to prepare for an AI operations interview, and prepare your own questions with the questions to ask in an AI operations interview template.
Questions people ask
What if I do not know the answer to a scenario?
Say what you would check and who you would ask. "I would hold it and escalate to the named approver" is a safe, sensible answer when you are unsure, and it shows you know your limits.
Do I need to use the exact terms, like deciding bound?
They help, if the employer uses governed agents. If not, describe the idea plainly: which limit or rule decided the outcome, and where the key fact came from.
How many scenarios should I prepare?
Ten covering the six types in the table is enough for most interviews. Depth of reasoning matters more than the number you have memorised.