Skills that make the work valuable
- Task-based documentation
- Technical interviewing
- Example validation
- Information architecture
Build proof, not just a list
Create a quick-start guide and troubleshooting section for an open-source tool you can run locally. Test every instruction, document prerequisites, and show how feedback from a new user improved the final explanation.
How to price this work as a freelancer
Estimate documentation from audience, technical access, deliverable types, and required validation rather than word count alone. Include interviews, example testing, and review cycles. Release changes and unavailable subject experts can create repeated rework, so define version coverage and maintenance separately from initial publication.
Start with the income you need to replace
Required hourly rate = (target salary + benefits budget + annual business expenses) ÷ (annual billable hours × share of revenue retained after fees).
For illustration, $100/hour × 25 billable hours/week × 48 working weeks = $120,000 revenue. After $20,000 in business expenses, that leaves $100,000 profit before personal taxes. Replacing a $100,000 salary plus $15,000 in benefits under those assumptions takes $112.50/hour, with no percentage fees.
These are editable planning assumptions, not rates surveyed for technical writer work. Your personal taxes, location, contract terms, and workload still affect the comparison.
Employee or freelancer?
Working as an employee
Employment can provide direct access to engineers, release planning, and product environments. Check whether documentation is included in development schedules or consistently arrives after decisions and changes are already finalized.
Running a freelance business
Independent technical writing can reward deep expertise in a product category. You must secure test access and technical reviewers, and price maintenance carefully because accurate documentation changes whenever the underlying product does.
Where this career could take you
- 01Junior technical writer
- 02Developer documentation specialist
- 03Technical writing lead
An example path, with room for lateral moves or specialization. Progression depends on opportunities and demonstrated work; these steps do not imply a timetable or salary increase.
Try one small next step
Find an unclear setup procedure in a tool you already use, reproduce it, and draft a corrected guide. Ask a new user to follow it independently.