Responsibilities

• 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

Requirements

• Experience: 3+ years in developer relations, technical content, or software engineering with a content track record
• 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.

Benefits

• Available to all employees
• Salary that makes sense — $150,000–$200,000/year (SF, U.S.-based), based on impact, not tenure
• Own a piece — Up to 0.1% equity in what you're helping build
• Generous PTO — 15 days mandatory, anything after 24 days, just ask (holidays excluded); take the time you need to recharge
• Parental leave — 12 weeks fully paid, for moms and dads
• Wellness stipend — $100/month for the gym, therapy, massages, or whatever keeps you human
• Learning & Development — Expense up to $1,000/year toward anything that helps you grow professionally
• Team offsites — A change of scenery, minus the trust falls
• Sabbatical — 3 paid months off after 4 years, do something fun and new
• Available to US-based full-time employees