Building Developer Relations Teams With Trag ![rw-book-cover](https://wsrv.nl/?url=https%3A%2F%2Fimages.transistor.fm%2Ffile%2Ftransistor%2Fimages%2Fshow%2F27278%2Ffull_1655766950-artwork.jpg&w=100&h=100) ## Metadata - Author: [[Build and Learn]] - Full Title: Building Developer Relations Teams With Trag - Category: #podcasts - URL: https://share.snipd.com/episode/ea4b9b99-2589-4a17-b82f-4f0ee6a6bf37 ## Document Notes ## Highlights - Tradeoffs of Dev Rel Teams • Dev rel teams can be under different departments, depending on the company. • Dev rel teams can have different focuses, depending on the department they are under. • Dev rel teams can be important for the developer experience. Transcript: Speaker 2 Is this is your new team? How is it organized? And also like, are you under marketing? Are you under engineering? And yeah, like I think there's a lot of benefits and trade offs depending on like where a dev rel team lands. And so yeah, I'm curious where your current setup is. And then maybe if you could speak to some of the trade offs of like where you put dev rel and like how that impacts things. And in some companies, like you report directly to the CEO, whereas like other places you might be buried under some sales or marketing team. Speaker 1 Yeah, it's it's it's such a like a hot button topic because I mean, folks have their, you know, their, I would say two things. People have their opinions on what dev dev advocates are. Like for whatever good or bad experience they've had with a dev advocate, like that is pretty much set in stone unless they're convinced otherwise in a different experience later. And I also think dev rel in marketing versus so I have, I've built dev rel teams under the CTO. Yeah, directly under the CEO. I've been directly under partnerships and business development. I've been under marketing and it's stripe. Obviously it was directly under engineering. And so it's kind of wild like your tactics in your focus shifts a little. But I do think you're still really fighting bit on behalf of the developer experience. And you're acting as developer zero. ([Time 0:17:19](https://share.snipd.com/snip/10957279-5429-4796-abcf-01c51b3c1ce4)) - Note: devrel - Tags: devrel - How to Manage a Dev Advocate • Dev advocacy can be many different things, including helping to improve SDKs and ensuring that the code quality is high. • It is important to have the skills to be an engineer in order to be a good dev advocate. Transcript: Speaker 3 Dev advocacy can be so many different things, even in one team, right? You have SDKs, which might be more someone's rolling up their sleeves and figuring out how do we generate these better? How do we make sure like, oh, our PHP one's not as good as our Ruby one, we're getting feedback, you're working with product to return that feedback to the team that's building those SDKs, You're helping people with contents, you've doing all these things. I think we kind of touched on this in our episode with Lindsey Barrett about technical support and technical support managers. And there's this you kind of touched on this as well of worrying about losing their engineering chops or maybe even I'll just say dev advocacy almost seeing as like less than being an Engineer when really, you know, I think there's a perception of that when really the job is just so different. It's just a difference job with different skills and you need to be able to do some of that engineering. ([Time 0:27:52](https://share.snipd.com/snip/bb74f89b-f68c-40b5-bc66-668f8f92a415)) - Note: devrel - Tags: devrel