Behavioural Interview Questions (and What Good Answers Sound Like)

Most good behavioural answers follow the STAR shape: Situation (the context), Task (what they were responsible for), Action (what they did) and Result (what happened). You do not need to teach candidates STAR; you just need to listen for whether all four parts are there.

The Action part matters most. Many candidates say 'we' throughout. Gently ask, 'what did you personally do?' The Result also matters: 'the customer was happy' is fine for a fresher, but for a sales or operations role, push for something concrete like 'he renewed the order the next month' or 'we cleared the backlog by Friday'.

If a candidate cannot think of an example, give them a moment, then offer a smaller version: 'it does not have to be at work — college, a family business or a part-time job is fine.' This keeps freshers in the conversation.

These suit telecallers, customer support executives, retail staff, receptionists and anyone facing customers. Strong answers show the candidate listened first, stayed respectful and fixed or escalated the problem with a clear follow-up.

• Tell me about a time a customer was angry with you for something that was not your fault.
• Describe a time you had to explain something complicated to someone who did not understand at first.
• Tell me about a call or conversation where you had to say no to a customer.
• Describe a time you switched to Hindi or a regional language to help a customer. What changed?
• Tell me about a complaint you resolved that you are proud of.

Useful for almost every role, from office boys to accountants. Listen for candidates who admit mistakes plainly and describe what they changed afterwards. Red flags include no mistakes at all, or stories where everything went wrong because of someone else.

• Tell me about a mistake you made at work. How did you find out and what did you do?
• Describe a time you had to finish something urgent with very little time.
• Tell me about a time you noticed a problem nobody had asked you to fix.
• Describe a period when you had to come in early or stay late. Why, and how did you manage?
• Tell me about a time you could not meet a deadline. What did you tell your manager?

For field sales, business development and telecalling roles, ask for numbers — but verify they belong to the candidate. Strong answers mention their own target, how they planned their day or territory, and what they did differently when they were behind. For more on these roles, see our page to hire field sales executives.

• Tell me about the month you were furthest behind target. What did you do in the last ten days?
• Describe how you got your first order from a new shop, dealer or client.
• Tell me about a deal you lost. What would you do differently?
• Describe a time you had to follow up many times before a customer decided.
• Tell me how you planned your beat or call list on a typical day.

For supervisors, team leads and anyone who will manage shifts. Good answers show the candidate dealt with people problems directly and fairly, without shouting or ignoring them. Listen for respect towards team members, including contract and daily-wage workers.

• Tell me about a time two people in your team were not getting along.
• Describe a time someone in your team was regularly late or absent. What did you do?
• Tell me about a time you had to get work done with fewer people than planned.
• Describe how you trained a new joiner who was struggling.
• Tell me about a decision of your manager that you disagreed with. How did you handle it?

Good for technical, accounts, IT and operations roles. Strong answers show a logical process: what they checked first, how they narrowed the problem and how they confirmed the fix. They also show curiosity — learning a new software, a GST change or a new tool without waiting to be sent on training.

• Tell me about a technical problem that took you a long time to solve.
• Describe a time you had to learn a new software or process quickly.
• Tell me about a report or number that turned out to be wrong. How did you catch it?
• Describe a time you improved a process so it took less time.
• Tell me about feedback that changed how you work.

The first answer is often polished. The real information comes from follow-ups. Use short, neutral probes and stay silent for a few seconds afterwards — candidates usually fill the pause with detail.

A rehearsed story tends to fall apart when you ask for specifics such as names of tools used, the exact words said, or what happened a week later. A real story gets richer. That is the single most useful signal in behavioural interviewing.

• What exactly did you say to them?
• What did you do first? And then?
• Who else was involved, and what was your part specifically?
• How did you know it had worked?
• Looking back, what would you change?

Take the question "Tell me about a time a customer was angry with you for something that was not your fault." A weak answer sounds like this: "Customers get angry often, I just stay calm and handle it." It has no situation, no action and no result. It may be true, but it gives you nothing to score.

A strong answer sounds more like this: "Last Diwali a customer called because his order had not arrived for a week. The courier had delayed it. I let him speak first, apologised for the delay even though it was the courier, checked the tracking while he was on the line, and promised to call back by 5 pm. I called the courier hub, got a new delivery date and called him back at 4.30. He was still unhappy but thanked me for calling back, and he did not cancel." That answer shows listening, ownership, follow-through and an honest result.

A middle answer has a real situation but stops at "I passed it to my senior". That is acceptable for a fresher, but for an experienced executive you would probe: what did you do before passing it on, and what happened afterwards?

Do not ask all 25. Choose two or three questions for each of the four to six competencies that matter most for the role, and ask them in the same order to every candidate. Score each answer on a simple 1–5 scale you have written down beforehand. Our structured interview guide shows how to build that scorecard.

Language matters too. If the job will be done in Hindi, Tamil or Marathi, ask the questions in that language. You will hear much better examples from candidates who are comfortable, and you will be testing the communication they will actually use on the job.

When you post a role on BetterJobs, the AI-written job description lists the core responsibilities, which gives you a ready starting point for choosing your competencies and questions.