Why the result is the part that goes missing
Most candidates can describe a situation for four minutes and never say what changed. An interviewer hearing eight of these in a day writes down the one that ended with a figure: collections cut from 62 days to 41, support tickets down 30 per cent, a release cycle shortened from three weeks to five days.
The number usually goes missing because nobody measured at the time, not out of modesty. Reconstruct it from what you can still check: what the weekly report said before and after, how many people were doing the task, how many hours a week it took, what the vendor quoted before you renegotiated.
If no number exists, use a countable fact instead — three other teams adopted it, it is still running two years later, the client renewed at ₹8 lakh. Scale is not the point; specificity is. Only the vague version fails, and “everyone was much happier” is the vague version.
What STAR is actually for
STAR is a way of rationing two minutes, not a script to recite. Roughly 20 seconds of context, 15 on what you owned, 60 on what you did, 25 on the outcome. Unprepared answers spend 90 seconds on the situation, then compress the interesting part into one sentence as they notice the time.
“Task” is the field people skip, and it is where individual credit lives. “We migrated the billing system” tells an interviewer nothing about you. “I owned the reconciliation script and the cutover plan for 40,000 accounts” tells them what you can be trusted with. Write it in the first person singular.
“Action” should be decisions, not duties. The interviewer is listening for judgement: what you considered and rejected, who you had to convince, what you did when the plan failed the night before go-live. A list of responsibilities reads like a job description, and every candidate has already copied one of those.
Building a set of stories, not one answer
Four or five stories cover most behavioural rounds: a conflict, a failure, a deadline, a time you influenced people who did not report to you, and something you shipped end to end. Build each one once, then reuse it — the same project answers two different questions if you change which part of the action you emphasise.
Then say them aloud with a timer. Text that reads well at 250 words often runs past three minutes spoken, and the first thing to cut is always the situation. The interviewer does not need your company's org chart, only enough context for the result to mean something.
Indian panels tend to probe the number rather than accept it. If you say revenue rose 18 per cent, expect “over what period, and what else changed in that period?” Keep the timeframe and the base figure in your head, and be straight about which part was yours and which was the team's.