United Kingdom version. Adds what UK fintech and banking interviewers probe: FCA and PRA operational resilience, impact tolerances, the UK GDPR 72-hour breach clock and where UK workloads run. US version

System Design Interview Framework (UK)

A timed system design framework for UK tech interviews, with impact tolerances, the 72-hour UK GDPR breach clock and UK hosting choices worked into practice designs.

The interactive tool loads here when JavaScript runs.

About this tool

What is System Design Interview?

If you are interviewing at a UK bank, building society, insurer or payment firm, a design that only scales is half an answer. Since 31 March 2022 the FCA and PRA operational resilience rules have required these firms to identify their important business services and set an impact tolerance for each: the maximum tolerable disruption, which must always include a time limit and applies at peak times as well as normal ones. By 31 March 2025 firms had to have done the mapping and testing to stay within those tolerances. When you are asked how your payment service fails, answer in that frame: which service, what tolerance, and how you stay inside it.

This page gives you a four-step framework for a 45 to 60 minute round (requirements, high-level design, detailed design, scaling), six practice prompts and about 40 building blocks to revise. The worked examples below turn the UK rules into estimates you can put on the whiteboard: how much backlog builds up inside an impact tolerance, and how fast you can find affected users when the 72-hour breach clock starts.

Ticks on the framework and topics stay in your browser. The diagram link opens the site's Excalidraw-based drawing tool.

  • Four-step framework with time boxes, steps and tips
  • Six practice prompts with key components and focus areas
  • About 40 core topics with short explanations, including CAP, QUIC, gossip and Merkle trees
  • Checklists for framework steps and core concepts, saved in your browser
  • Link to an Excalidraw-based diagram tool for architecture sketches
Read the guide: System Design Interviews: A Four-Step Method with Real Numbers

Updated

How to use System Design Interview

  1. Open the Framework tab and read the four steps with their time boxes before your first practice session.
  2. Pick a prompt from the Practice Questions tab and set a 45 minute timer.
  3. Work through the steps in order: requirements and estimates, then a high-level diagram, then one or two components in detail, then bottlenecks and scaling.
  4. Use the Advanced Topics tab to look up any building block you reached for but could not explain clearly, such as consistent hashing, Bloom filters or the saga pattern.
  5. Draw the final design in the Diagram Tool from the Whiteboarding tab, and tick the steps and Core Concepts you handled well.

Worked examples

Backlog inside a 2-hour impact tolerance

Input

A card payment service at 1,500 payments a second at peak; the firm has set a 2-hour impact tolerance; the plan is to queue and replay

Output

10.8 million payments to hold, replay and reconcile if an outage runs the full 2 hours

1,500 x 7,200 seconds is 10.8 million. The tolerance is the firm's own choice, not a regulatory figure, but the arithmetic shows why "we will queue it" needs a queue sized for millions of messages, idempotent replay and a plan for customers who retry. Because tolerances apply at peak, size it with the peak rate, not the average.

Can you find affected users within the 72-hour clock?

Input

Audit logs of 40 TB; a full scan reads at 2 GB a second

Output

About 5.6 hours for one full scan

40 TB divided by 2 GB a second is 20,000 seconds. UK GDPR Article 33 asks controllers to notify a personal data breach without undue delay and, where feasible, within 72 hours of becoming aware of it. Two or three full scans fit, but only just with investigation time, so partitioning audit logs by user and date is worth proposing.

Disaster recovery inside the UK

Input

Requirement: primary and recovery copies both hosted in the UK, on AWS

Output

One UK region (London, eu-west-2) with three availability zones

AWS lists a single UK region, so a UK-only recovery design spreads across availability zones in London, adds a second provider or a firm's own data centre, or agrees with the interviewer that a recovery copy in another European region is acceptable. Saying which, and what each costs, is the trade-off the interviewer wants to hear.

Background and insight

System design rounds are open-ended on purpose. There is no single right answer, so the interviewer is scoring how you get to one: whether you pin down requirements before drawing boxes, whether your numbers are in the right order of magnitude, whether you can go deep on one component, and whether you name trade-offs instead of presenting one option as free. Seniority shows mostly in the last two.

Back-of-the-envelope numbers anchor everything. A day has 86,400 seconds, so 100 million requests a day is about 1,160 per second on average, and peak is commonly two to three times that. A 7-character Base62 short code gives 62⁷, about 3.5 trillion, combinations. A single SSD-backed database node can usually serve thousands of simple indexed reads per second, so 1,000 QPS rarely needs sharding, while 100,000 usually needs caching or partitioning.

The CAP theorem is often stated as "pick 2 of 3", which is misleading. Network partitions happen whether you choose them or not, so the real decision is what the system does during a partition: refuse some requests to stay consistent, or keep answering and risk stale reads. PACELC extends this with the latency versus consistency trade-off that applies even when the network is healthy, and it is a better lens for most interview discussions.

Common use cases

  • Preparing for a senior engineering loop

    Practise one prompt every few days with the four-step framework until the timing feels natural.

  • Filling knowledge gaps

    Use the Advanced Topics list as a checklist of building blocks you should be able to explain in two sentences.

  • Running mock interviews

    As an interviewer, pick a prompt and use its focus areas as the probes for the detailed design step.

  • Reviewing real designs

    Apply the same requirements, estimates and trade-offs structure when reviewing a design doc at work.

Tips and limitations

  • Ask which service the prompt maps to in business terms ("make a payment", "check a balance") and say you would treat it as an important business service with its own impact tolerance.
  • Express availability targets as time, as the PRA does: "back within 2 hours" says more in this room than "four nines".
  • Bring third parties into the failure discussion. Card schemes, cloud providers and identity checks are the dependencies that operational resilience mapping is meant to surface.
  • For any system holding personal data, add breach detection and a way to list affected people to your non-functional requirements.

Sources and further reading

  1. Operational resilience, Financial Conduct Authority. Firms in scope, important business services, impact tolerances and the 2022 and 2025 dates.
  2. SS1/21 Operational resilience: Impact tolerances for important business services, chapter 3, Prudential Regulation Authority. Definition of an impact tolerance, the time-based metric and peak times.
  3. UK GDPR Article 33: Notification of a personal data breach, legislation.gov.uk
  4. AWS Regions, Amazon Web Services. Europe (London) is the only UK region in the list.

Frequently asked questions

What is an impact tolerance and why would a UK interviewer ask about it?

Under the PRA's supervisory statement SS1/21 an impact tolerance is the maximum tolerable level of disruption to an important business service. It must include a time-based metric and applies at peak times as well as in normal circumstances. Banks, building societies, insurers and payment and e-money firms work under these rules, so be ready to explain how your design keeps a service within a stated disruption limit.

Which firms do the UK operational resilience rules cover?

The FCA lists banks, building societies, PRA-designated investment firms, insurers, recognised investment exchanges, enhanced scope SM&CR firms, payment and e-money institutions, consolidated tape providers and qualifying cryptoasset firms. The rules came into force on 31 March 2022, and mapping and testing had to be complete by 31 March 2025.

How does UK GDPR change a system design answer?

Treat breach handling as a requirement. Article 33 of UK GDPR asks controllers to notify a personal data breach without undue delay and, where feasible, within 72 hours of becoming aware of it. In a design that means audit logging, detection and a way to work out quickly whose data was involved.

Should a UK design keep everything in UK data centres?

Only if the requirements say so; ask. An employer or client may require UK hosting, or may accept other regions with the right transfer safeguards. Be ready to say how a UK-only requirement limits your disaster recovery options, since a single cloud region in London gives you separate availability zones but not geographic distance.

Is the system design round the same at UK banks as at product companies?

The framework is the same: requirements, high-level design, detail, scaling. What changes is the weight on failure. Be ready for follow-up questions on how a service degrades, what is queued and replayed, how you reconcile afterwards and which third parties you depend on, alongside the usual questions on throughput and storage.

Is there an in-depth guide to System Design Interview?

Yes. “System Design Interviews: A Four-Step Method with Real Numbers” covers the background, how it works, common pitfalls and worked examples. Read the full guide.