The conceptual answer shape: say it, show how, then stop

Say the answer in one sentence, show how it works, then stop: depth shows in the follow-ups, not in length.

Before you read: predict

ExamHall design round, deep dive, minute 31. Your diagram puts Redis in front of Postgres for the exam paper. The interviewer points at the Redis box: “Why won't a bigger Redis fix the exam-start stampede?” You know Redis well.

How do you shape your answer?

The 30-second version

Answer a concept question in five parts: a one-sentence answer, how it works step by step, one concrete example, where it breaks or what it costs, and your own experience if you have some. Take 60–120 seconds, then stop and offer two places to go deeper.

Say the answer in one sentence, show how it works, then stop: depth shows in the follow-ups, not in length.

How it works

Step 1 of 10

Answer first. One sentence that answers the question asked. If you are cut off after it, the interviewer still has your answer. [R07]

Analogy: The train manager's announcement

A train stops between stations and the train manager takes the microphone. First, the one sentence everyone needs: "We're held here for about fifteen minutes." Then why: a train ahead has failed on the only platform, so the signal holds us. One concrete case: "If you're connecting at York for Edinburgh, change there; staying on gets you in forty minutes later." What she has seen before: these usually clear within the quarter-hour. Then: "I'll be in coach C if you want the detail," and the microphone goes off. A manager who opens with the line's history keeps a carriage waiting for the sentence it needs.

On the train	In the interview
"Held for about fifteen minutes"	The one-sentence answer
The failed train and the signal	How it works
The York connection	One concrete case
Change at York, or arrive later	Where it breaks, or what it costs
"These usually clear quickly"	Your experience
"I'll be in coach C"	Offering depth, then stopping

Breaks down when: passengers cannot interrupt an announcement; an interviewer can, at any second, and will. Wrong inference: "I may finish my planned answer before anyone speaks." The announcement also goes one way, while the interview's follow-ups are where you show depth.

In real terms: say the answer, show how it works on one case, name where it breaks, stop inside two minutes and offer the next step.

Picture it

a woman in a green jacket explains with an open palm in front of a blank whiteboard, with a small microphone and a stack of books on the desk. — An illustration to help it stick. The mechanism is in the sections above.

Try it

Answer first, then check. Nothing is saved.

Question 1 of 7

Ticketing design round.

The interviewer asks: “How do your seat holds expire?” Your first sentence: “A held seat goes back on sale by itself ten minutes after it was held.” The interviewer says: “Go on.” What do you say next?

Question 2 of 7

Ticketing design round, deep dive. Asked “How does your waiting room keep the on-sale fair?”, you have given a 90-second answer: one sentence, how a fan's place is given and admitted, an example, where it breaks and a case from your last job.

What do you say next?

Question 3 of 7

Ticketing design round. It is minute 33, and the deep dives end at minute 45. The interviewer plans to spend what is left on concept questions, each taking your answer plus about 1 minute of follow-up. Kim answers each in about 90 seconds. Lee, who covers everything she knows, takes about 4 minutes each.

Counting only questions whose follow-up ends by minute 45, how many questions does each get through?

Question 4 of 7

Ticketing design round. Your design caches each show's seat map in Redis for 5 seconds; bookings are written to Postgres. The interviewer asks: “When does that cache give a fan a wrong answer?” Your first sentence and the mechanism are out.

Which sentence comes next?

Question 5 of 7

Ticketing design round. The interviewer asks how your on-sale stops two fans from buying the same seat, and when that can still go wrong. Speak for 60–120 seconds at 150 words a minute, one part per line, each line starting with its label: Headline:, Mechanism:, Example:, Breaks:, Experience: (optional, only a true case) and Offer:.

Write the answer you would say.

Your answer (optional, stays on this page)

Question 6 of 7

Notes from a ticketing mock: “Asked ‘How do you stop two fans buying one seat?’, she lost her place around minute 2 and never reached the locking.” She says nerves scatter her answers.

Which practice change fits?

Question 7 of 7

A mock interviewer always cuts in about 30 seconds into an answer with the next question. The candidate speaks at about 150 words a minute. Asked “How do your seat holds expire?”, she says: Holds expire when the seat map is read, so no timer or sweeper job has to run. When a fan picks a seat we write a hold row with the moment it lapses, ten minutes ahead, and from then on every read of the seat map, whether it comes from a fan browsing the plan or from another fan trying to book that same seat, compares the row's lapse time with the database clock and treats a hold whose time has passed as a free seat, which the next booking simply overwrites in its own transaction. So a fan who picks a seat and walks away loses it ten minutes later, the first time anyone looks at it. It breaks if she is still paying when the ten minutes run out, so checkout extends the hold before it charges her card.

When the interviewer cuts in, what have they heard?

Go deeper

Pro tip

Record yourself answering three questions from this week's topics, then play each back with a stopwatch. Note the second at which your first sentence answered the question, and the second you stopped. Rewrite any answer whose question was still unanswered at ten seconds.

Checked against the tools and docs as of 2026-10-06.

Predict first