Luxor Tech is building Tenki Cloud, a compute platform for agent sandboxes, workflows, and general CPU/GPU compute, initially grown from internal runner infrastructure. They are hiring a Head of Developer Relations to build a public technical audience and drive adoption, requiring a strong engineering background and proven public presence.
What they want, where you stand, and the exact résumé edits to qualify.
Biggest lever: Lack of an established public technical presence and direct Developer Relations experience.
A starter prompt for Claude Code, what you'll need, and how to reach them.
You are an expert full-stack developer. Create a secure, isolated code execution sandbox service (an MVP of 'Tenki Cloud') using Next.js 16 App Router, React 19, Tailwind v4, and Neon Postgres on Vercel. The service should allow users to submit Python code snippets and execute them in a containerized environment, returning the output. Focus on the core functionality for secure execution and basic API. For the MVP, assume a single user and no UI for submission, just an API endpoint.
Here's the plan:
1. **Project Setup**: Initialize a Next.js 16 project. Configure environment variables for any necessary API keys (e.g., for container orchestration if using a third-party, though for MVP we'll mock or use a local Docker). Set up Tailwind CSS.
2. **API Endpoint (`/api/execute`)**: Create a POST API endpoint that accepts a JSON payload with a `code` string (Python). This endpoint will be responsible for sending the code to the execution environment.
3. **Secure Execution Core (Mock/Container Integration)**: For the MVP, create a backend function that simulates secure execution. Ideally, this would involve spinning up a Docker container, executing the Python code, capturing stdout/stderr, and cleaning up. Since direct Docker orchestration on Vercel is complex, mock the container interaction for now, focusing on the API interface. If time permits, provide a local `docker-compose.yml` for actual containerized execution outside Vercel, and a placeholder `exec_code_in_container.py` script.
4. **Database (Neon Postgres)**: Store basic execution logs (timestamp, input code, output, status) in a Neon Postgres database. Define a simple `executions` table schema.
5. **Output & Error Handling**: The API should return the captured stdout/stderr and any execution errors. Implement robust error handling for bad input and execution failures.
6. **Build & Verify**: Ensure the Next.js app builds successfully (`npm run build`). Test the `/api/execute` endpoint using `curl` or Postman with a simple Python script (e.g., `print('Hello from sandbox!')`). Verify logs are stored in Neon Postgres.The audience for Tenki Cloud is developers and AI engineers building and deploying agents or custom compute. The operator could cross-sell 'forge-kit' for automating build loops, 'mcp-kit' for AI tool integrations, 'agent-eval-lab' for agent testing, or 'ai-usage-monitor' for tracking AI spend, directly to this developer community.
Tenki Cloud by Luxor Tech | San Francisco, CA | Head of Developer Relations | Full-time | Remote (SF-based required for event assistance) | https://tenki.cloud/ 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 rele
Start a public technical blog or X thread series (e.g., 'Teardown Tuesday' of a complex OSS bug fix or new library) focused on agent-based systems, AI engineering, or compute platforms. Aim for 4-6 high-quality posts/threads over 2 months, linking to GitHub repos to demonstrate technical depth and building an initial audience. This will serve as a portfolio for content creation and technical communication.
standard Next.js deployment
standard database
New: container orchestration concepts for secure execution - ~1 day to understand basics
Learn it: Docker getting started ↗
Get set up: Install Docker Desktop → `docker run hello-world` to verify → write a Dockerfile.
Requires significant research into sandboxing, container security, and resource isolation for multi-tenant environments - ~1-2 weeks
Learn it: Search getting-started ↗
Apply via the AshbyHQ link provided in the Hacker News post: https://jobs.ashbyhq.com/luxor/eba7430f-c1f5-4d0b-933a-1b9950ead0b7?utm_source=YC
“The role requires engineering experience and a public technical audience. Frame your application around your proven ability to build complex systems quickly using AI tools and highlight your portfolio of indie projects that demonstrate technical prowess and audience engagement, even if not directly in DevRel.”
Open the original ↗