Forward Deployment Engineer (Developer Success)

Forward Deployment EngineerYou'll work directly with customers to deploy Firecrawl in real-world environments, unblock integrations, and turn customer needs into repeatable solutions and product improvements. This is a highly hands-on, customer-facing engineering role — ideal for someone who likes solving complex problems live and shipping pragmatic solutions fast.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 (Hybrid) OR RemoteJob Type: Full-Time (SF) OR Contract (Remote)Experience: 3+ years or equivalent shipped systemsVisa: US Citizenship/Visa required for SF; N/A for RemoteAbout FirecrawlFirecrawl 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 80k+ 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 DoWork directly with customers to deploy, customize, and troubleshoot Firecrawl in production environmentsOwn technical delivery for priority accounts, from first integration through ongoing optimizationDebug complex real-world issues involving APIs, crawling, data pipelines, and infra constraintsBuild reusable solutions, templates, and playbooks based on customer needsTranslate customer feedback into clear product and engineering insightsCollaborate closely with core engineers to improve reliability, performance, and usabilityHelp define best practices for how Firecrawl is implemented at scaleWhat We're Looking ForA strong engineer who likes being close to customers. You have solid fundamentals — APIs, systems, debugging — and you're comfortable explaining technical concepts clearly to people who aren't engineers. You'd rather hop on a call and unblock someone than file a ticket and wait.Calm and effective in ambiguity. You don't need a runbook for every situation. You diagnose fast, communicate clearly, and make good decisions with incomplete information.Biased toward action. You unblock first, optimize later. You ship pragmatic solutions over perfect abstractions and know when "good enough now" beats "ideal next quarter."Comfortable in a small, high-trust team. You don't need layers of process. You work directly with founders and core engineers, own your domain, and move fast.Backgrounds that often do well: Solutions engineers, SREs, devrel engineers, or customer-facing infra roles. Engineers at startups who wore multiple hats. Ex-founders who've debugged customer problems at 2am because the customer mattered.What We're NOT Looking ForBackend engineers who don't want to talk to customers. This role is half engineering, half customer. If you'd rather stay in your IDE all day, this isn't it.Process-dependent operators. If you need a detailed escalation path and a PM to prioritize your queue, you'll be frustrated here. You own the problem end-to-end.Perfectionists who can't ship under pressure. Customers are waiting. The best solution you can ship today beats the ideal solution next week.A Note On PaceWe 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.Benefits & PerksAvailable to all employeesSalary that makes sense — $170,000–215,000/year (SF, U.S.-based), based on impact, not tenureOwn a piece — Up to 0.20% equity in what you're helping buildGenerous PTO — 15 days mandatory, anything after 24 days, just ask (holidays excluded); take the time you need to rechar ... (truncated, view full listing at source)