2 min lesson
Writing for the right audience
Put yourself in this case: "You're writing up an Agent bug. What should the leadership brief lead with and how does it differ from the engineering ticket?" Give the clearest next step.
Step 1 of 2
The same bug needs three different documents. The JD names clear multi-audience writing as a core skill and the take-home will almost certainly make you produce at least one of them cold.
A PQE is the translation layer. The user feels the pain, the engineer needs to reproduce it and the exec needs to decide whether it's worth a sprint. Each reader has a different question, so the same facts get reordered, recompressed and re-toned for each.
Lead with impact and a recommendation.
One screen, ruthlessly summarized.
Decision-oriented: what should we do?
Numbers up front, detail in an appendix.
Precise, reproducible, evidence-rich.
Steps to repro, expected vs actual, logs.
Version, OS, model, frequency named.
Low ambiguity - no 'sometimes it breaks'.
Empathetic and plain-spoken.
Honest status without overpromising.
A workaround if one exists.
No internal jargon or blame.
Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.
The leadership brief and the engineering ticket invert almost every choice.