Mira Carvalho
Principal Engineer, runtime team @ Cloudflare
Wrote the kernel scheduler your favorite database probably blocks on. Teaches Systems & Performance and the dreaded Wednesday lab.
Twelve weeks. Six instructors. One discipline. We teach engineers to write code that other engineers actually want to read — by treating software as a craft, not a checklist.
Each cohort moves through six tracks taught by working practitioners. The pace is unforgiving but the cohort is small — eight per instructor, no exceptions.
Memory, concurrency, and the cost of every line. We descend through the stack until you can read assembly without flinching.
↗ 02 / 06Consensus, replication, and what to do when the network lies. Build a Raft from scratch; lose sleep over Byzantine generals.
↗ 03 / 06Build a small language end to end. Then build the tooling — formatter, language server, debugger — that makes it usable.
↗ 04 / 06Code that humans actually want to touch. Typography, motion, latency budgets, accessibility — the engineering behind taste.
↗ 05 / 06Trust, but verify. Implement the primitives, break the textbook protocols, then patch them. No black boxes.
↗ 06 / 06A weekly seminar on the literature: Knuth, Hickey, Hoare, Lamport, Ousterhout. The papers that shaped how good engineers think.
↗Every instructor still ships code in the field they teach. Office hours are Friday afternoons; the conversations are why most graduates say they came.
Principal Engineer, runtime team @ Cloudflare
Wrote the kernel scheduler your favorite database probably blocks on. Teaches Systems & Performance and the dreaded Wednesday lab.
Östberg"
loading="lazy"
onerror="this.remove()" />
Former staff engineer, distributed systems @ Stripe
Twelve years on payments infrastructure. Has opinions about clocks. Co-authored the consensus chapter you'll read in week four.
Compiler engineer @ Modular · ex-LLVM contributor
Builds languages by day; teaches you how to read compiler errors without crying by night. Patient, until you skip a lecture.
I came in writing code that worked. I left writing code that other engineers asked to read. That's the difference Lattice makes — and you can't unlearn it.
We accept thirty-two engineers per cohort. The application is a take-home, a written essay, and a ninety-minute conversation. No GPAs, no referrals, no tricks.
Begin your application