← Expedia Interview Insights

Expedia·Software Engineer·Onsite - Behavioral / Leadership·Intermediate

Intermediate
Jun 2026

Summary

Behavioral round at Expedia for a software engineer role. Just one question but it had a lot of layers to it.

Questions Asked (1)

Q1

Tell me about a time you didn't fully trust a colleague. What caused the doubt, how did you navigate it, and what came out of it?

Conflict ResolutionAdaptability & Ambiguity
Author's notes

This one made me pause longer than I expected.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Choose a low-stakes, resolved situation where initial doubt about a colleague's reliability or expertise was addressed through direct, respectful communication and verification. Focus on how you separated the person from the problem, used data or checkpoints to validate work, and preserved the relationship. Conclude with the positive outcome and what you learned about building trust.

Pro tip: Emphasize that you addressed the doubt by adjusting your own behavior first—like adding a review step or asking clarifying questions—rather than accusing the colleague. This shows emotional intelligence and a solutions-oriented mindset, which Expedia values in collaborative engineering teams.

1. Set the context briefly

Describe the project, your role, and the colleague's role in 1-2 sentences. Keep it neutral and avoid sounding like you're blaming anyone.

2. Explain the cause of doubt

State the specific, observable behavior or pattern that triggered your doubt (e.g., missed deadlines, inconsistent code quality, vague updates). Avoid personal attacks or assumptions about character.

3. Describe your navigation strategy

Explain the concrete steps you took: e.g., having a private conversation, increasing check-ins, adding code reviews, or verifying work through tests. Highlight how you kept communication open and respectful.

4. Share the outcome and resolution

Reveal what happened—whether the doubt was resolved, the colleague improved, or you adjusted expectations. Mention any process improvements or stronger working relationship that resulted.

5. Reflect on the lesson

Summarize what you learned about trust, communication, or assumptions, and how you apply that insight today.

Key Points to Mention

  • Specific, observable behavior that caused doubt (not personality judgments)
  • Direct, private conversation with the colleague to understand their perspective
  • Concrete actions you took to mitigate risk (e.g., pair programming, code reviews, checkpoints)
  • How you maintained professionalism and preserved the working relationship
  • The positive outcome or resolution, including any process improvements
  • A lesson learned about trust, communication, or giving people the benefit of the doubt

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.