I write Architecture Decision Records (ADRs) and system design documentation that capture the real context behind your technical decisions — so future engineers understand not just what was built, but why, and what would cause that decision to be revisited.
ADR process: async Q&A with your engineers (written questions via email, Slack, or a shared doc — non-intrusive, no meetings required unless preferred); context and alternatives research; ADR drafted in your team's preferred format (Nygard, MADR, Y-Statements); consequences documented honestly including known downsides; and status accurately classified (Proposed, Accepted, Superseded, Deprecated).
Historical ADR writing is the most common engagement — decisions made under pressure that were never documented. Batch writing of 5-50 historical decisions available.
System design documentation: C4 context and container diagrams; service interaction and data flow diagrams; integration maps; database schema documentation with field descriptions and relationships; deployment architecture documentation; and API contract documentation between internal services.
My engineering background means I can evaluate the technical tradeoffs in what I'm documenting — producing ADRs that are genuinely useful rather than superficially formatted.