Career guide
Technical writing: an underrated tech career for strong writers
Technical writers earn $80k–$130k creating documentation, API guides, and developer content for tech companies. Writers with domain knowledge and clear communication skills are well-positioned for this role.
What technical writers actually do
Technical writers create documentation that helps people use products and technology. At software companies, they work closely with product and engineering teams to translate complex functionality into clear language. The outputs include:
- User guides and help centers
- API documentation for developers
- Internal process documentation
- Release notes
- Onboarding content
- Video scripts
The spectrum of technical writing roles
Technical writing is not a single job. These four roles require different skill mixes and offer different career paths.
Documentation specialist
Most common entry pointWrites and maintains product documentation in a CMS or help center (Zendesk, Intercom, Confluence). The most accessible path for writers transitioning from non-tech backgrounds.
Developer advocate / developer documentation writer
Higher technical depthCreates API documentation, tutorials, and developer guides. Requires more technical depth — familiarity with APIs, developer workflows, and code samples. Commands the highest salaries in the field.
UX writer / content designer
UX-adjacentWrites the microcopy inside software — button labels, error messages, onboarding flows. More UX-adjacent than documentation. Often sits within design teams.
Technical content marketer
Marketing-adjacentCreates technical blog posts, case studies, and whitepapers for developer audiences. Bridges marketing and technical writing — good for writers who want to stay closer to content strategy.
Required skills
Most of these can be built after the career change. The writing foundation is what companies find hardest to teach.
Strong writing
The obvious one. Precise, clear, and structured. This is where career changers from journalism, academia, and marketing have a real head start.
Technical literacy
You do not need to code, but you need to understand how software works, read basic code, and follow technical workflows. Most technical writers build this on the job.
Docs-as-code tooling
Many developer documentation teams use Markdown, static site generators (Docusaurus, GitBook), and Git. These are learnable skills — a weekend of practice covers the basics.
Domain expertise
Technical writers with specialized knowledge (healthcare, finance, cybersecurity, developer tools) are more valuable than generalists. Your prior career is an asset here.
The portfolio that opens doors
Technical writing is a portfolio-driven field. Without prior job titles, your samples are your credentials. These four moves build a credible portfolio from scratch.
1Contribute to open-source docs
Find a project on GitHub with poor documentation and improve it. Many maintainers welcome this.
2Write an API tutorial
Pick a public API (Stripe, Twilio, any weather API) and write a clear getting-started guide for a developer audience.
3Rewrite an onboarding guide
Take a real product's onboarding documentation and rewrite it to be clearer. Compare the before and after.
4Publish publicly
Put your portfolio on a personal site or GitHub Pages. Hiring managers want to see examples, not descriptions of examples.
Salary and demand
Good technical writers are scarce relative to demand at most software companies. The field rewards specialization — the more technical the role, the higher the pay.
Documentation specialist$70k–$110k
Developer advocate / API documentation writer$100k–$150k
High demand — good technical writers are scarce relative to demand at most software companies. Writers who combine domain knowledge with clear communication skills are particularly valued.
Explore more
See all tech career paths
Technical writing is one path into tech. Explore the full landscape of roles available to career changers — from product management to data to UX.
Explore tech career paths