Forward Deployed Engineer (FDE)
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: $209,000–$265,000 USD/year OTE
Equity Range: Competitive equity. Details shared during the process.
Location
San Francisco, CA (SF HQ). On-site, five days a week.
Job Type: Full-Time
Experience: 3+ years in a customer-facing technical role or equivalent
Work Authorization: Open to candidates already authorized to work in the US. We also support H-1B transfers, F-1 OPT and STEM OPT, TN (Canada and Mexico), and E-3 (Australia). We’re not able to sponsor new H-1B visas for candidates outside the US.
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 Deployment 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