Dev Rel (Docs & YouTube)

Dev Rel (Docs & YouTube)

You'll be the person developers learn Firecrawl from — through docs that actually help them build, YouTube tutorials they watch start to finish, and community presence that makes them feel like they're building alongside us, not just consuming our API. We have the product. We need the person who makes it impossible to not understand.

Salary Range

$150,000–$200,000/year (Range shown is for U.S.-based employees in San Francisco, CA. Compensation outside the U.S. is adjusted fairly based on your country's cost of living. You can explore how we calculate this here: https://www.firecrawl.dev/careers/compensation.)

Equity Range: Up to 0.1%

Location

• San Francisco, CA or Remote (Americas, UTC-3 to UTC-10)
• Job Type: Full-Time

Experience

3+ years in developer relations, technical content, or software engineering with a content track record

Visa: US Citizenship/Visa required for SF; open for Remote

About Firecrawl

Firecrawl is the easiest way to extract data from the web. Developers use us to reliably convert URLs into LLM-ready markdown or structured data with a single API call. In just over a year, we've hit 8 figures in ARR and 100k+ GitHub stars by building the fastest way for developers to get clean, structured web data.

We're a small, fast-moving, technical team building essential infrastructure for the AI era. We ship fast and deep.

What You'll Do

Own Firecrawl's technical documentation — rewriting, restructuring, and maintaining docs so both humans and AI agents can discover and use the product effectively

Run and grow our YouTube channel — scripting, filming, editing, and publishing a consistent cadence of tutorials, walkthroughs, and demos developers actually finish watching

Build a presence in the AI engineering and open source community — on social, at conferences, in Discord servers, in the places developers actually hang out

Translate developer feedback into product insights and route them clearly to engineering

Create content that drives adoption — not just views — by meeting developers where they are in the build process

Show up on camera and on stage: conference talks, livestreams, Twitter Spaces, wherever our developers are

What We're Looking For

An engineer who can teach. You have a software engineering background and have built with APIs, SDKs, or developer tools. You know what it feels like to hit a wall in someone else's docs — and you know how to fix it.

A YouTube operator. You've owned a technical YouTube channel before — not just appeared in videos. You know the full workflow: scripting for retention, filming efficiently, editing for technical audiences, and building a publishing cadence that doesn't collapse under pressure.

Fluent in the AI/ML developer ecosystem. Agents, LLM tooling, orchestration frameworks, RAG pipelines — you speak this language and you've built in it. You understand where Firecrawl fits and why developers reach for it.

Thinks about docs as infrastructure. You understand that in an agent-first world, documentation needs to be structured for machines as much as humans. You have opinions about how to do that.

Community-connected. You have real relationships in the AI engineering or open source world — not just followers. You can open doors for Firecrawl that cold outreach can't.

Backgrounds that often do well: DevRel at an API-first or developer tools company, software engineer who started a technical YouTube channel, open source contributor with a content track record.

What We're NOT Looking For

Content marketers who have never shipped code

People who measure DevRel success in video views over developer adoption

Anyone waiting for a content calendar to be handed to them before they start creating

• A Note On Pace
• We're a small team doing a lot. Roles here are loosely defined on purpose — you'll own things that don't have a clear owner yet, and that's a feature, not a bug. If you need your scope fully defined before you can move, this probably is