Behavioral: Resolving a Team Conflict and Working Through a Constraint

Quick Overview

Two common behavioral questions from a software engineering interview: describe a conflict with someone you worked with and how you resolved it, and a time you faced a constraint such as limited time or resources and worked around it. It tests ownership, communication and structured storytelling.

Behavioral: Resolving a Team Conflict and Working Through a Constraint

Company: J.P. Morgan

Role: Software Engineer

Category: Behavioral & Leadership

Difficulty: medium

Interview Round: Technical Screen

Answer two common behavioral questions. They were asked in a short behavioral session of about 25 to 30 minutes, so each answer should be concise. ### Clarifying Questions - Are examples from internships, school projects or volunteer work acceptable, or only from full-time work? - Should the conflict be with a peer, or can it be with a manager, a customer or another team? ### Part 1 — Resolving a conflict Tell me about a time you had a conflict or disagreement with someone you worked with. How did you resolve it? ```hint Your part in it Include what you contributed to the disagreement and what you personally did to move it forward, not only what the other person did. ``` #### What This Part Should Cover - A real disagreement with something at stake, described fairly - Concrete actions to understand the other side and reach a decision - An observable outcome and the working relationship afterwards - Reflection on what the candidate would do differently ### Part 2 — Working through a constraint Tell me about a time you ran into a limitation or constraint, such as too little time, missing resources, missing access, or knowledge you did not yet have. How did you deal with it? ```hint Fixed or negotiable Before describing your workaround, say exactly what was limited and which parts of the goal were truly fixed. ``` #### What This Part Should Cover - A precisely stated constraint and its stakes - The alternatives considered and the reasoning behind the chosen approach - Communication about the trade-off, and the concrete result - What was learned for next time ### What a Strong Answer Covers - STAR-shaped stories with most of the time on the candidate's own actions - True, specific examples that hold up under follow-up questions - Observable results and honest reflection - Respect for teammates, even when describing a disagreement - Concise delivery suited to a short session ### Follow-up Questions - What would you have done if the conflict had still been unresolved at the deadline? - Looking back, could the constraint have been prevented or seen earlier? - Tell me about working with someone whose working style was very different from yours. - When you could not deliver everything, how did you decide which trade-off to make?

Overview: Two common behavioral questions from a software engineering interview: describe a conflict with someone you worked with and how you resolved it, and a time you faced a constraint such as limited time or resources and worked around it. It tests ownership, communication and structured storytelling.

|Home/Behavioral & Leadership/J.P. Morgan
J.P. Morgan logo
J.P. Morgan
Jul 16, 2026
mediumSoftware EngineerTechnical ScreenBehavioral & Leadership
0
0

Answer two common behavioral questions. They were asked in a short behavioral session of about 25 to 30 minutes, so each answer should be concise.

Clarifying Questions Guidance

  • Are examples from internships, school projects or volunteer work acceptable, or only from full-time work?
  • Should the conflict be with a peer, or can it be with a manager, a customer or another team?

Part 1 — Resolving a conflict

Tell me about a time you had a conflict or disagreement with someone you worked with. How did you resolve it?

What This Part Should Cover Guidance

  • A real disagreement with something at stake, described fairly
  • Concrete actions to understand the other side and reach a decision
  • An observable outcome and the working relationship afterwards
  • Reflection on what the candidate would do differently

Part 2 — Working through a constraint

Tell me about a time you ran into a limitation or constraint, such as too little time, missing resources, missing access, or knowledge you did not yet have. How did you deal with it?

What This Part Should Cover Guidance

  • A precisely stated constraint and its stakes
  • The alternatives considered and the reasoning behind the chosen approach
  • Communication about the trade-off, and the concrete result
  • What was learned for next time

What a Strong Answer Covers Guidance

  • STAR-shaped stories with most of the time on the candidate's own actions
  • True, specific examples that hold up under follow-up questions
  • Observable results and honest reflection
  • Respect for teammates, even when describing a disagreement
  • Concise delivery suited to a short session

Follow-up Questions Guidance

  • What would you have done if the conflict had still been unresolved at the deadline?
  • Looking back, could the constraint have been prevented or seen earlier?
  • Tell me about working with someone whose working style was very different from yours.
  • When you could not deliver everything, how did you decide which trade-off to make?
Loading comments...