Skills for Managing your Documentation Team
summary
Hiring feedback from application number 52 reveals a concrete mismatch: managers treated tech writer and developer roles as discrete while the candidate’s schema shows overlap from a six‑week JavaScript course and hands‑on Sphinx/Markdown work. Advice: track specific words teams use (importing libraries, split functions), measure enthusiasm as a proxy for motivation, and assess transferable tooling (proprietary toolchains vs Sphinx). A working JavaScript recreation of the Letters and Numbers letters game (nine letters, 30 seconds) proves the approach and prevents physical tile mishaps.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:10Overview
- 1:40Story 1 Interview 1
- 5:54Story 1 Reflection
- 6:25Story 1 Background
- 7:29Why is it important
- 8:38The latest game
- 10:26Why
- 12:02Enthusiasm
- 12:49Motivation
- 13:29Language
- 14:41Summary
related talks
45mHow I convinced my boss to build our docs team
30mEquipping your team to support junior developers
39mBeyond Words: Strategies for Leveling Up Your Tech Writing Career
44mFrom Me to Us: Building a docs team from the ground up
25mInterviewing and hiring technical writers: the Siberian way
38mSeven habits of increasingly technical technical writers
27mInterviewing a Technical Writer Candidate
35mEngage or Die: Four Techniques for Writing Indispensible Docs