Senior Backend Engineer

A connected route from foundations to production systems: 11 stages and about 310 hours, including practice and projects. Learn, practise, and prove each stage.

Set a target
Your progress0 of 48 topics
Current stageFoundations

Stage 1 of 11

Your paceNot set

Set a target on the planner

Take the placement check (10 min)

Draft. This path has not been reviewed by a second person yet. Topic order, estimates and tasks may change.

Arrows run from a prerequisite to what it unlocks. Select a topic to open it.
Filled: doneHeavy outline: in progressDashed: waiting on a prerequisiteDotted: skipped

The list view has the same topics and works with any screen reader.

  1. Stage 1: Foundations

    7 topics · 28 h · milestone: Serve a typed request locally0 / 7
    Stage project and rubric

    Serve a typed request locally. Replay it from the shell and explain each network hop and the handler's asynchronous work.

    Use your own small service or a disposable local example. Score each criterion: 0 missing, 1 partial, 2 demonstrated.

    • You demonstrate the stage milestone with reproducible inputs and outputs.
    • You explain one design trade-off using the topics in this stage.
    • You test a failure or boundary case and explain how your design responds.

    Target: 2 on every criterion. Record your evidence in the notes of the stage's last topic. Report a problem with this project.

  2. Stage 2: Data

    12 topics · 46 h · milestone: Build an order store0 / 12
    Stage project and rubric

    Build an order store. Tune five supplied slow queries and explain the observed plan changes and one transaction anomaly.

    Use your own small service or a disposable local example. Score each criterion: 0 missing, 1 partial, 2 demonstrated.

    • You demonstrate the stage milestone with reproducible inputs and outputs.
    • You explain one design trade-off using the topics in this stage.
    • You test a failure or boundary case and explain how your design responds.

    Target: 2 on every criterion. Record your evidence in the notes of the stage's last topic. Report a problem with this project.

  3. Stage 3: APIs

    4 topics · 24 h · milestone: Ship a paged orders endpoint0 / 4
    Stage project and rubric

    Ship a paged orders endpoint. An older client can retry safely and still read its expected response.

    Use your own small service or a disposable local example. Score each criterion: 0 missing, 1 partial, 2 demonstrated.

    • You demonstrate the stage milestone with reproducible inputs and outputs.
    • You explain one design trade-off using the topics in this stage.
    • You test a failure or boundary case and explain how your design responds.

    Target: 2 on every criterion. Record your evidence in the notes of the stage's last topic. Report a problem with this project.

  4. Stage 4: Identity and application security

    3 topics · 22 h · milestone: Protect two users' order histories0 / 3
    Stage project and rubric

    Protect two users' order histories. Verify session expiry, access isolation and secret rotation.

    Use your own small service or a disposable local example. Score each criterion: 0 missing, 1 partial, 2 demonstrated.

    • You demonstrate the stage milestone with reproducible inputs and outputs.
    • You explain one design trade-off using the topics in this stage.
    • You test a failure or boundary case and explain how your design responds.

    Target: 2 on every criterion. Record your evidence in the notes of the stage's last topic. Report a problem with this project.

  5. Stage 5: Testing and delivery

    3 topics · 24 h · milestone: Deliver the API in a container from CI0 / 3
    Stage project and rubric

    Deliver the API in a container from CI. A failing contract prevents promotion and a previous build still starts.

    Use your own small service or a disposable local example. Score each criterion: 0 missing, 1 partial, 2 demonstrated.

    • You demonstrate the stage milestone with reproducible inputs and outputs.
    • You explain one design trade-off using the topics in this stage.
    • You test a failure or boundary case and explain how your design responds.

    Target: 2 on every criterion. Record your evidence in the notes of the stage's last topic. Report a problem with this project.

  6. Stage 6: Performance and scale

    4 topics · 34 h · milestone: Load-test a read-heavy service0 / 4
    Stage project and rubric

    Load-test a read-heavy service. Submit a capacity estimate and a before/after trace identifying its bottleneck.

    Use your own small service or a disposable local example. Score each criterion: 0 missing, 1 partial, 2 demonstrated.

    • You demonstrate the stage milestone with reproducible inputs and outputs.
    • You explain one design trade-off using the topics in this stage.
    • You test a failure or boundary case and explain how your design responds.

    Target: 2 on every criterion. Record your evidence in the notes of the stage's last topic. Report a problem with this project.

  7. Stage 7: Reliability

    3 topics · 28 h · milestone: Keep a slow dependency from exhausting the service0 / 3
    Stage project and rubric

    Keep a slow dependency from exhausting the service. Demonstrate bounded work and recovery when it returns.

    Use your own small service or a disposable local example. Score each criterion: 0 missing, 1 partial, 2 demonstrated.

    • You demonstrate the stage milestone with reproducible inputs and outputs.
    • You explain one design trade-off using the topics in this stage.
    • You test a failure or boundary case and explain how your design responds.

    Target: 2 on every criterion. Record your evidence in the notes of the stage's last topic. Report a problem with this project.

  8. Stage 8: Distributed data

    6 topics · 38 h · milestone: Design a multi-replica order log0 / 6
    Stage project and rubric

    Design a multi-replica order log. State a consistency guarantee, demonstrate a failure and explain recovery.

    Use your own small service or a disposable local example. Score each criterion: 0 missing, 1 partial, 2 demonstrated.

    • You demonstrate the stage milestone with reproducible inputs and outputs.
    • You explain one design trade-off using the topics in this stage.
    • You test a failure or boundary case and explain how your design responds.

    Target: 2 on every criterion. Record your evidence in the notes of the stage's last topic. Report a problem with this project.

  9. Stage 9: Observability and operations

    2 topics · 22 h · milestone: Instrument an order call0 / 2
    Stage project and rubric

    Instrument an order call. Find the slow span, compute an SLO from a sample and write the incident follow-up.

    Use your own small service or a disposable local example. Score each criterion: 0 missing, 1 partial, 2 demonstrated.

    • You demonstrate the stage milestone with reproducible inputs and outputs.
    • You explain one design trade-off using the topics in this stage.
    • You test a failure or boundary case and explain how your design responds.

    Target: 2 on every criterion. Record your evidence in the notes of the stage's last topic. Report a problem with this project.

  10. Stage 10: Architecture and senior practice

    2 topics · 26 h · milestone: Write and review an RFC to split one domain boundary0 / 2
    Stage project and rubric

    Write and review an RFC to split one domain boundary. Document rejected options, estimate delivery and mentor through a revision.

    Use your own small service or a disposable local example. Score each criterion: 0 missing, 1 partial, 2 demonstrated.

    • You demonstrate the stage milestone with reproducible inputs and outputs.
    • You explain one design trade-off using the topics in this stage.
    • You test a failure or boundary case and explain how your design responds.

    Target: 2 on every criterion. Record your evidence in the notes of the stage's last topic. Report a problem with this project.

  11. Stage 11: AI-backed services

    2 topics · 18 h · milestone: Build a small source-linked answer service from fixtures0 / 2
    Stage project and rubric

    Build a small source-linked answer service from fixtures. Compare quality, cost and latency against a fixed evaluation set.

    Use your own small service or a disposable local example. Score each criterion: 0 missing, 1 partial, 2 demonstrated.

    • You demonstrate the stage milestone with reproducible inputs and outputs.
    • You explain one design trade-off using the topics in this stage.
    • You test a failure or boundary case and explain how your design responds.

    Target: 2 on every criterion. Record your evidence in the notes of the stage's last topic. Report a problem with this project.

Source inventory and coverage

48 topics map to 112 unique activities. Shared resources count once. Every topic has a self-check; every stage has a project rubric.

Supplementary pages kept outside this path:

Pages under Library and Practice come from, or build on, Donne Martin's System Design Primer (CC BY 4.0).

Esc
↑ ↓ to move↵ to open