Remote Head of Developer Relations
grabjobsReno (NV)
Remote Head of Developer Relations
Posted 45 days ago
grabjobsReno (NV)
SENIORITY
Manager
About the role
About The Role:
You'll be the public face and technical voice of Tenki, shaping how developers understand and define AI-native software development. This is not a traditional content role — we're looking for a developer who also happens to be a phenomenal communicator. Someone who has shipped real production code, can hold their own in technical conversations, and can translate that experience into clear, compelling narratives that resonate with engineers. Through your work, you'll help define how Tenki redefines the technical ecosystem. This is a fully remote role, but you are required to be based in San Francisco (CA).At Tenki, you will own how developers discover, understand, and trust what we're building: Build in public using Tenki: weekly livestream running Tenki against a real OSS bug; monthly write-up of what broke and why; public benchmarks against peer tools; teardown threads on X when a release ships; OSS PRs where Tenki was the assistant, with the diff and prompt history attached; written for engineers, not marketing. Ship a consistent stream of high-signal content across X, YouTube, long-form posts, podcasts, and conference stages Develop sharp, opinionated points of view on AI-native code review, developer infrastructure, and the agent-era engineering workflow, and defend them publicly Grow and engage a real developer community around Tenki. Not just a marketing list, an actual community of engineers who care about the same problems we doPartner closely with engineering, product, and design to shape onboarding, documentation, and the first-five-minutes experience for new users Show up where developers actually live: GitHub threads, technical Discords, hallway tracks at conferences, late-night debug sessions. Not vendor booths or pay-to-play panels Bring product feedback back inside, loudly. You'll be the closest person on the team to how developers actually use what we ship, and that signal needs to shape the roadmap
About You:
- We're hiring for impact, and that comes from passion x reach. Up to 2 years of doing this is plenty, but in that time your work should have reached engineers and changed how they think. Posts that got argued with. Repos people forked. Threads people quoted. Show us evidence the work landed.
- Not the LinkedIn-influencer energy. The "let me show you the actual code" energy.
- You've shipped real production code. You can hold your own in a technical conversation about model latency, static analysis, or distributed systems without faking it.
- You can take complex technical ideas and turn them into narratives engineers actually read to the end. You know the difference between writing for developers and writing at them.
- You have sharp opinions about where AI coding agents and developer tooling are going, and you're willing to defend them when smart people push back.
- You don't wait for permission. You write the post, book the podcast, file the PR on the docs, and move.
- You can set direction in an early-stage environment where priorities shift and clarity must be created, not awaited.
- How we use AI in our hiring process
- We use AI tools to support certain parts of our hiring process, and we believe in being transparent about how they're used.
- During your application, AI may assist in reviewing CVs, qualifications, and assignments by providing additional insights, but it does not make decisions, every application is evaluated at each step by a member of our hiring team.
- We also use AI to transcribe interviews so our team can stay focused on the conversation rather than note-taking. Any voice recordings are automatically deleted within 15 days.
- In addition, AI helps us keep candidates informed about their application status and helps us understand how our process is working so we can improve it over time.
In all cases, AI is used to support efficiency and consistency, not to replace human judgment. If you have any questions about how we use these tools or your data, or if you would prefer to opt out of any of these features, please include them in the dedicated section of the application form, and we'll follow up accordingly.
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.