Os Papéis · Quem ensina
Developer advocate
Escrito a partir de fontes publicadas
The engineer employed by a vendor whose work serves the people who use its technology. Advocacy sits inside developer relations, the broader function covering community, events, experience and content, and the advocate is its technical face: writing sample code, building reference integrations, answering in public channels, and carrying what the community says back into product and engineering.
De quem recebe
- The developer community
- Questions, complaints and the workarounds they invented without being asked.
- Product and engineering
- What is coming, and the reasoning behind what is already there.
- Support
- The recurring case, which is community difficulty already quantified.
A quem serve
- External developers
- A route to making the product work, and somebody who answers.
- Product management
- Field evidence with the vocabulary of the people who hit the problem.
- The company
- Adoption built on capability rather than on persuasion.
Do que o trabalho depende
The role is paid by one side and useful to the other, and the value depends entirely on the community believing the second part. That belief is built by the unglamorous half: filing the bug, saying plainly where the product falls short, and returning later with what changed. Advocates who do that are trusted and their companies benefit; the internal half of the job is what makes the external half true, which is why measuring only outbound activity produces a function that gradually stops working.