Roles
Tech stack
Location
San Francisco, CA
Work setup
- Employment
- full-time
- Level
- Senior
- Remote policy
- Remote (SF-based required for event assistance)
- Remote scope
- timezone-limited
- Timezones
- SF-based required for event assistance
- Travel
- Show up at SF meetups, hackathons, and developer events
Role details
Responsibilities
- Show up at SF meetups, hackathons, and developer events — be the person engineers meet first when they hear about Tenki
- Work side by side with engineering and product teams so you can speak honestly about how things work — and make sure that developer feedback shapes the roadmap
- Run weekly livestreams running Tenki against real OSS bugs
- Write teardown threads on X when a release ships
- Publish public benchmarks and honest post-mortems
- 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
- Real engineering experience
- Built a public technical audience (e.g., GitHub with stars, a blog running for a couple years, a YouTube channel engineers watch, or X threads people argue with)
- Know what the compute/agent sandbox space involves
Application
Apply via Ashby: https://jobs.ashbyhq.com/luxor/eba7430f-c1f5-4d0b-933a-1b9950ead0b7?utm_source=YC
- Portfolio
- unclear
- GitHub
- preferred
- Cover letter
- unclear
- Apply flow
- ats
Company context
- Product
- Tenki — Luxor's compute platform
- Industry
- unclear
- HQ
- San Francisco, CA
- Size
- hundreds of teams
Description
We’re building Tenki — Luxor's compute platform. It started as internal runner infrastructure, now powers code-review agents and isolated agent sandboxes (ADE), and the roadmap extends to agent workflows, background automation, and CPU/GPU compute. If you know what that space involves, you’ll understand why our bar is high. We need someone with real engineering experience who has also built a public technical audience. A GitHub with stars, a blog that’s been running for a couple years, a YouTube channel engineers watch, or X threads people argue with. You don’t need all of them, but you need something real to show. What you’ll actually be doing: - Show up at SF meetups, hackathons, and developer events — be the person engineers meet first when they hear about Tenki - Working side by side with engineering and product teams so you can speak honestly about how things work — and making sure that developer feedback shapes the roadmap - Weekly livestreams running Tenki against real OSS bugs - Teardown threads on X when a release ships - Public benchmarks and honest post-mortems Structure: You’d be the first person in this seat. Small, technical team. No playbook yet — full ownership. We want to grow with and because of you.
Similar jobs
-
Loading similar jobs...