Canada version. Adds the Canadian constraints to raise at banks, insurers and Quebec-facing products: OSFI Guideline B-13, Quebec Law 25, PIPEDA breach rules and keeping data in Canada. US version

System Design Interview Framework (Canada)

A timed system design framework for Canadian tech interviews, with OSFI B-13 recovery, Quebec Law 25 transfers, PIPEDA breach records and in-Canada replication.

The interactive tool loads here when JavaScript runs.

About this tool

What is System Design Interview?

The four steps on this page (requirements, high-level design, detailed design, scaling) are the same in Toronto, Montreal or Vancouver as anywhere else, and they fit a 45 to 60 minute round. What changes in Canada is the list of requirements you should raise before drawing anything. Banks and insurers regulated by OSFI work under Guideline B-13 on technology and cyber risk, in effect since January 1, 2024, which expects technology services to recover within timeframes the institution defines and disaster recovery plans to be tested against severe but plausible scenarios.

Personal information adds two more. Under PIPEDA an organization must report a breach to the Privacy Commissioner of Canada when it is reasonable to believe it creates a real risk of significant harm, and keep a record of every breach for two years. In Quebec, since September 2023 a business must complete a privacy impact assessment before sending personal information outside the province and cover the transfer with a written agreement, which matters as soon as your design puts a Quebec customer's data outside the province: in a US region, in a recovery region in another province such as Calgary, or with a vendor elsewhere.

The worked examples below turn those into numbers: the bandwidth a Montreal to Calgary replica needs, and what a bilingual search index costs. Ticks on the framework and topics stay in your browser.

  • 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

Replicating between two Canadian regions

Input

A bank ledger changes 2 TB a day; disaster recovery copy kept in a second Canadian region, for example AWS Canada (Central) to Canada West (Calgary)

Output

An average of about 185 Mbit/s of replication traffic; one 1 Gbit/s link would be busy 4.4 hours a day

2 TB x 8 bits divided by 86,400 seconds is 185 Mbit/s on average, and 16,000 seconds of a 1 Gbit/s link. Changes are not spread evenly, so size the link for the busiest hour and say what recovery point you can promise if replication falls behind. B-13 leaves the recovery timeframe to the institution, so the number you propose is part of the answer.

Search in English and French

Input

50 million product listings, each indexed in English and French, 2 KB of index per listing per language

Output

About 200 GB of index, double a single-language build

50 million x 2 languages x 2 KB is 200 GB. Each language needs its own analyzer (stemming, accents, stop words), so the design has two indexes or two fields per document and a rule for which one a query hits. It is a small example, but naming it early shows you have designed for Canadian users rather than adapting a US design afterward.

A Quebec customer's data in a US region

Input

A Montreal retailer's customer profiles stored in a US cloud region for cost

Output

A privacy impact assessment and a written agreement first, and the same applies to a Canadian region outside Quebec

Quebec's Commission d'accès à l'information says the transfer may go ahead only if the assessment shows the information would be adequately protected. Moving the profiles to a Canadian region does not end the question: the rule is about leaving Quebec, not leaving Canada, so a region in another province needs the same assessment and agreement. In an interview, ask where Quebec data may go before choosing regions.

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 whether the employer is federally regulated. If it is a bank or insurer, treat disaster recovery testing and third-party dependencies as first-class requirements, as B-13 does.
  • Ask where users are. Quebec users bring Law 25 into scope and usually French as well as English content.
  • Keep a breach record store in your design for systems with personal information: PIPEDA requires records of all breaches, not only the reportable ones, for two years.
  • Name a recovery time and recovery point in your scaling step. B-13 leaves them to the institution, so the interviewer wants to hear your reasoning.

Sources and further reading

  1. Guideline B-13: Technology and Cyber Risk Management, Office of the Superintendent of Financial Institutions. Outcomes, recovery expectations and disaster recovery testing against severe but plausible scenarios.
  2. OSFI releases final Guideline B-13, Office of the Superintendent of Financial Institutions. Effective date of January 1, 2024.
  3. Principaux changements introduits par la Loi 25, Commission d'accès à l'information du Québec. In French. Privacy impact assessment and written agreement before communicating personal information outside Quebec.
  4. What you need to know about mandatory reporting of breaches of security safeguards, Office of the Privacy Commissioner of Canada. Real risk of significant harm, reporting and two-year breach records.
  5. AWS Regions, Amazon Web Services. Canada (Central) and Canada West (Calgary).

Frequently asked questions

What is OSFI Guideline B-13 and does it matter in an interview?

B-13 is OSFI's guideline on technology and cyber risk management for federally regulated financial institutions, in effect since January 1, 2024. It expects a stable, scalable and resilient technology environment, recovery of services within timeframes the institution sets, and disaster recovery plans tested against severe but plausible scenarios. At a Canadian bank or insurer, mentioning it while you discuss failure and recovery shows you know the operating context.

How does Quebec Law 25 affect where data is stored?

Since September 2023 a business must complete a privacy impact assessment before communicating personal information outside Quebec, and the transfer must be covered by a written agreement. It can go ahead only if the assessment shows the information would be adequately protected. The rule is about leaving Quebec, not leaving Canada, so a disaster recovery copy in Calgary needs the assessment and agreement too. In a design, ask where Quebec data may go before choosing regions, and treat vendor location as a requirement to ask about.

When does a breach have to be reported under PIPEDA?

When it is reasonable in the circumstances to believe it creates a real risk of significant harm to an individual. The organization reports it to the Office of the Privacy Commissioner of Canada and notifies affected individuals. It must also keep records of all breaches, reportable or not, for two years, which is worth adding to the data model.

Can a Canadian company keep primary and backup data both in Canada?

Yes. AWS, for example, lists two Canadian regions, Canada (Central) and Canada West (Calgary), each with three availability zones, so a design can replicate between them without leaving the country. Ask the interviewer whether in-country recovery is a requirement before you add a US region.

Should a Canadian system design handle English and French?

Ask, especially for products serving Quebec or federal government clients. Bilingual support affects the content model (one record with two language fields or two records), search (an analyzer per language), notifications and templates, and testing. It costs little to mention during requirements and a lot to retrofit.

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.