Forward Deployed Engineer

FORWARD DEPLOYED ENGINEER You'll be embedded with our most important customers — not to write code in a corner, but to grow accounts by making Firecrawl indispensable. You'll run onboarding, lead demos, build POCs, drive expansion conversations, and be the technical face of Firecrawl that customers trust and want to keep working with. This is a customer-facing engineering role where your success is measured in revenue, not commits. Salary Range: $150,000–$250,000/year (Range shown is for U.S.-based employees. Compensation outside the U.S. is adjusted fairly based on your country's cost of living. You can explore how we calculate this here: https://www.firecrawl.dev/careers/compensation.) Equity Range: Up to 0.10% Location: San Francisco, CA or Remote (Americas, UTC-3 to UTC-10) Job Type: Full-Time (SF) OR Contract (Remote) Experience: 3+ years in a customer-facing technical role or equivalent Visa: US Citizenship/Visa required for SF; N/A for Remote 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 8 figures in ARR and 90k+ 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 super-intelligence will use to gather data on the web. We ship fast and deep. WHAT YOU'LL DO - Own customer onboarding end to end: Take new customers from signed contract to production deployment. Make the first experience so good they never consider an alternative. - Run demos and build POCs that close deals: Partner with the growth team to show technical buyers exactly how Firecrawl solves their problem — live, with their data, on their timeline. - Drive account expansion: Identify opportunities within existing accounts to grow usage, add new use cases, and expand contracts. You're not waiting for a CSM to flag upsell opportunities — you're the one closest to the customer. - Lead business reviews and customer calls: You're the technical face of Firecrawl. You run QBRs, handle escalations, and keep customers confident that we're the right long-term partner. - Build what customers need to buy: When a prospect needs a custom integration, a proof of concept, or a technical validation to get their team on board — you build it. Fast. - Feed product intelligence back to the team: You're in more customer conversations than anyone. Surface patterns — what's blocking adoption, what features would unlock expansion, where competitors are showing up — and make sure Product and Engineering hear it. WHAT WE'RE LOOKING FOR Someone who spends most of their time talking to customers, not coding alone. You're energized by customer calls, not drained by them. You'd rather be on a Zoom walking someone through an integration than heads-down in an IDE. The code you write exists to unblock a customer or close a deal — not for its own sake. Technically deep enough to build what customers need to buy. You can build POCs, debug integrations, write against our API, and go deep on technical architecture conversations. You're not a sales rep who needs an engineer on every call — you are the engineer on the call. Strong on-camera presence, confident on discovery calls and business reviews. You can run a demo without a script, handle live questions with poise, and hold a room (or a Zoom) with technical and non-technical stakeholders alike. People trust you because you're credible, clear, and genuinely helpful. Growth-minded. You think about accounts in terms of expansion potential, not just support tickets. You see a customer using Firecrawl for one use case and immediately start thinking about the other three they should be using it for. Fast to ramp on complex products. You'll develop a deep understanding of Firecrawl's API, infrastructure, and competitive landscape — not by reading docs, but by deploying it with real customers under real constraints. 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 Backend engineers who don't want to talk to customers. This role is 70% customer-facing, 30% building. If you'd rather stay in your IDE all day, this isn't it. Traditional CSMs who can't go deep technically. Relationship management matters, but you earn trust through technical credibility — building POCs, debugging live, and knowing the product cold. If you need an engineer on every customer call, this isn't the right fit. People who wait to be told which accounts to focus on. You own your book of business. You identify expansion opportunities, prioritize your own pipeline, and drive revenue