Describe a project mistake or interpersonal conflict you experienced
Behavioral question exploring error handling and conflict resolution skills. Follow-up probes examine adaptability under different constraints such as hierarchy differences or working with inflexible stakeholders.
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to assess maturity under stress: whether you can talk honestly about something that went wrong and show sound judgment in how you handled it. They are usually listening less for the surface story and more for your ownership, empathy, learning loop, and whether your response fits the scope expected at your level. A strong answer shows that you can navigate imperfection without becoming defensive, blameful, or passive.
Key Insights
- You do not need a dramatic failure or a heated argument. A strong answer often comes from a meaningful miss, misunderstanding, or disagreement where the stakes were real enough to reveal your judgment.
- Honest ownership of your contribution is a fast signal of maturity. If your story makes everyone else seem unreasonable and you seem purely correct, many interviewers will assume you lack self-awareness.
- For conflict stories, explain the other person's constraints or incentives, not just their position. For mistake stories, explain how you changed your behavior afterward, not just how you fixed that one incident.
What interviewers probe atlevel
Top Priority
You are not expected to have perfect judgment yet, but you are expected to be honest about what you contributed.
Good examples
🟢I realized I had been nodding along in standups even when I was confused, so part of the delay was that I had not asked basic questions early.
🟢I went into the conversation assuming my approach was simpler, but I had not considered how it affected the test setup the other person owned.
Bad examples
🔴The issue happened because the requirements kept changing, so there was not much I could have done differently.
🔴The disagreement came from the other engineer being pretty stubborn, and I mainly just waited for my mentor to step in.
Weak answers externalize the problem; strong answers clearly name the candidate's own behavior without over-dramatizing it.
Valuable
Example answers atlevel
Great answers
On an internship project, I was adding a small reporting feature and I told my mentor I was almost done because the code worked locally. When they tried to test it, they pointed out that I had made assumptions about the input format that were not true in the real workflow, so their test setup failed and we lost part of a day. I owned that pretty quickly because I had been hesitant to ask basic questions and had treated local success as enough. I asked them to walk me through the actual workflow, updated the implementation, and wrote down the assumptions in a short note so we could verify them together. After that, I started summarizing my understanding before I began coding in unfamiliar areas, and on the next task we caught a mismatch much earlier.
During a part-time role helping a local nonprofit update their website, I got into a conflict with another volunteer who was also editing the donation page. I had changed the wording to make it shorter, but I didn’t realize she had already shared the original version with a board member, so my update created confusion and made her look unprepared. I felt bad because I had assumed that since the change was small, I didn’t need to check in first. I apologized, put the page back in a stable state, and suggested we use a simple shared note for any future edits so nobody stepped on each other’s work. After that, we were much smoother, and I learned that even small projects need clear communication when multiple people are involved.
Poor answers
One conflict I had was with another intern about how to format some code. I felt pretty strongly that my version was cleaner, so I explained the style guide and stuck with it. It was not a huge issue, but I think it showed I can defend good engineering choices. In general, if I know something is correct, I try not to overcomplicate the discussion.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Late June, 2026
Late November, 2025
Typical behavioural question. We dived deeper into what I would do differently if I faced the same issue again and under different constraints, like if the person I had a conflict with was a senior manager, or if they had dogmatic views.
Hello Interview Premium
Your account is free and you can post anonymously if you choose.