Tell Me About a Time You Worked Under Pressure

The behavioral round is going fine, then it lands: "Tell me about a time you worked under pressure." Your instinct is to reach for the all-nighter, the week you barely slept and grinded everything out, because it feels like proof you're tough. That story usually hurts you. This guide gives you the one-line reframe (they're testing prioritization under constraint, not stamina), a selection rule for picking the right crunch, a STAR shape weighted on the decisions you made, a full worked student example, and the traps that sink an otherwise fine answer.

What the interviewer is actually testing

The question sounds like it's about endurance. It's really about what you do when time runs out and you can't finish everything. On their team, a launch will slip, a client will move a deadline up, two things will land in the same afternoon, and they want to know how you behave in that moment. Three signals decide the answer.

Triage. When you can't do it all, what do you do first, and what do you drop or simplify? A candidate who protects the one thing that matters and lets the optional stuff go is someone you can hand a messy week. A candidate who tries to do everything at full quality and drowns is a risk.

Early communication. Did you flag the problem while there was still time to react, or did you go quiet and hope? This is the beat generic answers skip, and it's the one that separates a mature answer from a panic answer. "I emailed the TA the moment I saw the collision" tells them you'll raise a slipping deadline on day two, not the night before it's due.

Composure. Not "I felt nothing." Clear-headed under stress: you assessed, you decided, you moved. Some nerves are fine and human. Frozen or frantic is not.

Here's the part most guides won't tell you: an all-nighter story can actively hurt you. "I stayed up all night and got it all done" signals that you let work pile up and then solved a planning problem with brute force. Interviewers hear the missing question, which is why you were in that hole at 3am in the first place. They want calm prioritization, not sacrifice.

The rule for picking your story

Not every crunch makes a good answer. Run your candidates through three checks and keep only the ones that pass all three.

1. Time or resources were genuinely short. There has to be a real constraint: a hard deadline, too little time, a person who dropped out, a resource you didn't have. No constraint, no story.

2. You made a visible decision. This is the filter that matters. You reprioritized, cut scope, asked for help early, or renegotiated the deadline. Something you actively chose, not just a week you survived by working more hours.

3. It ended okay because of that decision, not because you endured it. The good outcome should trace back to the call you made. "It worked out because I triaged to the graded piece" passes. "It worked out because I didn't sleep" does not.

Where students actually find one, no work history required:

• Colliding deadlines during exam or midterm week, when two big things are due inside the same 48 hours.
• A group project whose plan broke close to the due date, like a teammate going dark on Friday for a Monday deliverable.
• A part-time, retail, or event shift that went sideways, short-staffed or slammed with no warning.
• A club event with a last-minute problem, a speaker cancelling or a venue falling through the day before.

Any of these gives you a real constraint and room to show a decision. Pick the one where your call is clearest.

The answer shape: STAR weighted on the decisions

Use the STAR method as the skeleton, but do not spread your words evenly. The situation is not the answer. Set the clock ticking fast, then spend the bulk of your time on what you did.

Situation and task

One or two lines. Just enough to make the constraint real: what was due, when, and why there wasn't enough time. "Two final projects were due in the same 48 hours, and a teammate had gone quiet on one of them." Done. Resist the urge to narrate the whole semester.

Action

This is the heart of the answer, and it carries two beats.

First, triage. Say what you did first and what you deliberately dropped or simplified. Name your criteria out loud, because that's the thinking they want to see: "The graded core was worth most of the marks, so that came first, and I cut the optional extension section entirely." Cutting something on purpose reads as judgment. Trying to save everything reads as someone who can't prioritize.

Second, communication. Say who you told and when, and make it early. "I emailed the TA that morning to ask for a two-day extension." "I flagged the risk to my group lead the same day I spotted it and proposed reassigning one section." The "same day" and "that morning" are doing real work here. They prove you surface problems while they're still fixable.

Result

What happened, ideally with a small concrete outcome: you shipped the essential piece on time, the demo ran, the deadline got moved and the work landed. Then add one line about what you'd systematize so the crunch is smaller next time. "Now I map deadline collisions at the start of the term so I catch them weeks out, not days." That last line turns a survival story into evidence you learn.

A worked student example

Made-up material and an ordinary outcome, not a hero story. The point is the pattern, so copy the shape, not the words. Watch the weak version first, then the same situation done right.

Setup: two final projects due in the same 48 hours, and on one of them, a two-person deck due Monday, your teammate went silent on Friday.

Weak version: "I had two projects due at once and a teammate who disappeared, so I just put my head down and grinded. I stayed up basically all night both nights, did my half and most of his half, and somehow got everything in. It was rough but I proved I can handle pressure."

That answer sounds tough and lands as a warning. There's no decision in it, no communication, and the takeaway is "I can absorb punishment." Now the strong version:

"Two finals landed in the same 48 hours, and on the group deck due Monday, my partner went dark Friday afternoon. situation and task First I ranked them: the deck was worth more of my grade and had a hard Monday submit, so it went first, and I cut the optional analysis appendix on my solo project down to a short summary since it was ungraded. triage, with the criteria stated Then, Friday evening, I messaged our group lead and my partner: I flagged that I couldn't cover both halves at full quality and proposed reassigning my partner's section to a third teammate who had lighter finals. She took it Saturday morning. early communication We submitted the deck Monday with the core intact, my solo project went in on time with the trimmed appendix, and both landed fine. result What I changed after: I now lay all my deadlines on one calendar in week one, so a collision like that is something I see coming weeks out instead of discovering on a Friday. what I'd systematize"

Same weekend, opposite signal. The strong version makes a visible call, raises the problem while there's still time to fix it, and ends with a system, not a scar. Nobody stayed up all night, and it reads stronger for it.

Traps that sink an otherwise fine answer

• The martyr story. The all-nighter, the "I sacrificed my whole weekend." It signals poor planning and brute force, not judgment. If the hero move is suffering, pick a different story.
• No example at all. "I work really well under pressure" with nothing behind it answers nothing. Neither does "I never really feel pressure," which reads as someone who hasn't been tested or isn't being honest.
• Self-inflicted pressure with no lesson. A crunch that only existed because you procrastinated, told with no takeaway, tells them you'll create your own fires. If procrastination was the cause, the fix has to be the point of the story.
• A crunch that ended badly with no recovery. A story that just trails off into missing the deadline gives them nothing to grade. There has to be a decision that changed the outcome, or a clear takeaway if it didn't.
• So calm nothing's at stake. If you strip out all the tension, there's no pressure left to talk about. No real constraint means no story. Keep the stakes visible: name what was on the line and how little time you had.

Frequently asked questions

How do you answer "how do you handle pressure" if you have no work experience?

Use a school or club crunch and don't apologize for it. A colliding exam week, a group project whose plan broke, or a shift that went sideways all work, because the interviewer is grading your decision-making, not the setting. Interviewers screening interns expect no work history. Pick the crunch where your triage-and-communicate move is clearest.

How do you prioritize tasks when you have multiple deadlines?

Name your criteria out loud, because that's what the interviewer wants to hear. The usual order is hard deadline plus highest-impact or graded piece first, then cut or defer the optional. Say the cut explicitly ("I dropped the ungraded appendix to protect the graded core"). Deciding what not to do, on purpose, is the whole signal.

Is it okay to say you struggle under pressure or get stressed?

Yes, admitting some nerves is realistic and lands better than pretending you feel nothing. The move is to show the system you use to stay clear-headed: how you triage, who you loop in, how you keep moving. Just don't claim you never feel pressure, which reads as either untested or not level with them.

Should I use a work example or is a school example okay?

Either works for an intern role. Pick the one with the clearest decision, not the one with the most impressive setting. A group project where you cut scope and reassigned a section often beats a vague work story where you just "handled it," because the school example has a visible call in it.

What's a good example of working under pressure for students?

Colliding exam-week deadlines, a group project whose plan broke a few days before the due date, or a shift that went sideways. Each becomes a strong answer when you tell it as a triage-and-communicate story: what you did first, what you dropped, and who you flagged, when. The setting matters far less than the decision inside it.

Right now, pick one crunch from the last year that passes all three checks: real constraint, a decision you made, an outcome that traces back to that decision. Write the one line for "what I did first" and the one line for "who I told, and when." Then rehearse the beats out loud so triage and communication come through clean, and prep the rest of the questions intern interviews actually ask from the same hub.