Tell me about a time you had a disagreement with a teammate and how you resolved it.
Fast recall
Quick revision
Core answer
Whether you can handle professional conflict constructively while maintaining team cohesion and respect under disagreement.
Framing the story as 'I was right and convinced them' without acknowledging their valid points, which shows lack of emotional intelligence and collaborative mindset.
Show that you documented the decision and reasoning afterward in the team wiki or project notes so everyone had clarity moving forward, demonstrating follow-through beyond just resolving the immediate tension.
Interview-ready guide
Interview answer
So in my final semester project, my teammate and I disagreed on whether to use REST or GraphQL for our API.
I wanted REST because we'd both used it before and our queries were pretty simple. He wanted GraphQL because he'd been learning it and thought it'd be more flexible for the frontend. We were kind of stuck.
What I did was set up a quick call where I really listened to his points without interrupting. He was worried about over-fetching data and wanted the frontend to control exactly what fields they needed. That made sense, especially since we were planning some mobile screens later.
I explained that REST was faster to implement given our two-week deadline and we could always migrate later if needed. We decided to do a quick spike: he spent two hours building a small GraphQL prototype while I did the same with REST. When we compared them, REST was working and testable, while GraphQL still had some resolver setup issues he was debugging.
We agreed REST was the right call for our timeline, but we documented in our README why we chose it and what would need to happen if we ever switched to GraphQL. The project shipped on time, and honestly I learned a lot about GraphQL benefits from his research even though we didn't use it. The key thing is we both committed to REST after the decision, no second-guessing during implementation.
Tell me about a time you had a disagreement with a teammate and how you resolved it.
Direct Answer
Use the STAR format: describe the Situation clearly, explain your Task or position in the disagreement, detail the Action you took to resolve it through respectful communication and compromise, and share the Result showing how the team moved forward. Focus on listening, understanding their reasoning, and committing to the final decision even if it wasn't your first choice.
Code Example
// SITUATION: During a college project building an e-commerce backend,
// my teammate wanted to store all order data in a single orders table
// with JSON columns for flexibility. I believed we should normalize
// the schema with separate tables for order_items and customer_addresses.
// TASK: As the person assigned to design the database schema,
// I needed to make a decision that both of us could support.
// ACTION: I scheduled a 30-minute call to understand his reasoning.
// He was concerned about query simplicity and avoiding complex joins.
// I acknowledged that was valid for simple cases, then showed him:
var orderReport = """
SELECT o.id, o.total, c.name
FROM orders o
JOIN customers c ON o.customer_id = c.id
WHERE o.status = 'COMPLETED'
AND o.created_at > '2024-01-01';
""";
// I explained that SQL joins are optimized and readable, while
// JSON querying in SQL is messy and hard to index. We agreed to
// normalize core entities but use a JSON field for optional metadata.
// RESULT: The schema performed well, queries stayed clean, and we
// both learned that hybrid approaches can satisfy multiple concerns.
// We documented the decision in our project README so future
// contributors understood the rationale.
Common Mistakes & Pitfalls
- Winning the Argument: Freshers often frame the story as 'I explained why I was right and they eventually agreed,' which signals arrogance and inability to truly collaborate. Interviewers want to see that you acknowledged the validity in their perspective.
- Avoiding Specifics: Saying 'we had a disagreement and talked it out' without details makes you sound like you're hiding something or didn't actually handle it well. Be specific about the topic, your reasoning, and theirs.
- No Clear Resolution: Ending with 'we agreed to disagree' shows you avoided making a decision, which doesn't work in engineering teams. Show that you reached a concrete outcome, committed to it, and the project moved forward successfully.
Looking for a structured roadmap?
Every module on this page is also part of the full Java backend interview track.