Interview"Tell me about a challenge or difficult situation you faced." How to answer
A question asked in almost every interview. Why it is asked, how to build your answer, model answers, and what to avoid.
Why interviewers ask it
This is a behavioural question. The idea behind it is that how you acted in a real situation is the best guide to how you will act again. The interviewer wants a specific story, not a general statement about how you handle pressure.
How to build your answer
- Use STAR: Situation, Task, Action, Result. See the STAR method.
- Situation and Task in two sentences: where, when, what had to be done.
- Action is the main part: what you did, step by step. Say "I", not "we".
- Result with a number or a clear outcome, and one line on what you learned.
- Prepare four or five such stories before any interview: a deadline, a conflict, a mistake, an initiative, a difficult customer. Most behavioural questions can be answered from them.
Model answers
In my final year, our project demonstration was moved forward by a week, and one of our four members fell ill. I was responsible for the database. I listed what was essential for the demo and what could wait, took over my teammate's login screen as well, and worked with the others every evening that week. We showed a working system on the day and received an A grade. I learned to separate "must have" from "nice to have" early in any project.
A colleague in dispatch and I disagreed over delayed stock reports; each of us thought the other was at fault. Instead of arguing on the group chat, I asked him to sit with me for half an hour. We found that his entries reached me after my cut-off time. We agreed that he would send them by four o'clock and I would publish the report at five. The delays stopped, and we have worked well together since. I learned to talk directly and early.
In my first month I posted a payment to the wrong vendor because two names were similar. The vendor called about the unpaid bill a week later. I told my senior at once, reversed the entry, and called the vendor to apologise and confirm the date of payment. Since then I check the vendor code, not only the name, before posting, and I suggested adding the city to similar names in the master. It has not happened again.
A customer came in angry because his phone, given for repair, was a week late. I let him finish, apologised for the delay, and called the service centre in front of him. They confirmed it would be ready in two days, and I offered him a spare handset from the shop until then. He collected his phone two days later and thanked me. I learned that people calm down when they see you acting on their problem.
These are examples about invented people. Keep the structure, and put in your own facts and numbers.
What to avoid
- A general answer: "I handle pressure well."
- A story in which you were only a spectator.
- Blaming the other person in a conflict story.
- A "mistake" that is really a boast.
- No result at the end.
- A story that takes five minutes. Aim for about two.
Likely follow-up questions
- What would you do differently now? Have one honest improvement ready.
- What did you learn from it? One line, stated as a habit you now follow.
Other common questions
Questions by job
Model answers are examples. They show the shape of a good answer, reviewed in November 2026. Use your own facts: an answer copied word for word will not survive a follow-up question. Employers differ, and nothing here promises selection. Names in the examples are invented.