Forward Deployed Engineer - Revenue
Technologies
API · POC · integration · Firecrawl · LLM · markdown · structured data · devtools
About firecrawl
API that converts any URL into LLM-ready markdown or structured data, used by developers to feed AI agents reliable web data.
Series A · 10–50 people
Job description
The full responsibilities and requirements are on the employer’s site.
Open application page ↗Source and classification
Implementation & delivery · Evidence for this classification:
Forward Deployed Engineer - Revenue You'll 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're the one who shows up, digs into their stack, and ships 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: $190,000 to $265,000/year OTE Equity Range: Competitive equity — details shared during the process. Location: San Francisco, CA (Onsite) 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
More from the job description
Forward Deployed Engineer - Revenue You'll 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're the one who shows up, digs into their stack, and ships 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: $190,000 to $265,000/year OTE Equity Range: Competitive equity — details shared during the process. Location: San Francisco, CA (Onsite) 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 175k+ 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 w [... source excerpt omitted ...] 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 h [... source excerpt omitted ...] n 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 betw
Employer postings · Data from · Sources