Behavioral question
Tell me about a time you worked under pressure
Pressure is a clock plus a consequence. They want to see you narrow the work, tell the truth about what will not get done, and still land the part that mattered. Panic is not a skill.
Check this example, then replace it
The box starts with one STAR answer. Read the scores, then delete it and paste a story from your own work. Scoring stays in the browser.
84/100
Solid
About 56 seconds spoken · 139 words. Spoken time uses 150 words per minute.
Feedback
- This has a clear STAR shape. Only keep numbers you can defend out loud.
Which sentence is which
In December 2023 a partner launch was 36 hours out and our sandbox had been returning 500s all morning. I was responsible for a sandbox that could survive that demo, not for every bug in the queue. I triaged the 11 errors, fixed the 2 that the demo script hit, and wrote a status note that listed the other 9 as out of scope for the demo. I then ran the demo script 6 times with the partner engineer. I pinned the out-of-scope list in the partner channel so nobody quietly added an eleventh bug the morning of the demo. The result was a clean demo, those 2 errors gone, and the other 9 scheduled into the next sprint. The partner was going to demo it to their board. The partner signed the integration the following week.
Why this example holds up
The clock is 36 hours. You do not pretend you fixed everything. The signed integration is the result, and the explicit out-of-scope list is what makes the story adult.
How to answer “Tell me about a time you worked under pressure” with STAR
- Situation. Set the scene in one or two sentences: when it was and what was already wrong. For example: In December 2023 a partner launch was 36 hours out and our sandbox had been returning 500s all morning.
- Task. Say what you personally owned. For example: I was responsible for a sandbox that could survive that demo, not for every bug in the queue.
- Action. Say what you did, in order, with I. For example: I triaged the 11 errors, fixed the 2 that the demo script hit, and wrote a status note that listed the other 9 as out of scope for the demo.
- Result. End on the change, with a number you can defend. For example: The result was a clean demo, those 2 errors gone, and the other 9 scheduled into the next sprint.
Mistakes on this question
- A vague “it was a crazy week” with no clock.
- Heroics that hide the list of what you dropped. They will ask, and you should already have the answer.
- Pressure caused by your own missed planning, with no comment on that. You can use it, but own it.
How to practice it
Put the clock in the first sentence. If you cannot name the hour or the day, the pressure is atmosphere, not a story.
FAQ
Is an incident a good pressure story?
Yes, if you had a role in it. “I watched the incident channel” is not a role.
How much emotion should I show?
One clause is plenty. They are grading the cuts you made, not your adrenaline.