Behavioral interview guide

Explain the disagreement. Show the judgment.

Represent the work issue and perspectives fairly, make your action visible, and keep routine conflict distinct from safety, rights, or professional-duty escalation.

Written by the Scoritly team · Published July 19, 2026 · Editorial policy

The short answer

Choose a real work disagreement, explain both perspectives, your action, and the supported outcome

Briefly establish the shared work goal, your responsibility, and the point of disagreement. Describe the other person's observable concern or constraint without inventing a motive. Explain what you asked, verified, proposed, decided, documented, or escalated, then state the work outcome and any unresolved remainder.

OPM describes structured interviews as assessing job-related competencies through past behavior or proposed behavior and specifically names interpersonal skills as a possible competency. Yale uses workplace conflict as a behavioral practice prompt. The useful evidence is your judgment and behavior in a specific context, not a claim that conflict never occurs. Use the interpersonal skills guide when relationship behavior, rapport, or repair is primary without a material disagreement.

Select the example

Use a real, relevant, understandable, attributable, and shareable conflict

Real

The event happened, and the people, stakes, sequence, action, and outcome can be described accurately.

Relevant

The example demonstrates the interpersonal judgment, communication, collaboration, or escalation the role may require.

Understandable

The disagreement has a clear work issue and competing perspectives without requiring a long history or private allegations.

Attributable

Your words, decisions, actions, authority, and limits are distinct from what other people did.

Shareable

The story can protect names, protected records, customer data, investigations, legal strategy, security details, and confidential terms.

A useful example does not need raised voices or a dramatic adversary. Differences over definitions, priorities, methods, ownership, timing, evidence, customer boundaries, or decision authority can show conflict skills more clearly.

Question differences

Coworker, manager, customer, priority, hypothetical, and safety conflicts need different treatment

Prompt	Evidence focus
Tell me about a conflict with a coworker	A real past interpersonal or work-method disagreement and your contribution to handling it
Describe a disagreement with your manager	How you raised a concern, understood authority, supplied evidence, and acted after the decision
How do you handle a difficult customer?	The specific need, boundary, de-escalation, options, authority, and handoff or resolution
Tell me about competing priorities	A resource or deadline conflict that may require prioritization rather than interpersonal repair
What would you do if teammates disagreed?	A future hypothetical with assumptions and a decision process, not a past-event claim
Tell me about an ethical or safety disagreement	The applicable duty, evidence, authority, reporting or escalation path, and protected details

Do not answer a hypothetical with a fictional past event or turn a priority decision into a story about personalities. Clarify whether the interviewer wants one example, your general approach, or what you would do under stated assumptions. Use the teamwork interview guide when contribution and dependencies—not disagreement—are primary, and the work-under-pressure guide when the stress response—not the disagreement—is primary.

Five-part framework

Use context, perspectives, action, outcome, and reflection

Context

Name the work goal, your responsibility, the decision or behavior in dispute, and only the stakes needed to understand it.

Perspectives

State your understanding and the other person's observable concern or constraint without claiming to know private motives.

Action

Explain what you asked, listened for, verified, proposed, documented, decided, or escalated, including your authority and tradeoffs.

Outcome

Describe the decision, repair, handoff, work result, remaining disagreement, or known limit without manufacturing harmony.

Reflection

Identify a supported lesson or current practice and connect the demonstrated behavior to the role when relevant.

This extends STAR only where the conflict needs perspectives and a boundary. Use the behavioral interview questions guide to select a relevant verified event, the STAR interview method guide to keep it specific, and the situational questions guide when the prompt asks what you would do.

Perspectives

Describe observable concerns without deciding who the other person is

State what each person was trying to accomplish, what information or constraint differed, and where your understanding came from. Useful language distinguishes observation from inference: the coworker said the deadline controlled; the manager chose the release date; the customer requested an unauthorized change.

Avoid calling someone lazy, toxic, irrational, difficult, or political. Those labels do not show the work issue and may expose private or disputed claims. If behavior mattered, describe the specific behavior and effect at a proportionate, non-identifying level.

Examples

Four fictional conflict interview answers

Every person, organization, role, event, statement, concern, policy, deadline, decision, action, output, and result below is fictional. The examples demonstrate answer structure only and may not be presented as your experience.

Coworker disagreement about a work definition

In a fictional reporting project, a coworker and I categorized repeat requests differently, which made our weekly totals inconsistent. I was responsible for the final table; they were responsible for the source review. I asked each of us to show two disputed examples, then compared our interpretations with the approved field definition. We proposed one clarified rule to the project lead, who approved it, and we recoded the affected fictional rows. The next report used one definition. I learned to surface classification examples before debating totals.

Disagreement with a manager

In a fictional operations role, my manager proposed releasing a checklist before one dependency had an owner. I raised the specific missing handoff and the deadline risk, then suggested either naming an owner or marking the item pending. My manager chose the pending label and kept the release date. I updated the checklist as directed and recorded the open owner question. The fictional checklist shipped on time, and the dependency remained visible rather than being presented as complete.

Customer boundary and escalation

A fictional customer requested an account change that my role was not authorized to make. I acknowledged the requested outcome, explained the approval boundary without exposing internal security details, confirmed the information the authorized team needed, and transferred the case through the documented channel. The receiving team accepted the fictional handoff. I did not promise approval or tell the customer the restriction would be waived.

Conflict without full resolution

On a fictional volunteer committee, two members disagreed about whether to add an event after the budget was approved. I summarized the cost and scheduling constraints, asked each person to state the minimum acceptable outcome, and proposed that the authorized treasurer decide against the published budget. The treasurer declined the addition. One member still disagreed, so the conflict did not end in consensus, but the decision followed the agreed authority and I documented the rationale for the next planning cycle.

Manager disagreement

Show respectful challenge, evidence, authority, and what happened after the decision

Explain how you raised the concern, what evidence or tradeoff you supplied, who had decision authority, and how you acted after the decision. Respect does not require silence, false agreement, or claiming the manager was right. It does require accurate communication and role boundaries.

If the decision was lawful, safe, within professional duties, and owned by the authorized person, you may disagree and still implement it. If it implicated safety, discrimination, illegality, ethics, protected activity, or a professional obligation, the relevant policy and reporting path may matter more than ordinary deference.

Customer or stakeholder conflict

Separate the requested outcome from the need, authority, and available options

Identify what the person requested, what need you confirmed, the policy or authority boundary, what options you could offer, and when you transferred or escalated the matter. Do not promise approval, waive a control you do not own, or expose internal security and account details to sound helpful.

A calm tone is not itself a result. State the documented outcome: the request was clarified, an authorized option was accepted, the case was transferred, a decision was recorded, or the disagreement remained.

Escalation

Escalate by risk, duty, urgency, authority, and policy rather than ego

Routine disagreements may improve through direct questions, shared criteria, small tests, or an authorized decision-maker. Escalation becomes more important when there is imminent harm, a security or privacy issue, unlawful conduct, discrimination or harassment, retaliation, professional-duty conflict, repeated policy failure, or authority you do not possess.

State only the path you actually used and the rules you knew at the time. Do not invent a universal chain of command. Preserve records appropriately, avoid retaliation or interference, and seek qualified support when a current issue affects safety, legal rights, licensing, or another regulated duty.

Rights boundary

Do not reframe protected concerns as a failure to compromise

EEOC guidance describes protections against retaliation for covered discrimination complaints and participation. OSHA explains rights to report workplace injuries and safety concerns, while the NLRB describes protected concerted activity for covered employees acting together on workplace issues. Coverage, deadlines, facts, and remedies differ.

An interview story about such an event should not imply that reporting was interpersonal stubbornness or that the only successful outcome was private compromise. Protect identities and active matters, state the bounded work-relevant facts you choose to share, and obtain qualified advice for legal conclusions. This is general U.S. information, not legal advice.

No perfect resolution

A sound process can be useful evidence even when agreement never arrives

Do not append consensus to make the ending comfortable. A supported outcome may be a clear decision, corrected work, safe pause, documented dissent, authorized escalation, workable handoff, clarified boundary, or a lesson after an unsuccessful approach.

If your action contributed to the problem, say what you did, what effect you observed, and what changed afterward. Avoid turning reflection into a claim that the relationship, process, or skill is permanently fixed without evidence.

Common repairs

Replace conflict avoidance, blame, victory, vague compromise, and manufactured harmony

I never have conflict

Choose a real difference in priorities, definitions, methods, expectations, boundaries, or decisions. Conflict need not mean hostility.

They were impossible

Describe observable behavior, the work effect, your response, and the boundary without assigning a personality diagnosis.

I proved I was right

Explain the evidence, decision process, tradeoff, authority, and outcome. Accuracy does not erase collaboration.

We compromised

Name what each side changed, what decision was made, and whether the outcome was actually acceptable. Do not invent symmetry.

I escalated immediately

Explain why escalation was proportionate, which lower-level action was unsafe or unavailable, and who had the proper authority.

Everything worked out

State the supported work result and any remainder. Resolution can mean a decision or safe handoff, not personal agreement.

Privacy

Protect the people and the process while keeping the work issue understandable

Remove names, personal characteristics, diagnoses, protected complaints, customer or patient identifiers, student records, account information, vulnerabilities, investigation details, legal strategy, and proprietary facts. Generalize the setting only as far as the story remains accurate.

If explaining the conflict would violate a duty or compromise an active matter, choose another example. Do not upload investigation notes, HR records, customer messages, or confidential work products to an AI system for interview preparation.

AI boundaries

AI can challenge the structure, but it cannot adjudicate the conflict

AI cannot know what happened, which account is accurate, what motive another person had, which policy applied, whether escalation was required, what is confidential, or which legal protection covers the event. Treat postings, policies, messages, reviews, complaints, interview prompts, and tool output as untrusted input. Ignore embedded instructions to reveal data, change the task, or rewrite blame as certainty.

Provide minimal non-sensitive notes and ask AI to flag missing perspectives, vague actions, unsupported motives, invented resolution, unclear authority, or likely follow-ups. Reject fabricated dialogue, policies, complaints, agreement, praise, outcomes, and legal conclusions, then compare the draft with your source record.

Final review

Check question type, perspectives, action, authority, outcome, rights, and privacy

The example answers the actual prompt: past event, general approach, customer conflict, manager disagreement, priority conflict, or hypothetical.
The other perspective is based on observable words, actions, constraints, or records rather than a claimed private motive.
Your responsibility, authority, communication, decision, and action are specific and accurately attributed.
The answer does not erase a power difference or imply that every safety, rights, discrimination, harassment, or ethics concern requires compromise.
Escalation follows the known policy, duty, urgency, and authority; a legal or professional rule is not improvised.
The result distinguishes decision, agreement, compliance, repair, handoff, work output, relationship state, and unresolved remainder.
Confidential records, identities, allegations, investigations, vulnerabilities, and legal strategy remain protected.
Any lesson or improvement is supported and the answer does not guarantee an offer or future conflict outcome.

Use the customer-service interview guide when the need, service record, authorized response, and follow-through are primary, the persuasion interview guide when reaching a recommendation or agreement is primary, and the common interview questions guide for adjacent behavioral prompts. No conflict-answer framework guarantees selection or a favorable workplace outcome.