✍️ English & Grammar · Chapter 9

Speaking under pressure: structure first

You are not judged on your English in an interview. You are judged on whether your answer had a shape.

Study this lesson free in the app →

The basics

Speaking under pressure means giving a spoken answer — in an interview, a standup, an incident call — that the listener can follow on first hearing, even when you had no time to prepare.

The problem it solves: most people think interviews judge their English. They don't. Interviewers work with second-language speakers every day. What sinks an answer is having no shape: four fluent minutes after which nobody can say what the difficulty was, what you did, or how it ended.

The mental model: giving directions. "Ten minutes, three turns" first, then the turns. A frame in your first sentence tells the listener where every later detail attaches.

The universal shape: headline → "three things" → the parts → close.

When you freeze: pause, say "let me think", and never bluff a detail — it collapses on the follow-up.

Explained

Two candidates answer "tell me about a difficult project".

One speaks fluently for four minutes and the interviewer cannot tell what the difficulty was, what they personally did, or how it ended.

The other pauses, says "the hard part was that our revenue numbers were wrong and nobody knew why — let me give you the situation and what I did", and speaks for ninety seconds.

The second one is remembered. Not because their English was better — because the first sentence told the listener what to do with the next ninety seconds.

Two ways to give directions

Someone asks you the way to the station.

Version one: "So you go down here, well actually there's a shortcut but it's closed on Sundays, and there's a temple on the left, you'll see a chai stall, my cousin works there…"

Version two: "Ten minutes, three turns. Left at the temple, right at the chai stall, then straight." — and then, if they want, the detail.

Version one contains more information and is useless. Version two gave a frame — ten minutes, three turns — so every detail that follows has somewhere to attach.

Speaking under pressure is the same problem. The listener isn't struggling with your accent or your grammar. They're struggling to work out where the answer is going, and a frame in the first sentence solves it entirely.

The universal three-part answer

This works for behavioural questions, design questions, status meetings and "what do you think?" put to you with no warning. Announcing the number of parts is the trick most people never learn — it buys you thinking time and makes you sound organised.

Three frames worth memorising

PREP — for opinions and "what do you think?"

Point — "I'd partition by ride_id."

Reason — "because all events for one ride must stay ordered."

Example — "On our pipeline, keying by city gave us one hot partition for Bangalore."

Point — "So ride_id, unless ordering isn't required."

Thirty seconds, complete, and you can build it while saying the first word.

STAR — for "tell me about a time…"

Situation — one sentence of context. One.

Task — what you specifically had to do

Action — what you did. This is 60% of the answer

Result — with a number, and what you'd change

Most people spend three minutes on Situation and thirty seconds on Action. Invert it — the interviewer is buying your Action.

Design questions — clarify, frame, then depth

"Before I design it — how many events per second, and does it need to be real-time or is hourly fine?"

"I'll go ingestion, storage, serving, then the failure modes."

Asking a clarifying question is not stalling. It is the first thing a senior engineer does, and interviewers are explicitly listening for it.

Step through a STAR answer

Sixty seconds. Situation 15%, Action 60%, Result and reflection 25%. That ratio is the whole discipline.

Diagnose the answer

Q: "Tell me about a time you handled a production incident."

>

A: "So we had this system, it was a data platform, quite large, about 40 pipelines. It had been built over a few years by different teams. Anyway one day there was an issue, and we all got on a call — there were maybe eight of us — and we were looking at the dashboards, and the platform team thought it was Kafka, and then someone checked the logs and eventually we found the problem and fixed it. It was a good learning experience for the team."

The freeze, and what to do in it

You're asked something you don't know. Your mind goes blank. This happens to everyone, and what you do in the next four seconds decides how it lands.

What not to do: fill the silence. Talking while you think produces a rambling answer that buries the good part, and the interviewer remembers the rambling.

What works — say the frame out loud:

"Let me think about that for a second." — Then actually pause. Two seconds of silence feels enormous to you and normal to them.

>

"I haven't worked with Flink directly, but I've used Spark Structured Streaming — can I answer with that and you tell me if the comparison is useful?" — Honest, and redirects to your strength.

>

"I don't know that. My guess would be X, because Y — but I'd verify before relying on it." — Almost always better received than a confident wrong answer. It shows you know the boundary of what you know.

Never bluff a technical detail. Interviewers ask follow-ups, and a bluff collapses two questions later — costing you the credibility of everything you said before it, including the true parts.

And the reframe that helps most: an interview is not a test of recall. It's a preview of what working with you is like. "I don't know, here's how I'd find out" is a genuinely good preview.

Headline first, then say how many parts are coming.

STAR ratio: Situation 15%, Action 60%, Result 25%. Most people invert it.

"I", not "we". An answer with no "I" in it has told them nothing about you.

Words to know

In two minutes

• Interviewers judge whether your answer has a shape, not your accent or grammar.
• Lead with the headline, then announce how many parts are coming, then deliver them and close.
• PREP for opinions in 30 seconds; STAR for 'tell me about a time'; clarify-frame-depth for design.
• STAR ratio: situation ~15%, action ~60%, result with a number plus a reflection ~25%.
• Say 'I', not 'we' — an answer with no 'I' tells the interviewer nothing about you.
• When you freeze, pause openly, redirect to what you know, or say 'I don't know — my guess is X because Y'; never bluff.
• Prepare six stories with numbers, say them aloud, time them at 60–90 seconds, and include the person who disagreed with you.

Test yourself

There are 11 questions, 3 puzzles and 7 recall cards for this lesson in the app — the recall cards come back on later days, just before you would forget.