How to answer the conflicting requirements interview question

Written by Reed, an AI career analyst at PM Career Desk.Reed, an AI, drafted this guide from the Interview Coach question bank and its answer check. The question is shown word for word as Interview Coach asks it. It is general guidance and promises no outcome. The example answers and figures are invented.

The short answer

Interview Coach asks this question in these words:

Tell me about requirements that were unclear or in conflict. How did you get to agreement?

Pick one set of requirements where two groups wanted different things, or nobody could say what they wanted. Name the parties and the exact point of conflict. Then say which technique you used to get to agreement: a workshop, a process model, a prototype, a decision table. End with what was agreed, who signed off, and where the agreement was recorded.

Check your own answer in Claude with Interview Coach, free

What the interviewer is checking

For a business analyst this is the core of the job. The interviewer wants to hear a technique, not charm: anyone can "talk to both sides". The bank lists three things a strong answer does:

Names the parties and where their needs conflicted. Finance wanted invoices approved in one step, compliance wanted two. Name the groups and the exact disagreement.
Shows the technique you used: a workshop, a model or a prototype. A facilitated workshop with a decision table, a swimlane model, a clickable prototype. Say why that technique fit this conflict.
Says what was agreed, who signed off and where it was recorded. The agreed rule, the people who signed it, and the document that holds it: the requirements specification, a decision log, a sign-off email.

Avoid a story where you decided the requirement yourself. The analyst brings the parties to a decision; the business owns it.

A structure that works

Interview Coach describes a story answer in five parts:

Situation. Two or three sentences on the context and what was at stake. Here: the system, the parties and the conflict.
Action. What you did yourself, said with I, in the order you did it. Here: the technique you chose and how you ran it.
Result. What changed, and how you know. Here: what was agreed.
Evidence. A figure before and after, or a record a reader could ask for. Here: the sign-off, the specification or the decision log.
Length. About one to two minutes when spoken. Spoken at a normal pace, one to two minutes; the check marks an answer under 60 words as short.

The answer check reads the answer for a situation set before the action, at least two actions said with I, a result near the end, and a before and after pair of figures or a named record. It also reads the balance between "we" and "I", the length of a spoken answer, and words that weaken an answer: filler, hedges, weak ownership and vague claims.

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
When finance and compliance wanted different payment approval rules, a joint workshop was run with a decision table and the rule was written into the specification, and both owners approved the rule, per the decision log.	No sentence says what you did yourself, with I.	Say which of these steps were yours, with I.
When finance and compliance wanted different payment approval rules, I ran a joint workshop with a decision table, and both owners approved the rule, per the decision log.	Only one first person action found. Say what you did yourself.	Add the second step that was yours, in the order you took it.
When the rules conflicted, we met finance, we met compliance, we mapped rules, we drafted options and we ran reviews. I ran a workshop and I wrote the rule, and both owners approved it, per the decision log.	Mostly we and the team. The interviewer cannot tell which part was yours.	Give the team's work one sentence, then say which calls were yours.
I ran a joint workshop with a decision table and I wrote the rule into the specification, and both owners approved the rule, per the decision log.	No context is set before the action. Add what was at stake.	Open with what was at stake before you acted.
When finance and compliance wanted different payment approval rules, I ran a joint workshop with a decision table and I wrote the rule into the specification, per the decision log.	No result is named. Say what changed.	Say what changed in the end, and where it shows.
When finance and compliance wanted different payment approval rules, I ran a joint workshop with a decision table and I wrote the rule into the specification, and both owners approved the rule.	No figure and no named record. Name where the result shows, if you have it.	Name where the outcome is recorded, or give the figure before and after.
When finance and compliance wanted different payment approval rules, I ran a joint workshop with a decision table and I wrote the rule into the specification, and both owners approved the rule in 3 weeks.	A figure is given, with no starting point.	Give the starting figure too, or name the record that holds both.
When finance and compliance wanted different payment approval rules, I basically ran a joint workshop with a decision table and I wrote the rule into the specification, and both owners approved the rule, per the decision log.	Filler words found.	Drop the filler word and say the step plainly.

The check never adds a figure or a record for you. If no agreement was reached, say who decided and how it was recorded.

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, evidence, and no vague words, filler or hedges.

When a logistics company replaced its accounts payable system, finance and compliance wanted different approval rules for supplier invoices. Finance wanted a single approval under a set amount to keep payments fast; compliance wanted every invoice approved twice after an audit finding. I met each group separately to understand the reason behind each rule, and I found that compliance cared about new suppliers, not repeat ones. I ran a joint workshop with a decision table that crossed supplier history with invoice amount, and I let both groups fill the cells together. They agreed that invoices from new suppliers or above the threshold need two approvals, and the rest need one. I wrote the rule into the requirements specification, and the heads of finance and compliance signed it off the same week, per the decision log. After go-live, the share of invoices with two approvals fell from all of them to 31 percent, per the payables dashboard.

Why it works. The parties and the conflict are specific. The analyst finds the reason behind each position, picks a technique that lets both sides decide together, and closes with a signed record and a before and after figure.

What the check cannot see

The answer check reads the words of your answer, not the agreement behind them. This answer, sent on its own, gets every mark except length:

When the rules conflicted, I ran a workshop and I wrote the rule, and both owners approved it, per the decision log.

It passes every mark but length. An interviewer would ask: who were the parties, what did each want, why that technique, and what rule came out? "I ran a workshop" is the most common analyst answer; the content of the workshop is what sets yours apart.

Choosing your story

Pick a conflict between named groups. Two departments, a client and a vendor, two regulators. Vague "stakeholders" make the conflict sound invented.
Pick a technique you can describe. A decision table, a process model, a prototype. Be ready to draw it on a whiteboard.
Pick one with a sign-off. The question asks where the agreement was recorded; a verbal agreement is a weaker ending.
Unclear counts as well as conflicting. Requirements nobody could state are the same question; the technique is how you made them clear.

Your resume is where an interviewer looks for these stories, and a line such as "facilitated requirements workshops" invites this question. Get a free AI review of your resume and see which lines Reed flags first.

Prepare the follow-up questions

What would you have done if the two groups had not agreed in the workshop?
How did you keep the requirement stable after sign-off?
Which elicitation technique do you use most, and why?

Run the free review on your own resume lines.

Check your answer with Interview Coach in Claude

This question is in the business or process analyst track of the Interview Coach question bank. 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.

Check my answer in Interview Coach, free Review my resume, free

Free in Claude, no account. We do not store the text you send through it.

Questions

What if a senior person overruled both groups?

That is still an answer. Say how you prepared the decision, what options you put in front of that person, and how the decision was recorded. The analyst's part is the clarity of the choice.

Is this question only for business analysts?

It is in the business and process analyst track of the Interview Coach question bank. Product owners and product managers meet it as well; the same structure works.

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, 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: Business analyst interview questions
Guide: How to answer the defect before go-live question
Guide: How to answer the process mapping question
Guide: How to answer the stakeholder conflict question
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

Last updated: October 14, 2026