How to answer the stakeholder conflict interview question
The short answer
Interview Coach asks this question in these words:
Tell me about a time you disagreed with a senior stakeholder. What did you do, and how did it end?
Pick one real disagreement with someone senior to you, where each side wanted something you can name. Set the scene in two or three sentences, then say what you did yourself, in the order you did it, with "I". End with how it was settled, including any part that did not go your way, and with a figure or a record that shows the result. Spoken, that is about one to two minutes.
Check your own answer in Claude with Interview Coach, free
What the interviewer is checking
The question sounds like it is about conflict. It is about how you work when you cannot simply decide. The bank lists three things a strong answer does:
- It names the disagreement and what each side wanted. "We had different views" is not a disagreement. "The sales director wanted user testing cut from three weeks to one for a trade show demo; the test plan still had open defects" is one.
- It shows what you did yourself to move it, not only the meeting. A meeting is a place. What you prepared, who you spoke to first and what you proposed are actions.
- It says how it ended, including any part that did not go your way. An answer where you win everything can sound polished for the room. A split result, told plainly, is easier to believe.
How you describe the other person is part of the answer. A stakeholder who had a reason, even one you disagreed with, shows you understood the other side. A stakeholder cast as the villain shows the opposite.
A structure that works
Interview Coach describes a strong story answer in five parts, and its answer check looks for each one:
- Situation. Two or three sentences on the context and what was at stake.
- Action. What you did yourself, said with I, in the order you did it.
- Result. What changed, and how you know.
- Evidence. A figure before and after, or a record a reader could ask for: a defect tracker, steering minutes, a decision log.
- Length. About one to two minutes when spoken.
It also looks for words that weaken an answer: filler ("basically", "you know"), hedges ("I think", "maybe"), weak ownership ("helped", "was involved") and vague claims ("huge", "everyone was happy").
Answers as written, and what the check says
Illustrative, not a real client. Each answer below was sent on its own through the answer check of Interview Coach. All of them are also marked short for a spoken answer, because each is one or two sentences; the table shows the other finding, word for word, and one way to fix it.
| Answer as written | What the check says | What to change |
|---|---|---|
| We pushed back on the VP, we showed our numbers, and in the end we agreed a new date as a team. | Mostly we and the team. The interviewer cannot tell which part was yours. | Keep the team in the story, and add the steps that were yours: what you prepared, who you called, what you proposed. |
| I think the sponsor maybe had a point, and I guess I probably should have raised the risk sooner than I did. | Hedging or weak ownership words found. | If you raised it late, say so once and plainly, then say what you did next. |
| Basically the VP wanted the release in March and, you know, I kind of talked her into May instead. | Filler words found. | Drop the filler, then say how you made the case for May and what she weighed. |
| It was a huge disagreement with the sales director, but I handled it and in the end everyone was happy. | Vague amounts or claims found. Replace them with the figure or the record, if you have it. | Name what was disputed and what was decided, and where the decision is written down. |
| When the sales director asked to skip user testing, I set up a meeting, I walked her through the plan and I listened to her concerns. | No result is named. Say what changed. | Finish the story: what was decided, and what happened to the release. |
| I called the finance director, I showed him the test results, and he approved the extra time for the release. | No context is set before the action. Add what was at stake. | Open with the disagreement: who wanted what, and by when. |
| When the sponsor asked to cut user testing, I proposed a smaller first release, I got her agreement, and the release went ahead. | No figure and no named record. Name where the result shows, if you have it. | Name the record that shows the result, such as the defect tracker or the steering minutes. |
| When the sponsor asked to cut user testing, I proposed a smaller first release and I kept two weeks of testing. Defects after go-live fell to 4. | A figure is given, with no starting point. | Give the figure it fell from, and the record both come from. |
The check never writes a figure for you. If you have no record of the result, say what you saw instead, and say plainly that it was not measured.
An illustrative answer
Illustrative, not a real client. Every figure is invented. This answer gets all nine marks of the story check: length, situation, own action, team versus me, result, a before and after figure, and no vague words, filler or hedges.
Last year I ran the rollout of a new claims portal for an insurance client. Six weeks before go-live, the sales director asked to cut user acceptance testing from three weeks to one, so her team could demo the portal at a trade show. I disagreed, because the test plan still had open defects in the payment screens. I did not argue in the meeting. I pulled the defect tracker, I showed her which screens her customers would touch at the show, and I proposed a smaller first release: the screens she needed, tested in one week, and the payment screens two weeks later. She did not like the split, and I took both options to the steering meeting with the risks written down. The sponsor approved the split release. The demo went ahead on time, and defects found after go-live fell from 31 on the previous release to 9, per the defect tracker. Since then I bring the defect list to the first conversation, not the second.
Why it works. The sales director has a reason (the trade show), so she is not a villain. The actions are the speaker's own and in order. The result includes the part she did not like. The figure has a starting point and a named record.
Choosing your story
- Pick a disagreement about the work. Dates, scope, testing, money, a release. A clash of personalities is hard to tell without blaming someone.
- Pick someone senior to you. The question says senior stakeholder: a sponsor, a director, a client executive. A disagreement with a peer answers a different question.
- Pick a story that ended. If it is still open, the result is a guess.
- Pick one you can back up. The interviewer can ask for the record, and a reference can be asked about it. Your resume is where the interviewer looks first, so a story that matches a line on it is easier to defend. Get a free AI review of your resume and see which lines Reed flags first.
What the check cannot see
The answer check reads the words of your answer: it finds a situation, your own actions, a result and a figure or a record. It does not judge whether the story is true, whether you were right, or how you sound. Two answers can get the same marks while one is honest and specific and the other is not. Use the marks to find what is missing, then ask yourself the questions an interviewer would ask next: what would the sales director say about this, and which document shows it?
Prepare the follow-up questions
Interviewers often ask one more question after this one. Have an answer ready for each:
- What would you do differently with the same stakeholder?
- What did the disagreement cost the project, in time or money?
- How did you work with that person afterwards?
Run the free review on your own resume lines.
Check your answer with Interview Coach in Claude
This question is in the shared part of the Interview Coach question bank, not tied to one role. Write your answer the way you would say it and ask for a check.
- It reads the answer for a situation, your own action said with I, a result, and a before and after figure or a named record.
- It flags filler, hedging, weak ownership and vague claims, and says when the answer is short or long for a spoken answer.
- It does not judge whether the story is true or good, and it never adds a figure you did not give.
Your answers start from your resume. The free review quotes your own lines and flags the 5 to fix first, so you know which lines an interviewer may question.
Free in Claude, no account. We do not store the text you send through it.
Questions
What if I have never disagreed with a senior stakeholder?
Say so, then tell the closest story you have: a disagreement with a client, a peer in another team or a vendor, and what you did. Do not stretch a small exchange into a conflict. An interviewer who asks for detail will find the gap quickly.
Should my answer show that I won the argument?
No. The question asks how it ended, and a strong answer includes any part that did not go your way. What the interviewer weighs is how you handled it: what you prepared, how you proposed a way forward and how you worked with the person afterwards.
Does Interview Coach know whether my story is true?
No. Interview Coach runs in Claude and checks the structure of an answer by fixed rules: a situation, your own action, a result, and a figure or a record. It does not judge whether the story is true or good. You decide what to say.
Keep going
- Interview questions: Project manager interview questions
- Interview questions: Product manager interview questions
- Interview questions: Program manager interview questions
- Guide: How to answer the failed project question
- Guide: How to answer the influence without authority question
- Guide: How to answer the hardest deadline question
- Guide: How to answer the scope change question
- Guide: How to answer the project risk question
- Guide: How to answer the product metric question
Last updated: October 13, 2026