Developer Experience Engineer

Salary Range: $130,000–$170,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.)

Equity Range: Up to 0.15%

Location: San Francisco, CA (Hybrid) OR Remote

Job Type: Full-Time (SF) OR Contract (Remote)

Experience: 3+ years

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 a year, we've hit millions in ARR and 68k+ GitHub stars by building the fastest way for developers to get LLM-ready data.

We're a small, fast-moving, technical team building essential infrastructure for the AI era. We value autonomy, clarity, and shipping fast.

About the Role

We're looking for a Developer Experience Engineer to be the bridge between our product and the developers who use it. You'll build in public, create integrations, ship open source projects, and make sure every touchpoint—docs, demos, tutorials, landing pages—helps developers succeed with Firecrawl.

This role sits on the marketing team but you'll spend most of your time writing code, not copy. You're the technical voice that makes our product click for developers.

What You'll Do

• Build integrations and open source projects that showcase what's possible with Firecrawl

• Write technical blog posts, tutorials, and guides that developers actually want to read

• Create and improve developer documentation—make it clear, accurate, and useful

• Film demos and walkthroughs for product launches and marketing content

• Be a technical pair of eyes on marketing copy, landing pages, and announcements

• Build landing pages and handle minor design work for campaigns and launches

• Contribute to Launch Week setup, execution, and content creation

• Engage with the developer community—GitHub issues, Discord, Twitter, wherever they are

• Build in public and share what you're working on

Who You Are

• 3+ years as a software engineer, devrel, or similar technical role

• You ship side projects and genuinely enjoy building things

• You can write—technical content that's clear, concise, and helpful

• You're comfortable on camera or willing to get there (demos, walkthroughs, etc.)

• You have opinions about what makes good developer experience

• You're active in the developer community—open source, Twitter, blogs, whatever your thing is

• You can context-switch between code, content, and creative work without losing momentum

• Bonus: Experience with web scraping, AI/LLM tooling, or developer tools

What It Means to Join Firecrawl

• Build in Public — Your work ships fast and the community sees it

• High Leverage — Touch product, marketing, and community all at once

• Autonomy — Own your projects end-to-end with minimal oversight

• Remote-First Culture — Work from anywhere in U.S. time zones

• Creative Freedom — If you think it'll work, we'll let you try it

Benefits & Perks

Available to all employees

• $130,000–$170,000/year salary (U.S.-based), based on impact

• Up to 0.15% equity

• Unlimited PTO (minimum 3 weeks encouraged)

• 12 weeks paid parental leave

• $100/month wellness stipend

• $150/year learning & development budget

• Team offsites

• 3-month paid sabbatical after 4 years

Available to US-based full-time employees

• Full medical, dental, and vision (100% for employees, 50% for dependents)

• Life & disability insurance

• 401(k) plan

• FSAs and commuter benefits

• Pet insurance

Available to SF-based employees

• SF HQ perks—snacks, drinks, team lunches

Interview Process

1. Application Review — Send us your stuff: GitHub, blog, Twitter, whatever shows how you think

2. Intro Chat (~25 min) — Quick vibe check and alignment on the role

3. Technical Chat (~30 min) — Walk us through something you've built

4. Paid Work Trial (1–2 weeks) — Jump into real projects with the team

5. Decision — We move fast

If you're an engineer who loves building in public, explaining technical concepts, and making developer tools better—let's talk.