'How do you handle pressure?': example answers with real mechanisms

My honest answer is that I handle it with a sequence, because calm is a byproduct of knowing what you do first. The clearest test: results day, 8:40am, and our student records system went down — 300-plus calls building, clearing staff locked out, and admissions decisions due out by ten.

First move, and it isn't glamorous: I wrote the incident down in one sentence and timestamped it, because the version you communicate is the version you can manage. Second: split the problem — the fix belonged to infrastructure, so the desk's actual job was communication and workaround. I put a status line on the phone queue and the student portal inside ten minutes and refreshed it every twenty, whether or not anything had changed — 'no change' on schedule beats silence every time. Third, the subtraction: I pulled us off every routine ticket and told two departments their planned jobs wouldn't happen that morning, by phone, before they found out passively.

System came back at 9:50. What we got afterwards surprised me: two of the angriest departments wrote to thank us — not for the fix, which wasn't ours, but for never leaving them guessing. That taught me the lesson I've reused since: in an incident, the desk's product is certainty per twenty minutes.

I'd answer with a season rather than a day, because sustained pressure is a different skill. January in practice: my portfolio's share was around 180 returns, deadline immovable, and the pressure builds for five straight weeks.

What I actually do differs from how I worked my first January, which I survived on late nights and got a filing-review error for my trouble. Now the season is designed in advance. In November I chase the 30 clients who were late with records last year — specifically them — which pulls a chunk of the mountain forward. Through January I work to a daily returns number rather than a daily hours number, because hours lie and the count doesn't. Fridays are protected for review only: nothing new gets prepared, mistakes from the week get caught while they're cheap. And I book the queries call with my manager for Tuesday mornings, when the list is short, instead of ambushing her in week four when it's long.

The mechanism that matters most is boring: I stop at the planned time on all but the genuine exception days, because my error rate is the thing I'm actually managing — a return I prepare tired costs more in review than it saved in schedule.

Last two seasons: every return filed on time, and no review errors escalated. The season didn't get smaller. It got designed.

Mine is pressure with an audience, which has its own rules. Peak season we turn around three weddings in a weekend, and the couple can never see the machinery — my job is to be the calmest person either family meets, on the exact days I'm busiest.

The mechanism has two halves. Backstage: everything runs off a printed hour-by-hour sheet — mine, not memory — with the three failure points for that specific wedding marked before the day starts. I check those three deliberately instead of everything anxiously; the sheet does the worrying so I don't have to. Front-stage: one rule I hold absolutely, which is that no problem reaches the couple with a question mark on it. The Saturday our florist rang in sick at 7am, the bride heard about it at 8:15 — after I'd confirmed the replacement — as 'there was a supplier change this morning, it's handled, and here's the one difference you'll notice.' Same fact, but arriving as an answer rather than a problem.

The honest limit: a full peak season used to erode me by September, and one year the erosion showed in a snapped reply to a colleague mid-event — she deserved better, and I apologised the same day. Since then I book my own recovery weekend in mid-August the way I book suppliers: in advance, non-negotiable. It reads as indulgent until you've watched what a tired coordinator costs a wedding.

I'll give you the real one. As a second-year trainee I had three property completions land in the same week, the supervising partner was on leave, and I made the classic junior mistake: I decided the professional thing was to absorb it silently. By Wednesday I was reordering my list every twenty minutes instead of working it, and I missed sending a redemption statement request that Thursday's completion needed — caught by our conveyancing assistant on Wednesday evening, which is the only reason it didn't delay a family's move.

What failed wasn't effort — I was working flat out. It was that I'd treated asking for help as failure, so the pressure had no outlet except my own margins, and the margins ran out.

What I rebuilt afterwards is specific. First: a hard rule that when my list stops shrinking for a day, that fact gets escalated — the deputy supervising partner hears it as information, not apology. Second: completions now run off a checklist I built from that week, with the third-party dependencies — the things I can't chase last-minute — flagged at the top. I've had heavier weeks since; the difference is that people around me now know in advance, and the checklist means the dependency items move first.

I'd rather be the candidate who can tell you exactly how their pressure plan failed once than the one who claims it never has.