Hiring a developer relations team is hard. The pool of experienced people is small and the role requires an unusual mix of skills
Here are five things you should avoid if you’re hiring developer relations professionals.
Too many companies start the recruitment process without knowing what they want from their developer relations programme.
“Hey”, you might be thinking, “I’m hiring a devrel person to come create the strategy for me!”
If that’s the case, then you’ve already thought about it more than some hiring managers. Before you start recruiting, ask yourselves:
The answers are not a developer relations strategy but they will point towards the skills and seniority you require.
If you’re not sure what the answers should look like, seek help. Ask your peers in non-competing industries or hire a developer relations consultancy.
There’s a point at which interview questions and tasks turn into free work.
Ask yourself: are you gauging the candidate’s suitability or are you using them as a sounding board for your plan? How likely are you to go back to candidates with a, “we’re putting hiring on hold as we don’t quite know what we’re doing” type of response?
If you have a software engineering vacancy, hire a software engineer. If you want to do developer relations, hire a developer relations professional.
There’s a fallacy held by some that to do developer relations you need to be a supremely well known developer. That’s wrong for at least three reasons:
It’s hard enough to hire for developer relations roles as it is. Don’t throw ego and the wrong skills into the mix.
Building awareness, adoption and community for a developer-targeted product is usually a global task. It’s absolutely right that your strategy should focus on certain geographies but don’t get too tied up on where your devrel team lives.
Developer relations happens online and at events. Find the right people, establish remote-friendly working practices and give your team a reasonable travel budget.
The caveat is that you’ll need to work harder to integrate a remote devrel team with any office-bound engineering, marketing and product colleagues. That’s just table-stakes, though.
The people who excel as developer advocates, technical evangelists and community managers are creative and have a bias for action. They almost certainly run an event or an open source project or have some other side project.
You should celebrate that. It takes them, and your product, into places they wouldn’t reach otherwise and it gives them experience that they can feed back into their day job.
Don’t take the very characteristics that make a great devrel person and then quash them.
If you are hiring, it’s worth knowing that the small developer relations community is pretty tightly knit. News of your vacancy, and details such as compensation, will spread before your recruiter has finished their LinkedIn search.
Know what you’re looking for and then be honest and open about it. The developer relations community will help you. Not just with things like the devrel jobs board or events such as DevRelCon but also with personal introductions.
If you need help with your developer relations plan, speak to the developer relations consultancy Hoopy.
DevRelCon London speaker Tristan Sokol shares his ideas for making Stack Overflow a destination of choice for your community.
Convincing the company ‘suits’ to take APIs seriously as a commodity can be tricky – but get your strategy right, argues DevRelCon London speaker Mark Boyd, and the benefits could carry across your business.
Better documentation equals better developer experience – Adam Butler explains how his team at Nexmo are making this a reality.