Success Engineer

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 grown 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…