Developer Relations

Blaxel•San Francisco, CA

About The Position

The role You'll own how developers discover, learn, and adopt Blaxel, end to end. Everything a developer touches on the way in, the docs, the tutorials, the integration guides, the code examples, the deep-dive blog posts, the Discord, the talk they saw at a meetup, is your surface. Your job is to make Blaxel the platform developers reach for and the community they want to be part of. This is a founding, hands-on role today with a path to build the function tomorrow. You think like a mini-founder: you own the outcome, you set the playbook for how we reach developers, and you don't wait for someone to hand you a ticket.

Requirements

Builder first. You read code and ship working examples.
Hand you an unfamiliar feature or a corner of the codebase you've never seen, and you'll dig in, with AI as your accelerant, until you understand it well enough to build on it and explain it plainly.
Super autonomous. You don't wait for a hand to hold. You find the subject-matter expert, ask the sharp questions, and figure out how something works and how developers will get the most out of it.
A genuinely good technical writer. You take a complex topic and make it clear, engaging, and convincing without dumbing it down. Developers trust your writing because it's accurate and it respects them.
Fluent in the stack. Ideally, you know AI infra, containers, sandboxes, VMs, the tradeoffs between the major clouds and neoclouds.
You're actively curious about AI and where the ecosystem is heading, because that's the audience you're writing for.
AI-native. You use AI as a force multiplier on real technical understanding, not a substitute for it. You can explain why something works, not just what an LLM said about it, and you wire up automation so the boring parts run themselves.
Comfortable on stage and in the thread. You like being present in the community, whether that's a Discord DM at 10pm, a conference talk, or a viral technical thread. You represent the brand well because you actually care about the developers you're talking to.

Responsibilities

Write authoritative deep-dive blog posts on the hard problems we solve: latency, stateful serverless, sandboxing, enterprise agent architecture, benchmarks.
Interview the engineers who built it so each one is technically true, not surface-level.
Own the docs. Keep them accurate, clear, and current with everything we ship.
Ship integration guides, tutorials, and runnable code examples that show how a feature works and how to use it well.
Run and grow the community on Discord and beyond. Answer the hard questions, turn users into advocates, and route what you learn back to product and content.
Represent Blaxel at events. Speak, show up, and run community events that bring the right developers to us.
Set up the AI-powered systems and automation that let one person ship content at the pace of a team.
Measure what content and channels drive signups and adoption. Double down on what works, kill what doesn't.