Success Engineer

Firecrawl; San Francisco (CA); Hybrid; USD 180,000 - 240,000; Full time

Benefits offered by this job

Equity, competitive

Generous PTO

Parental leave

Wellness stipend

Learning & Development

Sabbatical

SF HQ perks

401(k) plan

Job summary

Firecrawl in San Francisco is seeking a Success Engineer to be the technical partner for customers, driving adoption, retention, and expansion. You will own integrations, troubleshoot complex problems, and turn a working setup into sustained growth.

This role requires 3+ years in a customer-facing technical role, the ability to read code, work with APIs, and build practical POCs. Hybrid, on-site work in SF is required.

Qualifications

• 3+ years in a customer-facing technical role
• Ability to read code, use an API, and build a POC/integration
• Experience growing accounts and driving adoption/expansion
• Discern between user error, bugs, and product gaps

Responsibilities

• Own the technical health of accounts: ensure success and deepen usage
• Hands-on with the product using customer data to build integrations
• Run technical discovery to diagnose where extraction/pipeline breaks
• Turn technical wins into adoption and partner with revenue to hit targets
• Be the trusted technical voice across the account lifecycle
• Know when to solo-solve or escalate to engineering

Skills

Customer success engineering

API / devtools product

Technical communication

Account growth & adoption

Job description

Success Engineer

You'll be the technical partner customers count on for the long haul. Once an account is live on Firecrawl, you're the one who keeps them winning: deepening how they use the product, unblocking the hard technical problems that come up, and turning a working integration into a growing one. This is a customer-facing engineering role measured in adoption, retention, and expansion, not tickets closed. You build, you deploy, you own the outcome.

• Salary Range: $180,000 to $240,000/year OTE
• Equity Range: Competitive equity — details shared during the process
• Location: San Francisco, CA (Hybrid, on-site required)
• Job Type: Full-Time
• Experience: 3+ years in a customer-facing technical role or equivalent
• Visa: Must be legally authorized to work in the United States. We're not able to sponsor visas right now, though that may change down the line.

About Firecrawl

Firecrawl is the easiest way to turn the web into data AI agents can use. One API call converts any URL into clean, LLM-ready markdown or structured data - the boring-hard problem everyone building with LLMs eventually hits, solved.

We hit 8 figures in ARR in year one and more than doubled it in year two. We have 150k+ GitHub stars, and developers, agents, and category-defining AI companies build on us every day. Growth like this is rare, and we're just getting started.

We're a small team punching far above our weight. Everyone here owns a real piece of the product and company, end to end, and runs it themselves - no hiding behind process or headcount.

This is a place for people who want to work at the frontier: an AI company building the infrastructure other AI companies run on, not one bolting AI onto an existing product. We move fast, go deep, and are building the tools superintelligence will rely on to gather data from the web.

What You'll Do

• Own the technical health of your accounts: keep customers succeeding, deepen their usage, and catch problems before they become churn
• Get hands-on with the product against real customer data, build integrations and solve the technical problems that keep accounts growing
• Run technical discovery: diagnose where a customer's extraction or pipeline breaks, and know whether it's usage, a bug, or a real product gap
• Turn technical wins into adoption and expansion, and partner with the revenue team to hit team targets
• Be the trusted technical voice for your accounts over their whole lifecycle, and bring what you learn in the field back to product and engineering
• Know when to solve it yourself and when to pull in engineering

What We're Looking For

• You've done customer success engineering, solutions, forward-deployed, or another customer-facing technical role, ideally at a developer, API, or AI-infra product
• You're technical enough to earn a developer's respect: you can read code, use an API, and build a real POC or integration yourself
• You've owned accounts over time and grew them, and can point to the technical work that drove adoption and expansion
• You check before you build: you can tell user error from a bug from a real product gap, and you don't turn every ask into a custom feature
• You can translate between deep technical detail and business value without losing either audience
• You move fast and close the loop - you'd rather ship a working fix against real data than perfect a doc
• Backgrounds that often do well: Customer success or solutions engineers at API/devtools companies. Customer-facing engineers who owned accounts from deployment through expansion. Technical account managers who actually built things.
• Ex-founders who sold and delivered their own product.

What We're NOT Looking For

• A pure backend engineer who doesn't want to be in front of customers
• A relationship-only CSM who can't get technical
• Someone who needs a fully-built playbook before they can run

A Note On Pace

We operate at an absurd level of urgency because the window for what we're building won't stay open forever. If that excites you, keep reading. If it doesn't, no hard feelings — but this role probably isn't for you.

Benefits & Perks

• Benefits & Perks Available to all employees
• Salary that makes sense — $180,000-$240,000 OTE, depending on experience
• Own a piece — Gain competitive 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 all parents
• Wellness stipend — $100/month for the gym, therapy, massages, or whatever keeps you human
• Learning & Development - Expense up to $1000/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 SF-based employees
• SF HQ perks — Snacks, drinks, team lunches, intense ping pong, and peak startup energy
• E-Bike transportation — A loaner electric bike to get you around the city, on us
• Full coverage, no red tape — Medical, dental, and vision (100% for employees, 50% for spouse/kids) — no weird loopholes, just care that works
• Life & Disability insurance — Employer-paid short-term disability, long-term disability, and life insurance — coverage for life's curveballs
• Supplemental options — Optional accident, critical illness, hospital indemnity, and voluntary life insurance for extra peace of mind
• Doctegrity telehealth — Talk to a doctor from your couch
• 401(k) plan — Retirement might be a ways off, but future-you will thank you
• Pre-tax benefits — Access to FSAs and commuter benefits (US-only) to help your wallet out a bit
• Pet insurance — Because fur babies are family too
• Available to US-based full-time employees

Interview Process

• Application Review
• Intro Chat (~25 min) — A quick conversation to get to know each other before we go deep. We'll talk about what you've been working on, what drew you to Firecrawl, and what you're looking for in your next role. Time for your questions too.
• Technical & Customer Scenario Interview (~55 min) — We'll walk through a real customer scenario: how you'd handle a live technical question, deepen an account's usage, and spot expansion opportunities. We're looking for technical depth, customer instincts, and how you think about growing an account over time — not rehearsed pitches.
• Founder Chat (~25 min) — Culture, pace, ownership, and how you like to work. Time for your questions too.
• Paid Work Trial (1-2 weeks) — Take on a real, scoped customer scenario with the team, paid at a contractor rate. Build an integration, solve an account problem, or run a technical discovery. It's the truest signal for both sides: you see what the role actually feels like, and we see how you operate. We'll flex around your current commitments.
• Decision — We move fast after the trial.