Technical Writer / Content Engineer
Hi, I'm Albert.
6 years making software documentation at C3 AI, AWS, and EY. Currently exploring what's next.
Documentation is an extension of the product.
Docs is how your users (and your user's agents) learn how to use your product. Often, docs can be the first look into how your users perceive the quality of your product. I firmly believe that documentation IS the product, and the best tech writers treat docs as a product itself.
My approach
Great docs come from collaboration. I work closely with product and engineering to understand what users need, then build documentation that meets them there. I also love teaching engineers how to write — the best docs orgs don't just have good writers, they have a culture where everyone values clear communication.
- Publishing process — I set up docs-as-code pipelines with Git, Markdown, and CI/CD. At C3 AI, I created the processes and templates that powered their documentation pipeline.
- Information architecture — At AWS, I consolidated three separate S3 guides into a single unified user guide.
- Technical expertise — I have a Computer Engineering degree from UIUC and have worked with highly technical software my entire career. I onboard fast.
- UI text & content— Documentation isn't limited to topics and guides. I write and edit UI text, error messages, and in-product copy to convey information cleanly.
Why hire a tech writer? Why not use AI to write everything?
I've seen a cultural shift in tech writing happen over the last year: AI is taking more and more of the share of the actual writing. Using AI to write is not only encouraged, but almost enforced. If you're an engineer, you already know how much your day-to-day involves using AI to write code. I think tech writing is inevitably meeting the same fate as coding — you can probably get 80-90% of the way there with an AI generated first draft.
However, that's only if you know what great output looks like. You still need a tech writer to monitor AI output and ensure quality standards. There's an understanding that comes with experience when you're specifically using LLMs to write content. The writing itself now extends to crafting prompts, writing system instructions for agents, creating reusable skills that enforce consistent voice and structure, and structuring context so models produce useful output. I argue the same skills that make someone good at documentation make them good at getting the most out of AI.
Using AI to generate drafts is only one piece of the puzzle, though; tech writers are becoming more like product managers. A great tech writer can multiply their output by validating AI generated content. The best tech writers think about docs as part of the product as a whole.
It may not be necessary to have a tech writer. But in my opinion, a tech writer more than makes up for their worth by strategizing the best way your users learn about the product. That human ownership gets your docs from 90% to 100% — and I think every user deserves 100% of your product.
Let's connect about possible opportunities or chat about writing.