Developer Advocate vs. Developer Relations Leader: Who to Hire First  [[3. Resources/Readwise/Full Document Contents/Articles/Developer Advocate vs. Developer Relations Leader Who to Hire First|Full Document Contents]] ## Document Notes Abstract: Founders and executives often struggle to determine the best title for their first DevRel hire - a developer advocate or developer relations leader. This article provides insight into how to decide which role to hire first, by looking at the different skill sets required for each role. It also provides information about the qualifications needed for a successful hire for either role, and outlines the importance of having the right strategy and processes in place for success. Finally, the article offers advice on how to best utilize user feedback to improve your product. 1. What are the most important traits of a successful developer advocate? 2. What strategies should I consider when setting up a successful developer relations program? 3. What is the role of a developer relations leader in a business context? This article discusses the question of whether to hire a developer advocate or a developer relations leader first. The article outlines the skill sets of each role and suggests that the right hire will depend on whether the organization has the right strategies and processes in place for success. It also suggests that a developer advocate should have strong problem solving and customer service skills, be able to present and solve complex problems easily, and enjoy networking and building relationships. The article concludes by recommending that organizations should do what is best for their team in terms of the hire that they make. > [!note]+ Document Notes > Abstract: > Founders and executives often struggle to determine the best title for their first DevRel hire - a developer advocate or developer relations leader. This article provides insight into how to decide which role to hire first, by looking at the different skill sets required for each role. It also provides information about the qualifications needed for a successful hire for either role, and outlines the importance of having the right strategy and processes in place for success. Finally, the article offers advice on how to best utilize user feedback to improve your product. > > 1. What are the most important traits of a successful developer advocate? > 2. What strategies should I consider when setting up a successful developer relations program? > 3. What is the role of a developer relations leader in a business context? > > This article discusses the question of whether to hire a developer advocate or a developer relations leader first. The article outlines the skill sets of each role and suggests that the right hire will depend on whether the organization has the right strategies and processes in place for success. It also suggests that a developer advocate should have strong problem solving and customer service skills, be able to present and solve complex problems easily, and enjoy networking and building relationships. The article concludes by recommending that organizations should do what is best for their team in terms of the hire that they make. ## Highlights - Developer advocate skill set • Relates to your developer audience • Knack for problem-solving and customer service • Desire to help other developers • Ability to be able to present & solve complex problems easily • Willingness to speak publicly or a comfort level with presenting technical topics • Solid technical writer — or ability to identify the details needed for an insightful documentation piece • Experienced developer in the areas that matter to your users • Enjoys networking and building solid relationships that matter ([View Highlight](https://read.readwise.io/read/01gwwx8aks1ec4acve8k4fxrxg)) - Tags: developer advocate - Developer relations leader skill set • Understands the wider developer ecosystem and how your product aligns • Strategizes your business & product goals alongside their developer audiences goals to define the best results • Understands developers, and not just because they are one, but because they know how they think & operate—they've "attracted" them before • Clearly defines developer audiences & their motivation • Builds strategy for scaled developer adoption through developer advocacy • Leads teams of developer advocates, community managers and developer support contributors • Understands when a goal needs a developer advocate, vs a tech writer, vs a community manager (or all) • Understands business & technology, not just one or the other • Understands how to best leverage user feedback to improve your product ([View Highlight](https://read.readwise.io/read/01gwwx9372mnc6hq3gh3b88z5j)) - Tags: devrel