Developer Advocate vs Technical Writer: which is more exposed to AI?
36 points apart. These are not comparable risk profiles.
Technical Writer sits at 88% time-weighted AI exposure against 52% for Developer Advocate, a 36-point gap driven by the 66% of technical writer work time that current models can already substitute outright. Developer Advocate holds a larger human-critical core — 34% of the role's time sits in work like "build community relationships" that models score poorly on. The two sit in different families — Computer & Math and Arts & Design — so any move between them is a career change, not a lateral step.
Seven dimensions, side by side.
What actually creates the gap.
Technical Writers spend 66% of their time-weighted week on tasks a current model can produce end-to-end, against 32% for Developer Advocates. The single largest contributor is "write api reference documentation", graded at 92% and worth 22% of the role's time. That one task accounts for more of the gap than any difference in seniority, tooling, or industry.
- Repurpose content across channels86% · 6% time
- Write tutorials and blog posts84% · 10% time
- Draft documentation improvements82% · 8% time
- Produce sample code and demos78% · 8% time
- Build community relationships12% · 12% time
- Speak and connect at events15% · 14% time
- Represent the brand authentically18% · 2% time
- Write API reference documentation92% · 22% time
- Create release notes and changelogs91% · 12% time
- Draft user manuals and guides88% · 18% time
- Write onboarding and help content84% · 14% time
- Extract knowledge from subject-matter experts18% · 10% time
- Information architecture design32% · 12% time
Both roles lean on creative, cognitive, judgement — that is the part of your experience that travels intact. The real divide is social: Developer Advocates score 82 there against 48 for Technical Writers, a 34-point spread. That is the gap you would actually have to close.
| DIMENSION | DEVELOPER ADVOCATE | TECHNICAL WRITER |
|---|---|---|
| Social | 82 | 48 |
| Procedural | 52 | 84 |
| Cognitive | 62 | 78 |
Technical Writer appears in our dataset as a mapped adjacent career for Developer Advocates: the move raises exposure by 36 points, landing at 88%. Switch difficulty reads moderate — capability profiles are 20 points apart on average.
Score your own exposure in 8 questions →Common questions.
Is Developer Advocate or Technical Writer more at risk from AI?
Technical Writer. It scores 88% time-weighted AI exposure against 52% for Developer Advocate — a 36-point gap. 66% of technical writer work time is already fully substitutable by current models, versus 32% for Developer Advocates.
Which pays more, Developer Advocate or Technical Writer?
Developer Advocate, by roughly $47k at the median ($125k versus $78k). Note that the higher-paying role here is also the less AI-exposed one, which matters if you are weighing pay against durability.
Can a developer advocate switch to being a technical writer?
Technical Writer appears in our dataset as a mapped adjacent career for Developer Advocates: the move raises exposure by 36 points, landing at 88%. Switch difficulty reads moderate — capability profiles are 20 points apart on average.
Which role is growing faster, Developer Advocate or Technical Writer?
Developer Advocate, at 10% projected ten-year growth versus 4% — a 6-point difference. Growth and AI exposure are separate signals: a role can grow in headcount while the content of the work is substantially rewritten.