Autocoder

STAR Method: Behavioural Interview Questions and Answers

Last updated 2026-11-19

Behavioural questions begin with phrases like tell me about a time when, or give an example of. They are common in product companies, global capability centres and many services firms. The STAR method (Situation, Task, Action, Result) is the standard way to structure the reply so that it is specific, short and ends with an outcome.

This page explains each part of STAR with proportions, shows how to build a story bank from projects and college life, and then walks through thirteen questions with full sample answers. For the round overall, see how to crack the behavioural interview. Replace the sample details with your own.

FormatSituation, Task, Action, Result
Time per answer90 seconds to 2 minutes
Story bank6 to 8 real stories

The four parts and how much time to give them

Build a story bank

List six to eight experiences: a project, a deadline you almost missed, a disagreement, a mistake, a time you led, a time you learned something quickly, and a time you helped someone. One strong story can answer several questions with a different emphasis. A fresher can use college projects, hackathons, clubs, internships and even part-time work.

Common errors

Saying we for all actions hides your part. Spending half the answer on the situation leaves no time for results. Choosing a story without a real conflict or outcome makes the answer flat. And inventing a story is risky, because follow-up questions such as what did the other person say or what would you do differently expose it quickly.

STAR Method: questions with worked answers

  1. 1

    Tell me about a time you faced a tight deadline.

    easy

    Situation: In our final-year project, our demo was in four days and the login module was incomplete. Task: I was responsible for authentication. Action: I listed what was essential, dropped social login, built email login with tests, and asked a teammate to review it in the evening. Result: We demoed on time, and the faculty noted the stable login. I learned to cut scope early instead of rushing everything.

  2. 2

    Describe a time you worked in a team to achieve something.

    easy

    Situation: A four-member hackathon team had 24 hours to build a hospital queue app. Task: I took the backend. Action: I agreed on the API with the frontend teammate in the first hour, built the endpoints in six hours and wrote a short mock server so the UI work was not blocked. Result: We finished second among 40 teams. The early API agreement saved us.

  3. 3

    Tell me about a time you disagreed with a teammate.

    medium

    Situation: A teammate wanted MongoDB for our project, and I thought relational data suited it better. Task: We had to choose within a day. Action: I listed our queries, showed that most needed joins, and suggested a small test of both. We ran a quick trial. Result: Postgres handled it more simply, and he agreed. I learned to bring evidence, not opinions. See conflict and teamwork questions.

  4. 4

    Give an example of a time you took initiative.

    medium

    Situation: In my internship, bugs were reported by email and lost. Task: Nobody owned it. Action: I made a simple shared sheet with status and owner, and showed my mentor. He agreed to try. Result: In a month the team stopped missing reports, and my mentor asked me to present it in the team call. The story shows a small fix beyond the assigned job.

  5. 5

    Tell me about a time you failed.

    medium

    Situation: I missed an assignment deadline in my third year because I underestimated a data-cleaning task. Task: I was solely responsible for it. Action: I told the professor early, explained what happened, and submitted a day late with the work finished. After that I began breaking tasks into hours. Result: I lost marks but met every later deadline. See failure and mistakes questions.

  6. 6

    Describe a time you learned something quickly.

    easy

    Situation: My internship project used React, which I had never used. Task: I had to fix UI bugs in two weeks. Action: I did a short tutorial on weekends, read the existing components and asked my mentor for review after each fix. Result: I closed 14 tickets by the end of the month. I learn best by reading real code with feedback.

  7. 7

    Tell me about a time you handled pressure.

    medium

    Situation: During a production issue at my previous company, the payment API started timing out during a sale. Task: I was on call. Action: I checked the dashboard, found a slow query, added an index after confirming with a senior and informed support of the status every fifteen minutes. Result: The service recovered in forty minutes. I wrote a postmortem the next day.

  8. 8

    Tell me about a time you helped someone.

    easy

    Situation: A junior in my hostel was failing data structures. Task: I volunteered to help. Action: I met him twice a week for six weeks, started with arrays and gave small problems. Result: He passed his exam with a B grade and later joined the coding club. Helping him made me better at explaining.

  9. 9

    Describe a time you had to persuade someone.

    hard

    Situation: My team lead wanted to skip tests to meet a release. Task: I was concerned about regressions. Action: I showed him that two of the last five bugs would have been caught by the tests, and proposed writing only the tests for the payment path. Result: He agreed and we shipped a day later, with no payment issues. Use data and a smaller ask to persuade.

  10. 10

    Tell me about a time you received critical feedback.

    medium

    Situation: My mentor told me my pull requests were too large. Task: I had to improve. Action: I started splitting changes into small pieces with clear descriptions and asked for review earlier. Result: Review time fell from two days to a few hours. I now ask for feedback early.

  11. 11

    Give an example of going beyond what was asked.

    medium

    Situation: I was asked to fix a report that showed wrong totals. Task: Fix the bug. Action: After the fix, I found that the same error existed in two other reports and corrected them, adding a test. Result: Finance stopped reporting mismatches. Describe extra effort with a purpose, not long hours.

  12. 12

    Tell me about a time you managed multiple priorities.

    medium

    Situation: During exams, I also had a project submission and a club event. Task: Handle all three. Action: I listed deadlines, assigned fixed study blocks, delegated event tasks to two members, and told my project team I would deliver my part two days early. Result: I completed all three. See time management questions.

  13. 13

    Describe a situation in which you led a group.

    hard

    Situation: As coordinator of the college tech fest, I had 25 volunteers. Task: Deliver three events. Action: I divided the team by event, held a ten-minute daily check-in, and fixed a venue clash by moving one event to the next morning. Result: All events ran, with about 300 participants. Be specific about decisions. See leadership questions.

Frequently asked questions

What does STAR stand for?

Situation, Task, Action and Result. It is a way to organise a story so it covers context, your role, your steps and the outcome.

How long should a STAR answer be?

Between ninety seconds and two minutes. Spend most of the time on the action and result.

Can freshers use college stories?

Yes. Projects, clubs, hackathons and internships are all valid, as long as the story is real and you can answer follow-ups.

What if I do not have a good result?

Use the learning as the result and describe what you changed afterwards. Honest learning is acceptable.

Related guides

More in HR Interview Questions

See all in this section