Technical Writing

Turn an informal, rambling explanation into a structured, precise internal doc.

Draft a compliance-framework-aligned policy template, flagging where current practice likely falls short.

Document an endpoint fully, with a realistic example request/response, not placeholders.

Turn informal technical notes into a numbered guide with prerequisites and checkpoints.

Prioritize what a new engineer needs day 1 vs. what they’ll pick up naturally.

Explain system architecture component-by-component, including the why behind decisions.

Write a blameless postmortem with a real timestamped timeline and separated fix/prevention.

Extract action items that trace to specifics in the postmortem, prioritized against team capacity.

Recommend architecture changes justified by a specific scale target, with trade-offs stated.