Go-to-market · Remote (US/EU) · Open
Developer Advocate
The first dedicated DevRel hire. Help AI engineers actually understand what Hatch does — through writing, code samples, conference talks, and the kind of community presence that a well-built product earns over time.
About the role
Hatch's customers find us through technical writing, conference talks, and the runtime's open-source SDKs. We've grown to 250 customers mostly on the strength of the team writing well; the role is to scale that.
You'd own the entire DevRel surface: the blog (3-4 deep technical posts per quarter), conference presence (we sponsor and speak at about a dozen events a year), the example apps and docs (we have working open-source examples for 12 use cases; we want 25), and a steady community presence on Hacker News, X, and the AI engineering Discords where our customers live.
This is a senior IC role partnering with Helena (Head of Product), Diego (Design), and the entire engineering team. You'll write, you'll ship example code, you'll travel.
What you'll do
• Write 3-4 technical deep-dives per quarter on the Hatch blog. Real ones — "how we built X," not "what is X." Past examples set the bar.
• Own conference presence: pick the right events, pitch talks, deliver them. ~6 talks a year, mix of regional meetups and major conferences (AI Engineer Summit, NeurIPS, KubeCon).
• Build and maintain the working example apps — 12 today, 25 by end of year. Real apps people deploy from, not snippets.
• Run our presence on Hacker News, X, and AI-engineering Discords. We're not a megaphone; we're a participant. You'd lead that.
• Partner with engineering on developer-facing release docs. Every major release ships with a 600-1200 word post — you'd own the writing, eng owns the technical correctness.
Who you are
• Four-plus years in a DevRel, technical-marketing, or engineer-turned-writer role at a developer-tools company.
• Genuinely good writer. We don't mean "writes okay" — we mean: you can write a Stratechery-quality post on how a real system works in eight hours, twice a quarter, and consistently.
• Comfortable on a stage. Roughly half this role is delivering talks; if public speaking is a chore, this isn't right.
• You can ship working code. Most of your example apps will be ones you wrote.
• Some background in AI engineering is a strong plus — you'd be talking to AI engineers most days.
About Hatch
Hatch is the workflow runtime for AI-native products. We're a 32-person team across Brooklyn and Berlin, $42M Series A (Accel + Khosla), and 250+ customers running production workloads on us today. Founded in 2024 by Mei Tanaka (ex-design lead at Notion) and Aaron Park (ex-infra at Stripe and Modal).
Our customers ship AI agents, copilots, and autonomous workflows. We solve the boring problems underneath them: queueing, retries, versioning, observability, rollback. The product is opinionated, the docs are honest, and the bills don't surprise you. We're remote-OK with hubs in two cities, comp is transparent, and we hire slow on purpose — the team you'd join all read the runtime end-to-end in their first two weeks.
APPLY FOR THIS ROLE
Apply for Developer Advocate.
We read every application. You'll hear from us within five business days — yes or not-this-time, never silence.
Prefer email? Send your application to hello@hatch.example with the role title in the subject.