For me the role of Developer Advocate is really defined in the title. It is about advocating for the developer experience with your product, both externally and internally. Previously at my company I was in Support helping solve issues for developer's. Now, I am taking the same customer centered mindset to make the developer experience better for those working with the Smartsheet API.
By working with the community I can find the pain points developers experience and bring that to the teams that can change that. I can also advise on best practices and create new materials for developers to learn what they need. Sometimes people experience issues working with an API because they aren't aware of a better way to do something and sometimes they have problems because of the way the API was built. I view my job as finding that out and doing what I can to help solve those problems.
As for resources, I would check out DevRel Weekly, Developer Avocados, and DevRel.net for more info. Also, this post with an interview with Mary Thengvall has some great stuff too.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi Conlin! Thanks for the question!
For me the role of Developer Advocate is really defined in the title. It is about advocating for the developer experience with your product, both externally and internally. Previously at my company I was in Support helping solve issues for developer's. Now, I am taking the same customer centered mindset to make the developer experience better for those working with the Smartsheet API.
By working with the community I can find the pain points developers experience and bring that to the teams that can change that. I can also advise on best practices and create new materials for developers to learn what they need. Sometimes people experience issues working with an API because they aren't aware of a better way to do something and sometimes they have problems because of the way the API was built. I view my job as finding that out and doing what I can to help solve those problems.
As for resources, I would check out DevRel Weekly, Developer Avocados, and DevRel.net for more info. Also, this post with an interview with Mary Thengvall has some great stuff too.