Technical Writer

Most days mix interviewing engineers, learning the product, and writing — sitting in on design reviews, building doc structure, writing first drafts, getting technical review, refining for the actual user, and managing the docs site or knowledge base. You're often working in software, hardware, medical device, or industrial settings, and audience — developer, end user, internal employee, regulatory — shapes everything.

What tends to be harder than people expect is how much of the role is influence and prioritization. Engineers don't always have time to review docs, product changes ship faster than docs update, and tooling (Markdown, Sphinx, Madcap, GitBook, Docusaurus) varies widely. API docs vs end-user docs vs regulatory docs are different specialties with different rates.

People who tend to thrive here are curious, fluent in writing and tech both, comfortable with iteration, and quietly committed to the user finding what they need. If you want pure creative writing, this is more applied. If you like the leverage of making complex things legible to the people who need to use them, the role offers strong remote opportunities, durable demand, and a path into product, developer relations, or content strategy.