Tell me about a time you had a conflict with a team member. How did you handle it?

This is a behavioural question. The interviewer believes that how you behaved in the past predicts how you will behave in their team. They are checking whether you can disagree without fighting, listen to others, and still get the work done.

"I've never had a conflict" is the worst answer. It sounds either untrue or like you avoid all difficult conversations. Every team project has disagreements. Pick one.

The best tool for this question is STAR:

• S - Situation: where and when, in one or two lines.
• T - Task: what you were responsible for, or what needed to happen.
• A - Action: what you did, step by step. This is the main part.
• R - Result: the outcome, ideally with a number, and what you learned.

A sample answer from a final-year ECE student in Coimbatore:

Situation: "In my final-year project, four of us were building a smart irrigation system using soil sensors and an Android app. About six weeks before the review, my teammate Karthik and I disagreed on the app. He wanted to add a weather forecast feature; I felt we didn't have time and should first make the sensor readings reliable."

Task: "I was handling the hardware integration, and we needed one working demo for the external review."

Action: "Instead of arguing in the group chat, I asked Karthik to sit with me for twenty minutes after class. I asked him why the forecast mattered to him, and he explained that it would let the system skip watering before rain, which was actually a strong point for the review. I showed him our test log, where the sensor dropped readings almost a third of the time. We agreed on a plan: I'd fix the sensor issue in the first two weeks, and he would build the forecast feature in parallel, using a free weather API, as a separate screen we could turn off if it wasn't ready. We shared the plan with our guide so everyone was clear."

Result: "Both parts were ready a week before the review. The examiners specifically liked the rain-skip logic, and we got an A grade. I learned that most disagreements get easier once you understand the other person's reason, and that writing down a plan stops the same argument from coming back."

• Spend about 10% on Situation and Task, 70% on Action, and 20% on Result.
• Say "I", not "we", in the Action part. The interviewer wants your behaviour.
• Describe the other person fairly. If they sound like a villain, you sound like someone who creates villains.
• Choose a conflict about work: priorities, approach, deadlines, division of tasks. Not personal fights.

STAR works for most behavioural questions: a time you failed, a time you led a team, a time you missed a deadline, a time you handled pressure. Prepare four or five stories from projects, internships, college fests or sports, and you can adapt them to almost any behavioural question in HR or managerial rounds.

• Saying you have never had a conflict.
• Blaming or mocking the teammate: "He was lazy and never did anything."
• Choosing a story where a professor or manager had to step in and decide everything for you.
• A story with no result, or one where nothing was resolved.
• Spending two minutes on background and ten seconds on what you did.
• Picking something too personal, like a fight with a roommate over rent.

• What would you do if the other person still refused to agree?
• Tell me about a time you disagreed with your manager or professor.
• Have you ever been wrong in a disagreement?
• How do you handle a teammate who is not doing their share of the work?