Head of Developer Relations

Luxor Technology Corporation

1d • Remote

About The Position

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 do
Partner 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

Requirements

• 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.

Responsibilities

• 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 do
• Partner 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

What This Job Offers

• Job Type: Full-time
• Career Level: Senior
• Education Level: No Education Listed