5 ms·
The difference between a developer advocate and a developer evangelist is inbound vs outbound. Developer advocates are focused on helping address developers' p
by murtza 12y ago
The difference between a developer advocate and a developer evangelist is inbound vs outbound.
Developer advocates are focused on helping address developers' problems. Developer evangelists are focused on increasing product use and adoption.
That said, the responsibility of these positions mostly overlap. In my personal experience as a developer evangelist at Marketo, my day-to-day work has encompassed the function of both titles. My goal is to create a great developer experience [0] in order to drive platform adoption [1].
Anecdotally, I have noticed a shift towards the developer advocate title. At Facebook, Dropbox, and Twitter, the role is called this.
[0] http://murtza.org/creating-a-great-developer-experience/ http://murtza.org/creating-a-great-developer-experience/
[1] http://murtza.org/driving-the-api-adoption-funnel/ http://murtza.org/driving-the-api-adoption-funnel/
- timothya 12y ago> The difference between a developer advocate and a developer evangelist is inbound vs outbound. That's a great way of looking at it. There is definitely some overlap, but I think it's nice to have the mindset that they are on the external developers' side rather than just the company's side. And it works well I think - by helping out those developers, they can work towards better products and platforms, and increase adoption at the same time. Everyone wins.
- girvo 12y agoSmall web world. I just spent the last two weeks integrating Marketo into a website at work.
- _navaneethan 12y agoWhich category Microsoft will sit on? Evangelist or Advocates?
- aceperry 12y agoDefinitely evangelist, promoting the company product.