Docs Engineering Portfolio
When I started my career in docs engineering, I thought documentation was just about explaining how things work. After years of working with developers at companies like Ably, Couchbase, and Atlas Copco, I've learned that great documentation is really about enabling people to succeed with complex technology.
My focus has been on taking complicated systems - from real-time messaging platforms to industrial manufacturing equipment - and creating documentation that developers and engineers can actually use to solve real problems. Each project taught me something different about how people learn and implement technology. The framework I keep returning to is Diátaxis, which splits docs into tutorials, how-tos, reference, and explanation so readers can find what they need in the mode they are actually in.
My work at Ably
Live in production: docs, pricing, LiveSync and LiveObjects, all redesigned and built by me.
Since joining Ably in 2023, I've focused on making real-time messaging technology accessible to developers. Working with WebSockets, Server-Sent Events, and database sync requires explaining complex concepts in ways that help developers build production-ready applications.
Server-sent events documentation.
Created comprehensive guides for real-time streaming using SSE, including code examples and troubleshooting sections. Built interactive demos showing connection flow and error handling. Specific sections: Protocol overview, Connection setup, Event handling, Error recovery patterns.

Webhooks security documentation.
Developed security-focused documentation for webhook implementation, covering HMAC authentication and security best practices. Includes practical examples for signature verification. Key areas: Webhook setup, Security configuration, Signature validation, Event filtering, Rate limiting.

Troubleshooting guides & developer support.
Built structured troubleshooting workflows using HAR file analysis and developer support resources to reduce support ticket volume by 40%. Documentation areas: Error code reference, Network diagnostics, Connection troubleshooting, Performance optimization, Debug logging setup.

Developer journey mapping & information architecture.
Redesigned documentation structure based on developer workflows and user research. Improved navigation patterns and information architecture.

Channels & pub/sub documentation.
Authored core messaging documentation for Ably's real-time pub/sub system, including channel options and presence features. Content sections: Channel creation, Message publishing, Subscription handling, Presence member tracking, Channel states, Message history.

Content restructuring & information architecture.
Led comprehensive information architecture overhaul to improve developer experience. Consolidated scattered content into logical sections and implemented docs-as-code workflows.

My time at Couchbase
As Lead Docs Engineer at Couchbase from 2022 to 2023, I worked on making NoSQL databases approachable for mobile developers. The challenge was explaining distributed database concepts to developers accustomed to simpler storage solutions, while maintaining the technical depth needed for production implementations.
Mobile platform documentation.
Built scalable documentation framework for Couchbase Lite and Sync Gateway platforms. Created cross-platform replication guides and conflict resolution documentation. Key sections: Installation guides, Database setup, Query APIs, Replication configuration, Conflict resolution strategies, Performance tuning.

Cross-platform API documentation.
Authored API docs spanning Couchbase Cloud, Mobile, and Server platforms. Implemented consistent SDK documentation patterns and OpenAPI specifications. Documentation areas: REST API reference, SDK integration guides, Authentication methods, Data modeling, Query language (N1QL), Cluster management.


Repository consolidation project.
Consolidated fragmented documentation repositories into unified GitHub monorepo structure. Migrated 15+ separate repos, implemented docs-as-code workflows, and established consistent contribution guidelines. Project scope: Content migration, Build system integration, Version control optimization, Workflow automation, Cross-team collaboration protocols, Documentation standards.

My work at Atlas Copco
Working as a Docs Engineer at Atlas Copco from 2018 to 2021 taught me that manufacturing documentation can be life-or-death. When your documentation goes to factories worldwide, unclear instructions don't just frustrate users - they can shut down production lines or cause injuries.
Self-pierce riveting documentation.
Authored technical documentation for Henrob self-pierce riveting systems, solving lightweighting challenges with mixed materials in automotive and industrial applications.

Henrob tape feed riveting documentation.
Created comprehensive guides for Henrob tape feed self-pierce riveting systems, featuring servo technology with super-fast cycle times as low as 1.2 seconds per rivet for high-volume automotive body-in-white production.


Henrob blow feed riveting documentation.
Developed technical manuals for Henrob blow feed self-pierce riveting systems, featuring magazine rivet feed with energy-efficient operation achieving 7Wh per rivet and setting force up to 85,000 N for automotive body-in-white manufacturing.


My work at CDW
My time as a Technical Solutions Specialist at CDW UK from 2021 to 2022 showed me how docs engineering works in enterprise sales. Unlike developer-focused documentation, enterprise customers needed materials that helped multiple stakeholders - from IT directors to compliance officers - understand complex technology implementations.
Cloud platform API documentation.
Authored developer-centric API documentation for AWS and Azure cloud services, supporting CDW UK's cloud migration and hybrid multi-cloud solutions.

Multi-language SDK documentation.
Created SDK documentation supporting multiple programming languages and frameworks for DevOps and cloud development workflows.

Developer onboarding resources.
Built comprehensive onboarding materials and professional services documentation to accelerate developer adoption of cloud platforms.

How I think about documentation
Good documentation enhances learning through low effort and helps people problem solve effectively:
| Principle | Description |
|---|---|
| Fast to scan | Developers are usually in a hurry and need information quickly |
| Copy-pasteable | Working code examples are gold for immediate implementation |
| Contextual | Explain the "why" not just the "how" to build understanding |
| Tested | If the code doesn't work, the documentation is useless |
| Visual when needed | Strategic use of images and diagrams to clarify complex concepts |
| Workflow-oriented | Create maintainable documentation workflows that scale with teams |
| AI-assisted | Implement AI systems for grunt work, freeing docs engineers and UX teams to focus on user experience optimization |