Head of Developer Experience

About the role

Developer experience at Sentry spans four areas: the integration and developer platform, docs, community, and DevRel. The DevEx team is responsible for how developers first encounter Sentry, how they learn to use it, and how they build on top of it - from SDK configuration docs to the Discord community to the integrations ecosystem. This role owns all of it. We recently had our Head of DevEx depart, and we're looking for a senior leader to step in with real ownership and real scope. You'll sit in Marketing, partner closely with EPD, and have direct influence over both the product surface (the integration platform) and the team responsible for developer education, docs, and community. In this role you will Own strategy and execution for Sentry's integration ecosystem and developer platform APIs - working closely with EPD to define the developer-facing surface and ensure building on Sentry is a genuinely good experience Lead the documentation function across SDK configuration docs, API reference, and tutorials - the places where developer activation actually happens or doesn't Connect docs to the product experience: logged-in state, contextual guidance, health checks, and surfacing adoption gaps in-context, in partnership with EPD and the Docs platform team Own Sentry's developer community across Discord, social, and events, and build the team and processes that turn engagement into measurable outcomes: signups, adoption, support deflection Build and deliver the content and education programs - workshops, deep dives, fireside chats - that teach developers tracing, debugging, and how to actually use Sentry's full product surface Build relationships with the builders, toolmakers, and platform partners who extend Sentry's reach You'll love this job if you You've shipped code and can tell when a code sample is wrong without running it - your technical credibility is real, and developers will know it You want to own a product surface, not just produce content about it You've built or scaled a developer community and can point to what actually moved because of it You care about documentation as a product, not a checkbox - you have opinions about what good looks like and will hold a team to that standard You're comfortable operating with ambiguity and resetting scope - you don't need to be told what to prioritize, and you're skeptical of complexity for its own sake