You already know: strategy, problem selection and decision-making under uncertainty (this domain); system design trade-offs (System design thinking); incidents and SLOs (D14, D11).
Why this matters for Atlas. At staff level, writing is the main way to think clearly, align many people and leave decisions that outlast meetings. Most engineering documents fail the same way: they bury the point, skip the alternatives, and assume the reader has context they don't. This lesson covers the four documents a staff engineer writes most (design docs, architecture decision records, postmortems and strategy docs), the structure that makes each work, and habits for prose that busy engineers actually read, plus small tools that check a document before you send it.
1. Write for the reader who stops early
The question. Why do good designs get ignored?
Start from nothing. Most readers read the title, the first paragraph and the headings, then decide whether to continue. So: lead with the conclusion (what you propose, why, what you need from the reader), make headings carry the argument ("Shard the index by course" beats "Design"), and put detail where those who need it can find it. Prefer short sentences, concrete numbers over adjectives ("p95 280 ms → 190 ms" beats "much faster"), active voice that names who does what, and one idea per paragraph. Define terms once; don't make readers decode acronyms.