Personal branding for developer advocates
You are paid by a vendor to be trusted by an audience that distrusts vendors, and both sides know it. The role's credibility problem is structural rather than personal.
You are the conflict of interest
This is a genuinely awkward position that no other profession here occupies. Your salary comes from a company whose product you discuss to people who have learned to discount anything a company says about its product. The audience is not being unfair: your incentive really is misaligned. The only resolution is visible independence, which means publicly saying when the product is the wrong tool, discussing competitors accurately, and being useful about things that sell nothing. Advocates who never criticise their employer are read exactly as accurately as they deserve.
What the generator produced for a developer advocates brief.
Captured output, not a mock. It came back from the same engine behind the free persona generator, run against the brief below, and the engine is deterministic so you can reproduce it. Kit Oyelaran is an illustrative name, not a customer.
- Offer
- developer relations
- Tone
- technical, generous, unmarketed
- Audience
- engineers who distrust vendor content
- Technical
- Generous
- Unmarketed
- Warm
- Supportive
Archetype: The Caregiver
Tagline: Technical. Made real.
- Name engineers who distrust vendor content directly, in the words they would use about themselves.
- Lead with the outcome of developer relations, then explain how it works.
- Leads with the reader's wellbeing.
If you are one of the engineers who distrust vendor content carrying this alone, you do not have to. Developer relations is the part we take off your plate.
Generate one for your own brief → No signup for the first output.
The mistake most people in this job make
Most developer advocacy is product content with a friendlier voice. The audience's filter is tuned precisely for that and the friendliness makes it more obvious, not less.
What to actually post about
- A case where your product is the wrong choice
- Something technical that sells nothing
- An honest comparison including where you lose
Who should skip this entirely.
An advocate whose remit is purely documentation and enablement. This is about external credibility, which that role does not need.