About the Developer Relations role at Hash

"Access to developers is a bigger threat to business success than access to capital" - according to Stripe

Companies across the globe have realized that money by itself can't solve some of their deepest and longest-lasting tech issues. In order to do that you will also need a bunch of people that understand the technology provided by the current times in order to implement a long-lasting real-life solution. While implementing these solutions, software development decisions involve analyzing trade-offs that comes both from the business needs and the current technology used by the company. And the less skilled your tech team is, the harder it is to keep the software updated with the business needs.

A "skilled tech team" is composed by many factors, not only technical skills. Since in a work routine you have to interact with different people, the quality of these interactions will impact in many aspects the technical work. Therefore, the company should be responsible for the overall health of the interactions between individuals and teams in order to maintain and improve the context in which people take work-related decisions. Improving the scenario here means hiring people that adhere to good work culture,  as well as listening to workers and propose changes where interactions seem to fail constantly. Thinking about this complex environmental issue we have created a "Developer Relations" role at Hash, which I’m in charge of, in order to tackle both the internal and external part of this issue.

The internal side deals with our internal community management: How good are the interactions between our tech teams? Are new/current people feeling safe to propose changes in our collective tech improvement meeting? These questions and others stimulates a line of  work that involves listening to people and proposing structural changes rather than reactive ones.

The external side deals with analyzing the output of Hash external content thinking with a tech mindset. Since our product is deeply technological, our marketing content can't be something averse to engineers. It is common to have companies pumping content which is aimed for developers without considering the engineers point of view and that completely backfires. This can only be avoided by involving the engineering team in the content production pipeline, which is led by the developer relations.

I am truly excited with the challenges that are  coming, I've just started this role and I hope to come back in the future writing about what we've learned trying to solve some of the issues listed. If you are also interested in solving problems that  are revolutionizing the way that companies deal with payments by building a new payments infrastructure, check our current open roles at our career page: Greenhouse Board