ClickHouse · posted · checked
Head of Developer Relations
$196k – $300kOn-site · Atlanta, Austin, Boston, Chicago, Denver, Los Angeles, New York and San FranciscoManager
Who can apply
On-site · Atlanta, Austin, Boston, Chicago, Denver, Los Angeles, New York and San Francisco
Location: Atlanta / Austin / Boston / Charlotte / Chicago / Columbus / Dallas / Denver / Detroit / Houston / Los Angeles / Minneapolis / Nashville / New York / Phoenix / San Francisco / United States
ClickHouse started as an open-source project that developers picked up on their own, told each other about, and built companies on. That community is still the reason most people first hear of us, and it is why ClickHouse Cloud fills with new users every day. As the database becomes a platform for real-time analytics, data warehousing, observability, and AI workloads, the community has more to learn from us and more to teach us than ever. Developer relations is how we hold up our end of that relationship.
As Head of Developer Relations, you’ll own how developers discover ClickHouse, get productive on it, and bring others along: the developer experience, the technical content that teaches it, the channels where developers find it, and the community that carries it. You’ll lead our global team of developer advocates and give the function the goals, systems, and investment of a core growth channel. You’ll partner closely with product marketing engineers, field marketing in every region, and product and engineering, and you’ll inherit a strong, globally distributed team and a community that has been generous with us for years. If you believe developer relations starts with helping people, that trust is the only thing that compounds, and that the work should be measured like any other growth investment, this is a rare seat.
WHAT YOU WILL BE DOING
Lead, coach, and grow a globally distributed team of developer advocates, and set ClickHouse’s long-term developer and community strategy with marketing, product, and engineering leadership, turned into a multi-year plan with headcount, budget, and investment priorities
Own the developer experience from the outside in: track time to first query and getting-started completion, run friction logs on the onboarding path and docs, and own the feedback loop into product and engineering on what developers are building, where they get stuck, and what they want next
Own the Developer Relations budget and represent the function to customers, partners, and the open-source community, on stage and on a podcast
Set targets across the whole function: community growth and engagement on Slack, Reddit, GitHub, YouTube, and your advocates’ own platforms, developer-experience measures, and content and channel reach, and report on them like any growth channel
Build the champions program into a real force, with clear tracks for customers, open-source users, and independent voices, so the community grows the community