Tell me about a complicated relationship you had with a coworker
Asked at:
Meta
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.
“Tell me about a coworker you found difficult to work with. What made it challenging?”
“Describe a time when your working relationship with a teammate was strained. How did you handle it?”
“Have you ever had an ongoing disagreement or tension with a colleague? What happened?”
“What's an example of a professional relationship that took effort to make work?”
“Tell me about a time you and another person worked together poorly at first but eventually improved it.”
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
A strong junior answer shows initiative: you did something concrete to make the working relationship better.
Good examples
🟢I asked if we could do a short one-on-one so I could understand their expectations and agree on a better way to hand work over.
🟢I started sending a brief summary with my changes and questions before review, which reduced back-and-forth and made our interactions smoother.
Bad examples
🔴I mostly waited for my manager to pair us less often so we wouldn't keep running into the same issue.
🔴I just kept my messages very short and tried not to interact unless necessary.
Weak answers avoid the problem; strong answers try small, direct interventions that improve day-to-day collaboration.
You do not need to agree with the coworker, but you do need to show that you tried to understand where they were coming from.
Good examples
🟢After talking with them, I learned they had inherited several production issues before, so their caution in reviews made more sense to me.
🟢I found out they were often getting incomplete handoffs from multiple people, which explained why they asked so many detailed questions.
Bad examples
🔴They were just really strict about quality and didn't seem to understand that I was still learning.
🔴I think they just preferred doing things their way, so there wasn't much to understand there.
Weak answers flatten the other person into a trait; strong answers uncover context that makes their behavior understandable.
Valuable
Do not end the story at the conversation itself; show that day-to-day working conditions actually got better.
Good examples
🟢After that, reviews became much faster and I felt comfortable asking them questions earlier, which made the rest of the project smoother.
🟢We ended up pairing on another task later, and that went much better because we had a clearer way of communicating.
Bad examples
🔴After we talked, things were fine and we just moved on.
🔴We never became close, but the project ended so it wasn't really an issue anymore.
Weak answers give a vague happy ending or let time solve the problem; strong answers show concrete evidence of improved trust or collaboration.
A good junior story can be small in scope, but it should still be meaningful enough to show real interpersonal skill.
Good examples
🟢The relationship mattered because we had to coordinate closely on a shared feature, and the tension was causing rework and hesitation in asking for help.
🟢It was a meaningful example because I depended on this person for reviews and handoffs, so improving the relationship directly affected my ability to deliver.
Bad examples
🔴We had a complicated relationship because they preferred tabs and I preferred spaces, and we finally settled on the formatter settings.
🔴A coworker once sent blunt messages in chat, so I just ignored the tone and finished my tickets.
Weak answers pick a trivial annoyance; strong answers choose a real collaboration challenge with visible impact.
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
Meta
Mid-level
Late January, 2025
Meta
Mid-level
Hello Interview Premium
Your account is free and you can post anonymously if you choose.