Skip to content

Staff Engineering

The route through systems, performance, and failure, in the order they bite

For technical staff. The order follows the cost model down: what a data structure costs, then what the silicon costs, then what the network costs once the first two are right.

  1. 01SoftwareFundamentalsInterfaces, indexes, and the shape of a running system
  2. 02Operating SystemsFundamentalsWhat the kernel does for you, and what it charges
  3. 03Data StructuresFundamentalsThe cost model under every query you will be asked to explain
  4. 04DatabasesFundamentalsHow data survives a crash, and what a query costs
  5. 05HardwareFundamentalsAccelerators, memory bandwidth and the fabric between devices
  6. 06Distributed SystemsFundamentalsConsensus and partial failure, the two facts that shape everything
  7. 07Compilers and RuntimesFundamentalsKernels and fusion, where the throughput is actually won
  8. 08Data EngineeringFundamentalsPipelines and lineage, because the data is the dependency
  9. 09Performance EngineeringApplicationRoofline, tail latency and what a utilization number hides
  10. 10DeploymentApplicationServing, rollout, and the operational surface of a model
  11. 11AgentsApplicationLoops, tool calls and sandboxing, where a model becomes a process with permissions
  12. 12CryptographyFundamentalsHashes, signatures, and content addressing, the integrity layer under a supply chain
  13. 13SecurityApplicationIsolation, weights, and the attack surface a model adds
  14. 14Engineering PracticeApplicationReview, testing, and the discipline that holds under load
  15. 15Resume FeedbackAppendix: InterviewsHow a staff-level record reads to someone deciding in six seconds
  16. 16LeetCode PatternsAppendix: InterviewsThe coding round family by family, each with the signals that name it and a tested template
  17. 17Interview TipsAppendix: InterviewsWhat a systems interview is really scoring