Forward Deployed Engineer - Revenue at Firecrawl

Overview

You will be the engineer customers trust to make Firecrawl work in the real world. When a high-value account hits a hard extraction problem, a messy integration, or a "can it even do this?" question, you show up, dig into their stack, and ship the thing that unblocks them. This is a customer-facing engineering role measured in adoption 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 Land inside a customer's environment, understand what they're building, and make Firecrawl work for their actual use case Get hands-on with the product against real customer data, build integrations and POCs that turn "not sure this works for us" into production 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 Partner with the revenue team to turn technical wins into adoption and expansion, and hit team targets Be the trusted technical voice for accounts, 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 forward-deployed, solutions, or customer-facing engineering, 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 the full lifecycle for a customer, from demo to POC to production, and can point to the technical work that made it land 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 POC against real data than perfect a doc Backgrounds that often do well: Solutions engineers or SEs at API/devtools companies. Customer-facing engineers at startups who owned the full lifecycle from demo to deployment. 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 quota-carrying seller who can't build 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.

What You'll Do9

• 1Land inside a customer's environment, understand what they're building, and make Firecrawl work for their actual use case
• 2Get hands-on with the product against real customer data, build integrations and POCs that turn "not sure this works for us" into production
• 3Run technical discovery: diagnose where a customer's extraction or pipeline breaks, and know whether it's usage, a bug, or a real product gap
• 4Partner with the revenue team to turn technical wins into adoption and expansion, and hit team targets
• 5Be the trusted technical voice for accounts, and bring what you learn in the field back to product and engineering
• 6Know when to solve it yourself and when to pull in engineering
• 7Own the full lifecycle for a customer, from demo to POC to production, and point to the technical work that made it land
• 8Translate between deep technical detail and business value without losing either audience
• 9Move fast and close the loop - you'd rather ship a working POC against real data than perfect a doc

Salary Insight