Tell Me About a Compromise: Outcome, Follow-Through and What You Would Change

Read the full interview experience this question came from →

Quick Overview

A behavioral conflict question asking for a time you had to compromise, followed by probes on whether you were satisfied with the result, what you did afterwards to achieve what you gave up, and how you will act differently. It tests conflict handling, judgment, follow-through and honest self-reflection.

Tell Me About a Compromise: Outcome, Follow-Through and What You Would Change

Company: Google

Role: Software Engineer

Category: Behavioral & Leadership

Difficulty: medium

Interview Round: Technical Screen

This behavioral question is about conflict. Tell me about a time you had to compromise. After your story, expect these probes: - How will you act differently because of that experience? - Are you satisfied with the result? - After the compromise, did you do anything to make what you had given up happen later? ```hint Pick a real trade Choose a story in which you gave up something you genuinely wanted, for a reason you can defend, so that the question about satisfaction has an honest answer. ``` ```hint Prepare the sequel The last probe asks what happened after the compromise. Pick a story with a follow-through you can describe, whether or not it worked. ``` ### Clarifying Questions - Does a compromise in which both sides gave something up count, or is the interviewer looking for one where you conceded your preferred approach? - Should the other party be a peer, a manager, another team or a customer, or does any of them work? ### What a Strong Answer Covers - A concrete disagreement with real stakes, the options on the table, and the legitimate reasons behind each side's position. - The reasoning behind the compromise: what was traded away, what was protected, and how the agreement was made explicit. - An honest assessment of the result, including what did not go well. - Evidence of follow-through on what was given up, or a deliberate, explained decision not to pursue it. - A specific change in behavior, ideally shown in a later situation. - Scope that fits a senior engineer: disagreements about technical direction, priorities or cross-team commitments rather than minor code-style arguments. ### Follow-up Questions - If you had had the authority to decide alone, would you still have compromised? - How did the other party see the outcome, and how do you know? - Tell me about a time you refused to compromise. What made that case different?

Overview: A behavioral conflict question asking for a time you had to compromise, followed by probes on whether you were satisfied with the result, what you did afterwards to achieve what you gave up, and how you will act differently. It tests conflict handling, judgment, follow-through and honest self-reflection.

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

|Home/Behavioral & Leadership/Google
Google logo
Google
Sep 8, 2026
mediumSoftware EngineerTechnical ScreenBehavioral & Leadership
0
0

This behavioral question is about conflict. Tell me about a time you had to compromise.

After your story, expect these probes:

  • How will you act differently because of that experience?
  • Are you satisfied with the result?
  • After the compromise, did you do anything to make what you had given up happen later?

Clarifying Questions Guidance

  • Does a compromise in which both sides gave something up count, or is the interviewer looking for one where you conceded your preferred approach?
  • Should the other party be a peer, a manager, another team or a customer, or does any of them work?

What a Strong Answer Covers Guidance

  • A concrete disagreement with real stakes, the options on the table, and the legitimate reasons behind each side's position.
  • The reasoning behind the compromise: what was traded away, what was protected, and how the agreement was made explicit.
  • An honest assessment of the result, including what did not go well.
  • Evidence of follow-through on what was given up, or a deliberate, explained decision not to pursue it.
  • A specific change in behavior, ideally shown in a later situation.
  • Scope that fits a senior engineer: disagreements about technical direction, priorities or cross-team commitments rather than minor code-style arguments.

Follow-up Questions Guidance

  • If you had had the authority to decide alone, would you still have compromised?
  • How did the other party see the outcome, and how do you know?
  • Tell me about a time you refused to compromise. What made that case different?
Loading comments...