Tell me about your most difficult working relationship
Asked at:
Meta
Oracle
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to assess how you handle sustained interpersonal difficulty when the other person is not easy to work with. They are looking for maturity under friction: whether you can understand the real source of tension, take responsibility for your part, work toward a productive resolution, and preserve effectiveness rather than simply labeling someone as difficult.
“Describe a time you had to work with someone you found particularly challenging.”
“Tell me about a colleague or counterpart you struggled to collaborate with. What made it hard?”
“Have you ever had a working relationship that was consistently difficult over time? Walk me through it.”
“Who was the hardest person for you to work with professionally, and how did you handle it?”
“Tell me about a time you and another person just weren't working well together. What did you do?”
Key Insights
- Conflict in this question does not need to mean open fighting. You will often do better with a story about repeated friction caused by misaligned incentives, communication gaps, trust issues, or different working styles than with a dramatic argument.
- You should show honest ownership of your contribution to the problem. If your story makes the other person sound unreasonable and you sound flawless, experienced interviewers will worry that you lack self-awareness.
- You need to explain not just how the tension ended, but how you adapted your working model. Strong answers show a durable change in how you collaborated, not a one-time compromise.
What interviewers probe atlevel
Top Priority
You do not need to agree with the person, but you should show that you tried to understand why they were acting that way.
Good examples
🟢At first I thought the engineer was being overly critical, but after talking with them I realized they were covering a part of the system that had caused incidents before, so they were very risk sensitive.
🟢The teammate seemed dismissive in chat, but once we spoke directly I learned they were juggling support issues and were frustrated by unclear handoffs, not by me personally.
Bad examples
🔴They were just hard to work with and gave harsh feedback, so I tried not to involve them unless I absolutely had to.
🔴He kept pushing back on my changes for no reason, and eventually I realized that was just his personality.
Weak examples reduce the other person to a trait; strong examples treat the other person as rational within their context and investigate the source of the behavior.
Even at junior level, interviewers want to hear that you took a constructive step yourself instead of only waiting for someone else to fix it.
Good examples
🟢I asked for a one-on-one conversation so we could talk through how we preferred to review work and what was causing the repeated back-and-forth.
🟢I started sharing smaller updates earlier and asked directly what information they needed from me so we could reduce misunderstandings.
Bad examples
🔴I told my manager that collaborating with them was hard, and after that I mostly let my manager handle the communication.
🔴Since their style was difficult, I just minimized contact and focused on my own tasks.
Weak examples outsource the problem or avoid it; strong examples show the candidate personally initiated actions that could improve the working dynamic.
Valuable
You do not need a perfect story; you need to show that you learned something about how you work with others.
Good examples
🟢I learned that when I feel defensive, I tend to avoid early communication, which usually makes the relationship worse, so now I surface questions sooner.
🟢I learned not to interpret blunt feedback as personal right away and to ask what concern is underneath it before reacting.
Bad examples
🔴The main thing I learned is that some people are just hard to work with, so you have to adapt to their style.
🔴It reinforced that I should trust my instincts when someone seems difficult.
Weak examples externalize the lesson onto other people; strong examples identify a personal pattern and a changed behavior.
Choose a real working relationship that affected your ability to deliver or collaborate, not a minor personality annoyance.
Good examples
🟢I had trouble working with a senior engineer who reviewed my code very bluntly, and it slowed me down because I started avoiding early feedback and my tasks dragged out.
🟢The hardest relationship I had was with a teammate on a shared feature where we depended on each other, but we had very different assumptions about when work was ready to hand off, which caused repeated misses.
Bad examples
🔴The hardest relationship I had was with a teammate who was pretty quiet in standup, so I just avoided asking them questions and went through someone else instead.
🔴I worked with a designer who preferred a different ticket format than I did, and it was frustrating because I like things organized a certain way.
Weak examples center on irritation or preference mismatch; strong examples involve a relationship problem that had real impact on delivery, learning, or team effectiveness.
Example answers atlevel
Great answers
The most difficult working relationship I had was with a senior engineer I depended on for reviews during my first few months. Their feedback was very blunt and I started dreading sending changes to them, which slowed me down because I would wait too long before asking for input. I asked if we could talk one-on-one, and I learned they were supporting a service that had recently had production issues, so they were being extra cautious and assumed I wanted direct feedback. After that, I started sending smaller changes earlier and including a short note on what I was unsure about, and they adjusted by grouping feedback into major versus minor issues. We never became close friends, but the relationship became much easier to work in, my review cycles got faster, and I learned not to interpret a tough style as personal before understanding the context.
My most difficult working relationship was with a product manager at a small startup who would frequently reprioritize work to prepare flashy demos for investors. That left me constantly switching tasks and delivering incomplete features, which was stressful and demotivating. I asked to join the weekly planning meeting, created a one-page summary for each task with clear acceptance criteria, and offered to sit in on demo prep so I could understand their goals. Those short checkpoints helped us lock priorities earlier in the week and reduced surprise requests. As a result, I shipped more predictable work, fewer bugs reached users, and we built a professional respect for each other’s constraints. I learned to be proactive about alignment and to explain trade-offs in terms of user value rather than just timelines.
Poor answers
My most difficult working relationship was with a teammate who questioned a lot of my implementation choices. It felt like they always had comments, so I started making the changes myself and only looping them in when I was basically done. That worked pretty well because there was less back-and-forth and I could keep moving. In the end the feature shipped, so I think that was the right way to handle it.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Early March, 2026
Meta
Mid-level
Late February, 2026
Meta
Mid-level
Mid February, 2026
Meta
Staff
Hello Interview Premium
Your account is free and you can post anonymously if you choose.