I fell into my first developer advocacy role.
While searching for roles, I stumbled upon an opening titled "Agency & Community Engineer" and the company was focused on WordPress & Drupal. With open-source PHP as the center of my engineering career, I was intrigued.
The job description was a little something like this:
Produce material and lead efforts that will attract, educate, and inspire developers by advocating for better development practices with company. That work includes blog posts, sample code, videos, webinars, conference presentations, documentation, real-time trainings, and more.
As someone who had a passion for mentoring developers, this role seemed like a dream. I noticed a connection of mine knew the hiring manager, so I reached out and asked about the role. He sent kind words about me over the hiring manager, and the rest was history.
I had no idea that developer advocacy and leading communities was even a career path. I had spent most of my career in agency and enterprise e-commerce focused on open-source PHP platforms. The idea of getting paid to mentor developers blew my mind and made my heart incredibly happy (it still does today).
Developer advocacy and building community came so naturally to me that it wasn't long before I landed my first promotion and had the chance to build a thriving developer community, a growth-driven external advocacy program, and even built a community team. I was living on cloud nine.
Most folks I speak to about developer advocacy think they're not qualified to be a developer advocate. They say things like "I don't have a big Twitter following" or "I have a fear of public speaking." My first developer advocate hire at Lacework doesn't even have Twitter.
I understand all the fears and apprehensions—they're valid. However, a great developer relations team has a diverse pool of advocates, each with their own passions and dreams.
I am currently in the midst of building an advocacy and community team. My first advocate hire is a backend software engineer with a strong desire to code most of her day. My next advocate hire will likely be more like I was in my advocacy role.
I had a stronger passion for thought leadership than my peers. Don't get me wrong, I still wrote code and built demos and SDK's, but when there was a chance to speak at an event, write a blog post, capture developer feedback, or have a call with a developer 1:1, I was eager to volunteer.
The thing about developer advocacy is that it can take many forms and depend on the company you're at. I spent 50% of my time facilitating technical training with customers 1:1 in one role. Each developer advocacy role is different—figure out what motivates you and find a role that compliments your motivations and passions.
If you're ready to start pursuing a career in developer advocacy, you can check out the Uncommon jobs board to get a feel for what different roles might look like. There are a number of places to look for roles as well in this post, Where to Look for DevRel jobs.
Join the Uncommon community to connect with peers in the space and exchange best practices.
This article was originally posted on Devocate, which joined the Common Room family in August 2022. For more developer relations insights and resources, check out the Common Room blog. Learn more about Common Room’s solution for DevRel teams if you're looking for an intelligent community growth platform to educate, empower, and enable your community.