In this article
Before you start
For where this round sits among the others, see interview loops.
Why interviewers ask this
A role-play shows how you behave in a hard conversation, which a rehearsed story cannot. IGotAnOffer's guide, last updated June 2026, reports that Stripe engineering manager (EM) candidates play the manager while the interviewer plays a direct report in a realistic conflict. It says there are no scripts.
That is a reported format. No company publishes the rubric, so treat every company detail on this page as candidate-reported.
The same guide says the round assesses whether you can "balance business needs against the person in front of you, in real time." A weak answer lists what the candidate would do. A strong answer holds the conversation: it asks, listens, states the business need honestly and ends with a next step.
The manager role-play round from first principles
- Manager role-play round
- The manager role-play round is an interview round in which the candidate plays a manager and the interviewer plays someone the manager leads, such as a direct report, working through a realistic people problem as a live, unscripted conversation that the interviewer observes and judges.
- Direct report
- A direct report is an employee who reports straight to a given manager, so that manager sets their priorities, gives them feedback and takes part in decisions about their growth and pay. In this round, the interviewer usually plays this person.
In plain words
Think of a driving test, not a written exam. A written exam asks what you would do at a junction. A driving test puts you at the junction. The analogy breaks in one place: a driving test follows fixed rules, while here the other person reacts to every sentence you say, and there is no script.
The guide cited above says you are expected to handle the scenario "as a live conversation, not describe what you would do in the abstract." One candidate write-up (Sridharan, Medium) describes three set-ups. The first is a one-to-one where you coach someone through a problem. The second is a team meeting where you build consensus or mediate a conflict. The third is a code review where the engineer pushes back. LeadDev says you may be asked to role-play a situation with a would-be report (Joshi, LeadDev, 2026).
In one precise sentence: the round tests whether you can ask, listen and decide in real time with a person whose goals conflict with a business need.
Step 1: Ask before you decide
The conversation opens with a question, not a verdict: that is the first move in a manager role-play. Input: the scenario card and the interviewer's first line. Change: you invite the other person to describe where they are before you say what is changing. Output: you hold facts you did not have, and the person feels heard.
Take the scenario IGotAnOffer reports for Stripe: your report is working on a project they care deeply about, with high visibility and a clear path to promotion. If you open with "I need you on something else," you spend the conversation's goodwill in one sentence. If you open with "tell me how the project is going and what you want from it," you learn how attached they are, what they fear losing and whether they know a deadline you do not.
Asking is not stalling. Keep it to a couple of questions, then move on. You now know what the person wants, which sets up the next step.
Step 2: State the constraint plainly
A strong role-play states the business constraint plainly, with what is fixed and what is flexible. In another reported Stripe scenario, a senior engineer is excited about an upcoming initiative and you must assign them an urgent 12-week compliance audit instead.
The fixed part is that you must assign them the audit. The flexible parts are when the initiative starts, how the audit work is shared and how the work is recognized.
Input: what you heard in Step 1. Change: vague pressure becomes a clear boundary. Output: the person knows where they can still influence the outcome. Do not hide the constraint behind softer words, and do not call it optional when it is not. The same guide frames the test as balancing the business need against the person in front of you, so name both.
Step 3: Work out options together
Offering two or three real options turns an order into a decision you make with the person. Input: the constraint and what the person told you they want. Change: you propose choices, such as moving the start date, sharing the audit work, tying it to a development goal or arranging cover for the project, and you ask which one works or what they would change. Output: a choice both of you own.
Do not promise outcomes you cannot control, such as a promotion. Promise what you can do, such as describing this work accurately in their next review.
One candidate write-up notes that in a code-review variant the engineer may push back on your suggestions and you may be expected to coach them through the conversation. When the interviewer pushes back, answer the concern behind the words instead of defending yourself.
Step 4: Agree the next step and say it back
The conversation ends with a named next step, an owner and a date. Input: the option you chose together. Change: a loose agreement becomes a commitment. Output: a closing line the observers can score.
Say it back in two sentences: what was agreed, what you will do, what they will do and when you will talk again. Then ask how they feel about it. If the person is still unhappy, say so fairly and leave them clear about what happens next. You are not required to win agreement. You are required to leave the person informed and respected.
Step-by-step description
- Open with a question, not a verdict.
- Say what is fixed and what is flexible.
- Decide the way forward together.
- Name an owner and a date, then say it back.
- The conversation opens with a question, not a verdict.
- The business constraint is stated plainly, with what is fixed and what is flexible.
- The conversation ends with a named next step, an owner and a date.
A worked example: running a 45-minute discovery call
The customer variant follows the same four-part shape. Candidates report that Anthropic's applied AI loop includes a customer-conversation simulation in which the interviewer plays a fictional buyer, such as a vice president of engineering at a 5,000-person fintech evaluating Claude for an internal copilot, and the candidate is asked to run a 45-minute discovery call (getperspective.ai, 2026). Another guide lists it as a live role-play with no editor that covers discovery, constraints and data-privacy boundaries, and says reports show it eliminates the most candidates who cleared the coding rounds (theforwarddeployed.io).
Our Anthropic interview process page and the forward deployed and applied AI engineer rounds page cover the wider loop. One candidate guide (theforwarddeployed.io) recommends this order: ask what outcome the business is measured on and who owns it, ask where the data lives, ask what they already tried, reflect the constraint back, and only then propose a narrow first slice.
Here is an illustrative split of the 45 minutes, our own example and not a sourced rubric: opening 5 minutes, discovery 25, narrow proposal 10 and next steps 5.1 In the illustrative split, discovery takes 25 of the 45 minutes, about 55.6%.1 The narrow proposal comes only after discovery.
Text description of the diagram
- In the illustrative split, discovery takes 25 of the 45 minutes.
- The narrow proposal comes only after discovery.
Where does the round sit in the loop?
The manager role-play is usually one round among several, not the whole loop. IGotAnOffer reports a Stripe loop of up to six rounds, with the role-play appearing in nearly every detailed review from 2022 onward. For how another company structures its people-focused rounds, see the Meta engineering manager interview page.
Knowing it is half the job. Saying it is the other half.
Interview Clozo is an AI interview copilot for real interview rounds: it hears the question and puts a strong answer on your screen, and you say it in your own words. See the features or how it works.
Start Free Trial →The Staff-level answer
The answer in this round is the opening of the conversation, and an opening of about a minute sets its tone. Imagine the interviewer, as your direct report, is excited about an upcoming initiative and you must assign them an urgent compliance audit instead.
You need to move me off the initiative I'm excited about and onto an urgent compliance audit. Go ahead.
Thanks for making time. I know you're excited about the new initiative, so tell me where it stands and what you hope it leads to. (pause, listen) Thank you, that helps. Here is the part I can't change: the compliance audit is urgent and needs you as its owner. What I can shape with you is when the initiative starts, which audit work we share, and how this work is recognized in your reviews. Which of those matters most to you? (pause, listen) Then let's agree who does what and when we next check in, and I'll say it back so we're both clear.
What makes it Staff-level: it asks first and pauses to listen, states the fixed constraint without hiding it, names what is flexible, promises nothing it cannot control and commits to a next step.
The rubric
This table is a preparation lens built from the behaviors reported above. It is not a published scoring sheet from any company.
| Dimension | Weak answer | Strong answer | Staff answer |
|---|---|---|---|
| Opening | Announces the decision at once | Asks how the person is doing on the work | Asks, then frames the shared goal in one sentence |
| Listening | Waits for a turn to talk | Repeats back what the person said | Reflects the fact and the feeling, and changes the plan because of it |
| Constraint | Hides it or blames "the company" | States it plainly and owns it | States what is fixed, what is flexible and why |
| Pushback | Defends or gives in | Stays calm and answers the concern | Separates the concern from the decision and offers a trade |
| Close | Ends with "let's keep talking" | Names a next step | Names owner, date and follow-up, and says it back |
Three variants of this question
How do you move a high-performing report off a project they love?
Ask what the project means to them, state that the urgent work needs an owner, offer options that keep their growth visible and agree a date to review. This is the scenario IGotAnOffer reports for Stripe, a report on a high-visibility project with a path to promotion. Never promise the promotion.
How do you tell a report their performance is below the bar?
Describe the specific gap with one or two concrete examples, state the expectation plainly, ask for their view, offer support and agree a review date. LeadDev lists dealing with poor performance among the common management challenges (Joshi, LeadDev, 2026). Do not soften it into a vague hint, and do not leave without a date to check progress.
How do you run a 45-minute discovery call with a buyer played by the interviewer?
Ask about the outcome, the data and what they tried before, reflect the constraint back and propose only a narrow first slice, as the reported Anthropic simulation rewards. The worked example above gives an illustrative time split.
Common mistakes
- "I would sit down with them and have a conversation." (wrong) That describes the conversation instead of having it, and the round expects it live. (right) "Thanks for making time. Tell me where the project stands."
- "Here's what we're doing: you're on the audit." (wrong) A decision announced first leaves nothing to discuss. (right) "Before I say what's changing, I'd like to hear what this project means to you."
- "Do this and I'll make sure you're promoted." (wrong) It promises something you cannot control. (right) "I'll describe this work accurately in your next review, and we'll agree what success looks like."
- "Here's how our platform would solve that." (wrong) Pitching before discovery is the reflex the round punishes, according to candidate guides such as getperspective.ai. (right) "What outcome is your team measured on, and who owns it?"
Follow-up questions
How is a manager role-play interview different from a behavioral interview?
A behavioral interview asks you to describe something you did before. A role-play asks you to do it now, with someone who reacts. IGotAnOffer describes the Stripe round as a live conversation, not a description of what you would do in the abstract.
Do only managers get role-plays?
No. Anthropic applied AI candidates report a customer-discovery role-play where the interviewer plays a buyer, as covered in the forward deployed and applied AI engineer rounds page.
Is the role-play scored on whether you reach agreement?
Not according to what is reported. IGotAnOffer says the Stripe round assesses whether you can balance business needs against the person in front of you, in real time. You are not required to win agreement; you are required to leave the person informed and respected, with a named next step (Step 4).
How should I prepare for the manager role-play round?
LeadDev suggests building a bank of stories, using the Situation, Task, Action, Result (STAR) structure to stay concise and knowing your leadership style and gaps, and it lists poor performance, conflict, promotions and deadlines as common challenges (Joshi, 2026). STAR suits stories, so for a role-play also rehearse out loud with another person. See interview skills for the general habits.
What if the interviewer pushes back hard or the scenario feels unfair?
Stay with the person's concern, restate your reasoning in one sentence and offer a trade instead of repeating yourself. If you still disagree, say so fairly and agree what happens next. That is a legitimate way to end.
- The manager role-play round is a live simulation: you play the manager, the interviewer plays a direct report.
- Open with a question, not a verdict.
- State what is fixed and what is flexible, and promise nothing you cannot control.
- Close with a named next step, an owner and a date, said back.
- No company publishes its rubric, so treat company formats as candidate-reported.
Sources
- Stripe Engineering Manager Interview (questions, process, prep) — IGotAnOffer, 9 Jun 2026
- How to prepare for your engineering manager interview — LeadDev (Vaidehi Joshi), 29 Jun 2026
- Cracking the Engineering Manager interview - Part 1 — Medium (Srivatsan Sridharan), 26 Oct 2026
- Anthropic Forward Deployed Engineer Interview Guide — theforwarddeployed.io, 26 Oct 2026
- Anthropic Applied AI Engineer interview process — getperspective.ai, 26 Oct 2026
