{"id":2104992,"date":"2022-02-17T00:05:00","date_gmt":"2022-02-16T22:05:00","guid":{"rendered":"http:\/\/nhub.news\/?p=2104992"},"modified":"2022-02-17T06:04:16","modified_gmt":"2022-02-17T04:04:16","slug":"youre-doing-it-wrong-recruiting-a-devrel","status":"publish","type":"post","link":"http:\/\/nhub.news\/fr\/2022\/02\/youre-doing-it-wrong-recruiting-a-devrel\/","title":{"rendered":"You\u2019re Doing It Wrong \u2014 Recruiting a DevRel"},"content":{"rendered":"<p style=\"text-align: justify;\"><b>Hiring a developer relations\/advocate is difficult. It&rsquo;s even harder to be the first DevRel in the company. My colleagues share their experience in detail<\/b><br \/>\nJoin the DZone community and get the full member experience. The DevRel collective is a community where people in the developer relations field can chat and help each other out. But this post isn\u2019t about that group\u2026 We\u2019ll get to that. This is an article about you: the startup founder or manager who\u2019s trying to hire your first developer relations person. This article is here to help you by example. I\u2019m not the first to write about this problem. Taylor Barnett wrote a great piece on this as well. Be sure to check it out! But first, let\u2019s make sure we have the terminology right: Developer Relations is a field that encapsulates all the different roles that facilitate the communication between an organization and third-party developers. That can include a developer advocate (such as myself), a developer evangelist, community manager, and much more. But getting started is pretty hard. Wesley Faulkner started this by opening this thread on the DevRel collective community Slack: \u201cHey y\u2019all I need a temperature check. I\u2019m getting a lot of LinkedIn solicitations for \u2018first developer advocate\u2019 roles. Here\u2019s just a snippet of the last one I got: With that, we are looking for our first Developer Advocate* to create our Developer Relations strategy from scratch. There\u2019s no set playbook, but you\u2019ll thrive in this role if you\u2019re passionate about educating developers.\u201d His response to this was: \u201cThank you for reaching out, but I\u2019m not interested at this time. Hiring someone to execute and do strategy is really hard. Time and time again, I\u2019ve seen this go south in a hurry, and no one wins in that situation. If you review the job description, it is heavily biased towards action. With a first role, there\u2019s a lot to do, and without focus and direction, the results will not only seem scattered externally but internally as well. It\u2019s as if you wake up in a field and want to get out, so you bolt off in a direction. Then it feels like you\u2019re going nowhere, so you turn around and go in the opposite direction. All that work and time gets wasted.\u201d My suggestion is to create a solid strategy and direction before getting someone to execute it. You could even hire a contractor or consultant to help with that. Better yet, make that the first role you hire. You wouldn\u2019t open a restaurant with just servers on staff, would you? You would get a manager to make sure that all tasks are delegated responsibly. Why wouldn\u2019t you take that same approach with DevRel?\u201d I (Shai) am currently the first developer advocate at Lightrun, and I can very much empathize with those sentiments. A former boss of mine is running an open-source company without a DevRel person. He asked for my help, so I popped into a Zoom meeting with them. It was clear they felt uncomfortable asking this, but it\u2019s the obvious question: \u201cWhat do you do?\u201d I can answer this about my job, but I can\u2019t provide an answer for other developer advocates or developer relations. The reason is that our jobs vary too much and include a lot of flexibility. An open-source company that targets big data will have completely different needs from a close-source enterprise debugging tool. The job of a developer relations advocate in both companies can be completely different. As a result, a perfect candidate for the job at Company A might be a terrible candidate for the job at Company B. With Lightrun, our founders interviewed a lot of developer relations people. This didn\u2019t take off. Part of this is the huge demand we have in the market right now. We\u2019re getting a lot of solicitation over LinkedIn by just having that job title. But another part is the vagueness of our job descriptions. If I\u2019m considering a job, I\u2019d like to know that I\u2019ll be able to do it. I\u2019d like to know what it would require. Unfortunately, that\u2019s something the employer needs to define for the employee\u2026 Not the other way around. Lightrun solved this problem by hiring me. Since I was already a part of the team, I understood the product. I\u2019m a company founder and effectively did developer relations for 20+ years in one way or another (we just didn\u2019t call it that). Since I know what\u2019s needed and understand the company\/culture, I could draw up a plan and decide what needs to be done. When we grow this activity, additional DevRel staff can fit into the framework I\u2019m constructing here and improve it with their experience. Right now with the proverbial \u201cblank slate,\u201d I very much feel the words Wesley wrote about and can understand why people don\u2019t want to be the first developer relations person in a company. Most companies don\u2019t have an experienced person on staff already. But most have a technical founder. When reaching out to developers, a lot of the founders do this in an ad hoc way. You post to Reddit or set up a blog and try to get some developers to use the product. That\u2019s all great and could be the starting point for a developer relations role within the company. But the trick is to turn this into something that\u2019s more strategic and actionable. Are you hiring a developer relations person just to write blog posts? Where can that person contribute? What are reasonable KPIs? What would the day of a developer relations person at your company look like? What\u2019s the chain of command? Is marketing in charge or is it the CTO? If you can\u2019t answer these basic questions, you don\u2019t have the infrastructure in place to hire a developer relations person. You can hire the \u201cbest\u201d person out there and be disappointed because they won\u2019t know what to do. I know, a lot is thrown on the shoulders of founders, but if you\u2019re a B2D (business to developer) company, then you pretty much need to understand the role in depth. Otherwise, you\u2019ll have a hard time managing and evaluating the work of the developer relations person. Wesley\u2019s thread struck a serious nerve in the community with 63 responses. Here are some highlights, which I think are the perfect TLDR for this post: \u201cThe inevitable reaction in these situations,3 \u2013 6 months in, is either \u2018You\u2019ve gotten great results from your efforts, but we\u2019re not seeing the vision or the strategy part done. Maybe you\u2019re not the one to do that part.\u2019 Or, you focused on the strategy portion, so you get \u2018Nice execution on the strategy, but we\u2019re just not seeing the results on the ground. Maybe DevRel doesn\u2019t actually work.\u2019 It is an absolute strategy for failure.\u201d \u2014 David G. Simmons \u201cI\u2019ve seen a number of these first hires fail this summer and now the engineers, first advocates themselves, feel imposter syndrome and otherwise about DevRel. And it was the stakeholders\u2019 fault for not having their strategy known to their hire.\u201d \u2014 Tessa Kriesel \u201cThis is a well-articulated response with understandable examples. VP of Eng\/Mkt should do a lot of legwork in these small companies on that strategy piece BEFORE hiring the first DevRel.\u201d \u2014 Dewan Ahmed \u201cIt\u2019s been a different experience for me. As a first devrel at $CURJOB, I had a lot of existing trust with the founder\/exec team and executing on a couple of tactical things (docs, tutorials, forum) helped build some credibility. The main strategic goal when I was hired was \u2018get more pageviews,\u2019 though since then it has been refined since.\u201d \u201cWe\u2019ve been working toward a strategy, but one hard thing about a strategy at a small company is that it is difficult to formulate. It\u2019s hard to do internally (to make the time) and hard to know who to trust to come in and consult. It\u2019s hard to find the right fit (esp when you are still trying to do the tactical stuff at the same time).\u201d \u201cI doubt I would have had the same success without the deep trust I had with the founder.\u201d \u2014 Dan Moore Published at DZone with permission of Shai Almog, DZone MVB. See the original article here. Opinions expressed by DZone contributors are their own.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Hiring a developer relations\/advocate is difficult. It&rsquo;s even harder to be the first DevRel in the company. My colleagues share their experience in detail Join the DZone community and get the full member experience. The DevRel collective is a community where people in the developer relations field can chat and help each other out. But [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2104991,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[93],"tags":[],"_links":{"self":[{"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/posts\/2104992"}],"collection":[{"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/comments?post=2104992"}],"version-history":[{"count":0,"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/posts\/2104992\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/media\/2104991"}],"wp:attachment":[{"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/media?parent=2104992"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/categories?post=2104992"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/tags?post=2104992"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}