Tell me about a complicated relationship you had with a coworker
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to understand how you behave when collaboration is hard, not just when it is easy. They are looking for emotional maturity, empathy, communication skill, and whether you can improve a strained working relationship without making the situation bigger than it needs to be. At higher levels, they also want to see whether you can resolve tension in a way that protects team effectiveness, not just your own preferences.
Key Insights
- Conflict does not need to be dramatic to count. A strong answer often centers on mismatched working styles, risk tolerance, communication patterns, or trust—not a big argument.
- You should name your own contribution to the difficulty. Honest ownership is one of the fastest signals of maturity; a story where the other person was simply hard to work with is usually weak.
- Do not stop at 'we worked it out.' Explain how you understood the root cause, what you changed in your approach, and whether the relationship or working model improved afterward.
What interviewers probe atlevel
Top Priority
At junior level, interviewers mainly want to see that you can acknowledge your role in friction instead of defaulting to blame.
Good examples
🟢I realized part of the tension was that I took review comments personally, which made me slower to ask clarifying questions and probably made me seem defensive.
🟢We were struggling to work together, and after a few interactions I recognized that I wasn't giving enough context when I handed work off, so some of the rework was on me too.
Bad examples
🔴My teammate was pretty hard to work with because they were very particular, so I mostly tried to stay out of their way until the project ended.
🔴We had a complicated relationship because they kept changing my code, and I felt like they just didn't trust junior engineers.
Weak answers frame the problem as something done to the candidate; strong answers show self-awareness without excusing the other person's behavior.
Valuable
Example answers atlevel
Great answers
In my first year, I worked closely with a more experienced engineer who reviewed most of my changes, and the relationship felt tense for a while. I felt like their comments were harsher than I expected, but after a couple of rounds I realized I was submitting work with too little context and then getting defensive in review. I asked if we could do a short one-on-one, and in that conversation I learned they had recently dealt with a few production issues caused by unclear changes, so they were being extra careful. After that, I started adding a short summary of what I changed, what I had tested, and where I wanted feedback. Reviews got much smoother, and I became more comfortable asking questions early instead of guessing. We later worked together on another task, and it felt much more collaborative.
On my second rotation I paired with a product designer who loved iterating visually but often pushed new mockups late in the sprint, which left me scrambling to rework code and miss small details. I care about shipping predictable, polished features, so I felt frustrated and started avoiding questions so I wouldn’t slow them down, which made things worse. I asked for a short meeting to explain the impact of late changes and proposed a lightweight process: quick alignment at the start of the week and a short “intent” note on any mockup updates describing what must not change versus what can be tweaked later. They appreciated the clarity, and we also agreed I’d point out the parts that would be costly to change so they could prioritize. After a few sprints the back-and-forth became faster and less stressful, and we ended up enjoying iterating together because we both understood constraints and goals.
Poor answers
I had a complicated relationship with a coworker who was very picky in code reviews. They would leave a lot of comments, and it slowed me down because I had to keep making changes. I mostly handled it by keeping my work small and waiting for them to approve things, which worked out fine. We never really saw eye to eye, but the project got done and there were no major issues.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Mid May, 2025
Late January, 2025
Hello Interview Premium
Your account is free and you can post anonymously if you choose.