In this episode of Community Pulse, Jason, PJ, and Mary talk to Rain Leander and Sherrie Rohde about their role as Community Managers for open source projects and how this differs from what’s now considered Developer Relations.

Working with a specific community is great, but what happens when it’s time to change companies? Do you bring your community with you? Do you need to start over in a new community? What does it mean for your “personal brand”? Jason and PJ talk about all of these topics and more with this month’s guests, Alyss Noland and Joel Lord.

Developer Advocate. Community Engineer. Developer Evangelist. Community Manager. Technical Writer. All these are job titles in DevRel, but what do they mean, and what do people think we do based on our titles? Jason, Mary, and PJ are joined by Bear Douglas, Director of Developer Relations at Slack, and Jeremy Meiss, Director of Community at Solace, to chat about the various roles within DevRel and what makes them all unique. Is it really all in the name?

As Developer Relations becomes more mainstream, the understanding of what makes someone qualified to be a Developer Relations professional is getting cloudy. Do you have to have a technical background? And if so, does that mean that you’ve held a “Software Engineer” title? Or simply that you’ve taken the time to understand the technical pieces of your product? Jason, Mary, and PJ are joined by Karissa Peth, Sr. Developer Relations Program Manager at Microsoft, and Matty Stratton, DevOps Advocate at PagerDuty, as they dig into the nuances of the various Developer Relations career paths.

Defining Developer Relations is a difficult thing to do. So how do you know what to expect when you transition into Community & DevRel? This month, PJ and Mary chat with Emily Freeman and Chloe Condon about how their initial experience has been and what they'd do differently if they had a choice.