How delivery works
We optimize for working adults: async depth during the week, live blocks for synthesis, and mentor feedback that references your actual artifacts instead of generic rubric language.
01 — Intake
We confirm toolchain access, timezone fit, and whether you need enterprise invoicing.
02 — Baseline survey
Short questionnaire maps your comfort with SQL, operations, and modeling so mentors pre-read context.
03 — Weekly rhythm
Recorded briefs plus live clinics; labs due mid-week so mentors annotate before weekends.
04 — Review windows
Async diffs include explicit questions — we expect you to answer them before the next milestone unlocks.
05 — Capstone gate
Rubric covers rollback narrative, observability hooks, and plain-language README for reviewers.
06 — Retro
Anonymous survey shapes the next cohort; we publish aggregate changes when feasible.
Before / after workflow
Before: ad-hoc SQL changes land without rollback notes; on-call learns via outages.
After: migrations ship with paired plans, rehearsal timings, and comms templates borrowed from our drills.
Talk through a pilot