Technical content for AI and developer-focused companies.
I turn complex technologies into clear, technically grounded content that helps developers understand products, solve problems, and make better technical decisions.
Technical writer · AI/ML · Developer tools · Technical storytelling
Written for
Actian · Bright Data · Zenrows · ToolJet
Complex technology needs clear communication.
Four ways I help AI and developer-focused companies explain what they are building.
In-depth explainers, architecture deep dives, and research-backed content for technical audiences.
Learn more Developer TutorialsStep-by-step how-to guides, API walkthroughs, and integration tutorials developers can actually follow.
Learn more Product-Led ContentTechnical use cases, comparison pieces, and workflow guides that show what a product does and why it matters.
Learn more Technical Thought LeadershipFounder POVs, industry analysis, and technical narratives that build credibility and category authority.
Learn morePublished work you can evaluate.
Benchmarks, tutorials, and analysis written for technical readers and their teams.
An original benchmark of 200 requests across 7 targets, comparing performance and cost for large-scale scraping.
Read Technical Tutorials Build a Stateful Web Research Agent with Zenrows and LangGraphA production-grade tutorial for a stateful AI agent with retry logic and live web scraping.
Read Technical Tutorials Integrating Zenrows into smolagents for Production Web AccessA step-by-step guide to swapping smolagents' default web tool for a Zenrows-powered one so AI agents can read JavaScript-rendered and bot-protected pages.
Read AI/ML 5 Edge AI Architecture Patterns for Disconnected EnvironmentsAn architecture guide for running AI at the edge with no cloud connection required.
ReadTechnical enough to understand it. Writer enough to make people care.
Technical depth
Real time spent understanding the subject before writing a word: reading the docs, running the code, talking to the engineers. Not a generalist summarizing.
Storytelling
Content structured so readers can follow the argument and act on it. A clear thread from problem to solution, not a wall of correct information.
Reader-first
Written for the person who has to use the content (integrate the API, make the call, ship the thing), not the person who assigned it.
How the work gets done.
The brief, the technical challenge, the approach, and what happened next.
Challenge. The value of the role is often spread across product decisions, support, engineering, and internal communication, which makes it difficult to describe with a single metric or job description.
Approach. Interviewed nine senior technical writers, including practitioners from companies such as Google and Mastercard. Coded the interviews for recurring themes and used those themes to build the final narrative.
Outcome. The resource sparked sustained discussion among senior practitioners on LinkedIn, reached around 700 technical writers, and shifted how several of them framed the value of the role inside their own organizations.
View case study Case study A Reproducible Benchmark for Large-Scale Web ScrapingChallenge. Comparisons in this space are usually vague or self-serving. The piece had to define a fair methodology, run it across several real targets, and report results honestly, including where the product was not the fastest option.
Approach. Ran a defined test of 200 requests across 7 target sites, compared the platforms on performance and cost, and documented the method so a reader could reproduce it.
Outcome. Published as Zenrows' reference comparison for large-scale scraping, and ranks in search for "Apify vs Zenrows" and related evaluation queries.
View case study Case study Turning a Fragmented Topic Into Five Usable Architecture PatternsChallenge. Edge AI for disconnected environments is real but fragmented: the patterns are spread across separate industries and rarely named or compared. The piece had to make the space concrete without a cloud fallback to lean on, and stay useful to an architect rather than drifting into abstraction.
Approach. Researched how inference and control actually run offline across those industries, then distilled the field into five distinct patterns (the Drone, the Factory, Hierarchical Federated Learning, Store-and-Forward, and the Network), each with its constraints, trade-offs, and the situations it fits.
Outcome. Published on Actian's developer blog, where it ranks number one in search for the "edge AI architecture" keyword.
View case studyUnderstand, research, structure, write, refine.
A practical sequence that keeps the content accurate and the timeline predictable.
Understand
Learn what you are building and who it is for. The content can only be as clear as the understanding behind it.
Research
Read the docs, run the product, talk to your engineers. Claims get checked so you are not defending the piece later.
Structure
Decide the one thing the reader should walk away with, then build the outline around that. Structure is where a piece is won or lost.
Write
Draft for the reader who has to act on it. Plain sentences, complete code, no filler between the reader and the point.
Refine
Edit for accuracy, flow, and length. Every round removes friction between your product and the person evaluating it.
I write about technology for a living.
I came into technical writing from writing, and into AI and developer tools from a background in mathematics and hands-on machine learning. Long enough in to know the hardest part is not understanding the technology. It is knowing what your reader actually needs to walk away with.
Writing about technical content.
Frameworks and lessons from Tech & Storytelling, my newsletter on the craft.
A model for ranking technical content by how much work it does for the reader.
Read Craft Bridging Product and People in Technical WritingWriting that serves the product and the person using it at the same time.
Read Frameworks The PTS Framework: Problem, Tension, SolutionA structure for technical pieces that keeps a reader moving through the argument.
ReadI write about making technical content easier to understand.
A newsletter for technical writers who want to become better storytellers.