Developer Advocate vs Software Engineer: which is more exposed to AI?
A 15-point gap separates these roles — Developer Advocate is the more defensible seat.
Software Engineer sits at 67% time-weighted AI exposure against 52% for Developer Advocate, a 15-point gap driven by the 32% of software engineer 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. Both roles sit inside Computer & Math, so the exposure difference reflects task design rather than a change of field.
Seven dimensions, side by side.
What actually creates the gap.
Both roles hand a similar slice of the week to substitutable work — 32% for Developer Advocates, 32% for Software Engineers — but it is different work. Developer Advocate exposure concentrates in "repurpose content across channels"; Software Engineer exposure concentrates in "write boilerplate & crud code". Two roles can share a score and face completely different disruption timelines.
- 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 boilerplate & CRUD code92% · 14% time
- Generate unit tests from specs88% · 8% time
- Author documentation85% · 6% time
- Translate code between languages81% · 4% time
- Mentor junior engineers11% · 3% time
- Negotiate scope with stakeholders14% · 5% time
- Triage production incidents22% · 4% time
Both roles lean on cognitive, creative — that is the part of your experience that travels intact. The real divide is social: Developer Advocates score 82 there against 32 for Software Engineers, a 50-point spread. That is the gap you would actually have to close.
| DIMENSION | DEVELOPER ADVOCATE | SOFTWARE ENGINEER |
|---|---|---|
| Social | 82 | 32 |
| Procedural | 52 | 84 |
| Judgement | 58 | 41 |
Software Engineer appears in our dataset as a mapped adjacent career for Developer Advocates: the move raises exposure by 15 points, landing at 67%. Switch difficulty reads moderate — capability profiles are 26 points apart on average and both sit in the same family.
Score your own exposure in 8 questions →Common questions.
Is Developer Advocate or Software Engineer more at risk from AI?
Software Engineer. It scores 67% time-weighted AI exposure against 52% for Developer Advocate — a 15-point gap. 32% of software engineer work time is already fully substitutable by current models, versus 32% for Developer Advocates.
Which pays more, Developer Advocate or Software Engineer?
Software Engineer, by roughly $7k at the median ($132k versus $125k). Note that the higher-paying role here is also the more AI-exposed one, which matters if you are weighing pay against durability.
Can a developer advocate switch to being a software engineer?
Software Engineer appears in our dataset as a mapped adjacent career for Developer Advocates: the move raises exposure by 15 points, landing at 67%. Switch difficulty reads moderate — capability profiles are 26 points apart on average and both sit in the same family.
Which role is growing faster, Developer Advocate or Software Engineer?
Software Engineer, at 17% projected ten-year growth versus 10% — a 7-point difference. Growth and AI exposure are separate signals: a role can grow in headcount while the content of the work is substantially rewritten.