Singapore version. Adds what Singapore bank, insurer and payments interviewers listen for: MAS's 4-hour limits for critical systems, the 1-hour incident notice, PDPA breach notification and local regions. US version

System Design Interview Framework (Singapore)

A timed system design framework for Singapore interviews, with the MAS limits on critical system downtime, the 1-hour incident notice and PDPA breach deadlines.

The interactive tool loads here when JavaScript runs.

About this tool

What is System Design Interview?

The four-step structure on this page (requirements, high-level design, detailed design, scaling) works for any 45 to 60 minute round. At a Singapore bank, insurer or payment service provider, the non-functional requirements come partly from MAS. Under its Notice on Technology Risk Management, a regulated firm must keep the total unscheduled downtime of each critical system to no more than 4 hours in any 12 months, set a recovery time objective of no more than 4 hours, and tell MAS within 1 hour of discovering a system malfunction or IT security incident with severe and widespread impact.

MAS's FAQ gives examples of critical systems: ATM systems, online banking, and systems supporting payment, clearing or settlement. A failure absorbed by a high-availability set-up without disrupting service does not need reporting, so the design itself decides how often the notification clock starts. Partial or intermittent disruption counts towards the downtime budget, not only full outages.

Personal data brings in the PDPA. Once an organisation assesses a data breach as notifiable, it must notify the PDPC as soon as practicable and no later than 3 calendar days after that assessment. Ticks on the framework and topics are saved in your browser only.

  • 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

What 4 hours a year means as availability

Input

A critical online banking system; MAS limit of 4 hours of unscheduled downtime in any 12 months

Output

1 − 4 ÷ 8,760 = 99.954% availability, counting partial and intermittent disruption, over a rolling 12-month window

The window rolls: in MAS's worked example, a 3-hour outage in July and a 30-minute one in December leave 30 minutes for the rest of the 12 months. Say how you would spend that budget: no planned single points of failure, canary releases, and fast rollback.

Recovery time versus notification time

Input

Disruption starts at T; the team discovers it at T + 1 hour

Output

MAS must be told by T + 2 hours; the 4-hour recovery time objective still runs from T

This is MAS's own FAQ example. The design needs alerting that measures customer-facing failure quickly, because detection time eats into the recovery objective.

Choosing regions for a Singapore workload

Input

Primary in AWS Asia Pacific (Singapore), ap-southeast-1, with 3 availability zones; disaster recovery option in Asia Pacific (Malaysia) or (Jakarta)

Output

Synchronous replication across the 3 Singapore zones; asynchronous copy to a second region if the data may leave Singapore

AWS lists 3 availability zones in Singapore, and both nearby regions as opt-in. A zone-level failover keeps the RTO inside 4 hours; a cross-border copy raises data-location questions to clarify with the interviewer.

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

  • Write the MAS figures under non-functional requirements: 4 hours of downtime in 12 months per critical system, RTO of 4 hours or less, notice within 1 hour.
  • Point out that a failover that keeps the service running avoids a reportable incident; MAS's FAQ says a failure recovered through high availability need not be reported.
  • For personal data, add audit logs that let you assess quickly whose data was involved; the PDPA clock is 3 calendar days from the assessment.
  • Name the region: ap-southeast-1 is Singapore, and AWS lists Malaysia and Jakarta as opt-in neighbours.

Sources and further reading

  1. Frequently Asked Questions: Notice on Technology Risk Management, Monetary Authority of Singapore. Critical systems, 1-hour notice, 4-hour downtime in 12 months, RTO of 4 hours, worked examples
  2. Guidelines on Risk Management Practices: Technology Risk, Monetary Authority of Singapore
  3. Personal Data Protection Act 2012, section 26D, Singapore Statutes Online. Notify the PDPC no later than 3 calendar days after assessing a breach as notifiable
  4. Guide on Managing and Notifying Data Breaches Under the PDPA, Personal Data Protection Commission. Notify the Commission as soon as practicable and no later than three calendar days after determining a breach is notifiable
  5. AWS Regions, Amazon Web Services. Singapore ap-southeast-1 with 3 AZs; Malaysia and Jakarta opt-in

Frequently asked questions

What is the MAS downtime limit for critical systems?

Under MAS's Notice on Technology Risk Management, each critical system's maximum unscheduled downtime must not exceed 4 hours within any 12-month period, counting total, partial and intermittent disruption.

How fast must a bank in Singapore report an IT incident to MAS?

Within 1 hour of discovering a system malfunction or IT security incident with a severe and widespread impact on operations, or a material impact on customers, whenever it happens. Off-peak timing does not remove the duty if the impact test is met.

Which systems count as critical in MAS's rules?

MAS's FAQ gives ATM systems, online banking systems, and systems that support payment, clearing or settlement as examples. Each firm keeps its own framework and list of critical systems.

What is the PDPA deadline for reporting a data breach?

Section 26D of the PDPA: once an organisation assesses that a breach is notifiable, it must notify the PDPC as soon as practicable and no later than 3 calendar days after the assessment. A breach is notifiable if it causes or is likely to cause significant harm, or is of a significant scale.

Should I replicate outside Singapore in a design answer?

Ask first. Many answers keep the primary and synchronous replicas across the three Singapore availability zones, then discuss an asynchronous copy in a neighbouring region for disaster recovery, with the data-location trade-off stated.

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.