Behavioral: Cross-Functional Disagreement and a Manager Conflict You Got Wrong

Read the full interview experience this question came from →

Quick Overview

A senior behavioral question on conflict: describe a significant disagreement with a partner from another function and a conflict with your manager in which you turned out to be wrong. It tests how you raise disagreement, argue from evidence, change your mind gracefully and protect working relationships.

Behavioral: Cross-Functional Disagreement and a Manager Conflict You Got Wrong

Company: Meta

Role: Software Engineer

Category: Behavioral & Leadership

Difficulty: medium

Interview Round: Technical Screen

This is a behavioral round in a senior to staff-level software engineering loop. The interviewer asks about two conflicts with different power dynamics: one with a partner you cannot direct, and one with a manager who can overrule you. Expect follow-ups on what you said, what you did and what you would change. ### Clarifying Questions - Does "cross-functional partner" mean someone in another discipline, such as product, design or data science, or can it be an engineer on a partner team? - For the manager conflict, must you have been wrong on the whole position, or is being wrong on the decisive point enough? - Should the conflicts be recent, and is it acceptable if one of them ended in escalation? ### Part 1 — Disagreement with a cross-functional partner Describe a significant disagreement with a partner from another function or team. What was at stake, how did you work through it, and what happened afterward? ```hint Argue their side first Be ready to state the partner's position so fairly that they would sign off on your summary before you describe what you did. ``` #### What This Part Should Cover - The stakes and both positions, stated fairly - How the discussion moved from opinions to shared goals and evidence - The mechanism that produced a decision - The state of the working relationship afterward ### Part 2 — A conflict with your manager where you were wrong Tell me about a time you had a conflict with your manager and it turned out that you were the one who was wrong. ```hint Name the turning point Identify the specific fact or argument that changed your mind, and how quickly you acted once you saw it. ``` #### What This Part Should Cover - What you believed and why it was reasonable at the time - How you pushed back - What showed you were wrong, and how you acknowledged it - What you changed in how you work ### What a Strong Answer Covers - Disagreement raised early, directly and privately first - Reasoning anchored in shared goals and evidence, not authority or persistence - A genuine change of mind, owned plainly, without excessive self-criticism - A decision that stuck and a relationship that survived or improved - A durable lesson that shows up in later behavior ### Follow-up Questions - If the partner had refused to move and the deadline was fixed, what would you have done? - Looking back, what early signal could have told you that you were wrong? - How do you behave once a decision goes against you? - How would your partner or your manager describe the same episode?

Overview: A senior behavioral question on conflict: describe a significant disagreement with a partner from another function and a conflict with your manager in which you turned out to be wrong. It tests how you raise disagreement, argue from evidence, change your mind gracefully and protect working relationships.

Read the full Meta Software Engineer interview experience this question came from

Meta logo
Meta
Apr 1, 2026
mediumSoftware EngineerTechnical ScreenBehavioral & Leadership
0
0

This is a behavioral round in a senior to staff-level software engineering loop. The interviewer asks about two conflicts with different power dynamics: one with a partner you cannot direct, and one with a manager who can overrule you. Expect follow-ups on what you said, what you did and what you would change.

Clarifying Questions Guidance

  • Does "cross-functional partner" mean someone in another discipline, such as product, design or data science, or can it be an engineer on a partner team?
  • For the manager conflict, must you have been wrong on the whole position, or is being wrong on the decisive point enough?
  • Should the conflicts be recent, and is it acceptable if one of them ended in escalation?

Part 1 — Disagreement with a cross-functional partner

Describe a significant disagreement with a partner from another function or team. What was at stake, how did you work through it, and what happened afterward?

What This Part Should Cover Guidance

  • The stakes and both positions, stated fairly
  • How the discussion moved from opinions to shared goals and evidence
  • The mechanism that produced a decision
  • The state of the working relationship afterward

Part 2 — A conflict with your manager where you were wrong

Tell me about a time you had a conflict with your manager and it turned out that you were the one who was wrong.

What This Part Should Cover Guidance

  • What you believed and why it was reasonable at the time
  • How you pushed back
  • What showed you were wrong, and how you acknowledged it
  • What you changed in how you work

What a Strong Answer Covers Guidance

  • Disagreement raised early, directly and privately first
  • Reasoning anchored in shared goals and evidence, not authority or persistence
  • A genuine change of mind, owned plainly, without excessive self-criticism
  • A decision that stuck and a relationship that survived or improved
  • A durable lesson that shows up in later behavior

Follow-up Questions Guidance

  • If the partner had refused to move and the deadline was fixed, what would you have done?
  • Looking back, what early signal could have told you that you were wrong?
  • How do you behave once a decision goes against you?
  • How would your partner or your manager describe the same episode?