FieldsTechnical Writer
Technical Writer
Turn complex systems into documentation people actually use.
Career
What you learn
- Understanding a system well enough to explain it honestly
- Documentation organised around tasks rather than around features
- Developer documentation where someone succeeds in their first five minutes
- Documentation kept true as the product keeps changing
What you will understand
- Documentation succeeds when the reader does, not when it is accurate
- Stale documentation is worse than none, because it is trusted
- The four documentation types, and why mixing them serves none of them
- The curse of knowledge, and writing against your own expertise
How you will practice
- Use the thing yourself and verify every step by performing it
- Watch a stranger complete the task using only what you wrote
- Convert a feature shaped documentation set into a task shaped one
What you will build
- A developer documentation set with runnable examples that fail the build when broken
- A documentation test where a real reader succeeded and the success rate is reported honestly
The proof you build
Evidence that you can produce documentation people succeed with and keep it true as the product changes.
Your work is observed with your consent, scored for independence and assistance, and turned into proof that carries a confidence level. The career path can reach a high-assurance credential, anchored by a scored capstone.
What is not live yet
The desktop app, consent-based observation, scoring, and credentials are in development. Nothing here implies they are live yet.
Get early access