Technical skill gets you shortlisted, but many hiring decisions in IT are influenced by behavioural rounds: questions about how you have handled real situations. Product companies, global capability centres and many services firms now include a dedicated behavioural or “culture fit” round. Preparing for it is straightforward if you use a structure.
The STAR method
- Situation: the context, briefly.
- Task: what you were responsible for.
- Action: what you did. This is the most important part, so spend most of your answer here.
- Result: the outcome, with a number if possible, and what you learned.
A worked example
Question: “Tell me about a time you dealt with a production incident.”
- Situation: “During a festive sale, our order service started timing out and checkout failures rose sharply.”
- Task: “I was the on-call engineer and responsible for restoring service.”
- Action: “I checked dashboards and saw the database connection pool was exhausted. I scaled the service’s read replicas, temporarily disabled a non-critical recommendations call that was holding connections, and kept the support team updated every 15 minutes. After recovery, I wrote the post-incident review and added connection-pool alerts.”
- Result: “Checkout recovered within about 25 minutes. The new alerts caught a similar problem early the next month before customers noticed.”
Common questions to prepare for
- Tell me about a time you disagreed with a teammate or manager.
- Describe a project that failed or a mistake you made.
- Tell me about a time you had to meet a tight deadline.
- Describe a time you learned a new technology quickly.
- Tell me about a time you improved a process.
- Describe a difficult stakeholder or client and how you handled them.
- Tell me about a time you took ownership beyond your role.
- Describe a time you helped a colleague grow.
Build a story bank
You do not need a separate story for every possible question. Prepare six to eight strong stories from your work, written in STAR format, that together cover conflict, failure, success, leadership, learning and customer focus. Most questions can be answered by adapting one of them.
Answering questions about failure
Interviewers ask about failures to see whether you take responsibility and learn. Choose a real mistake with moderate consequences, describe it honestly without blaming others, and spend most of the answer on what you changed afterwards. Avoid disguised boasts such as “I work too hard.”
Tips
- Say “I” for your own actions, even in team stories, so the interviewer can assess you.
- Keep each answer to about two minutes.
- Never invent stories; follow-up questions expose them quickly.
- Freshers can use stories from college projects, internships, hackathons or student clubs.
Leave a Reply