Firecrawl

Manage customer onboarding, lead technical demos, build proofs of concept, and ensure long-term customer success. | At least 3 years in a customer-facing technical role with strong communication and problem-solving skills. | 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 without someone handing you a list every morning. Slow movers. Customers are evaluating us alongside alternatives in real time. If you can't turn around a POC in days, not weeks, you'll lose deals here. 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. Benefits & Perks Available to all employees Salary that makes sense — $150,000–$250,000/year, based on impact, not tenure Own a piece — Up to 0.10% equity in what you're helping build Generous PTO — 15 days mandatory, anything after 24 days, just ask (holidays excluded); take the time you need to recharge Parental leave — 12 weeks fully paid, for moms and dads Wellness stipend — $100/month for the gym, therapy, massages, or whatever keeps you human Learning & Development — Expense up to $1,000/year toward anything that helps you grow professionally Team offsites — A change of scenery, minus the trust falls Sabbatical — 3 paid months off after 4 years, do something fun and new Available to US-based full-time employees Full coverage, no red tape — Medical, dental, and vision (100% for employees, 50% for spouse/kids) — no weird loopholes, just care that works Life & Disability insurance — Employer-paid short-term disability, long-term disability, and life insurance — coverage for life's curveballs Supplemental options — Optional accident, critical illness, hospital indemnity, and voluntary life insurance for extra peace of mind Doctegrity telehealth — Talk to a doctor from your couch 401(k) plan — Retirement might be a ways off, but future-you will thank you Pre-tax benefits — Access to FSAs and commuter benefits (US-only) to help your wallet out a bit Pet insurance — Because fur babies are family too Available to SF-based employees SF HQ perks — Snacks, drinks, team lunches, intense ping pong, and peak startup energy E-Bike transportation — A loaner electric bike to get you around the city, on us Interview Process Application Review – Send us your stuff + a quick note on why this excites you (plus links to things you've built or deployed for customers). Technical & Customer Scenario Interview (~45 min) – We'll walk through a real customer scenario: how you'd run an onboarding, handle a live technical question, and identify expansion opportunities in an account. We're looking for technical depth, customer instincts, and how you think about growing revenue — not rehearsed pitches. Founder Chat (~30 min) – Culture, pace, ownership, and how you like to work. Time for your questions too. Paid Work Trial (1–2 weeks) – Test drive the real thing: work on a real customer engagement with measurable impact. Decision – We move fast after the trial. If you want to be the engineer customers ask for by name — and the reason accounts expand — at one of the fastest-growing AI infrastructure startups, this is your shot. 👉 Apply now and let's set something on fire. 🔥

Own the operational backbone including billing, revenue dashboards, procurement, compliance, and support enterprise deal operations with AI automation. | 3+ years in revenue, billing, or growth operations in SaaS or usage-based companies with proficiency in dashboards and compliance frameworks like SOC 2 or GDPR. | Growth Operations Lead We're looking for someone who keeps the engine running — and makes it run faster. You'll own the operational backbone of Firecrawl's growth motion: billing lifecycle, revenue dashboards, procurement, collections, and the compliance workflows that let us close enterprise deals without tripping over ourselves. If you're the person who finds the thing that's broken before anyone notices, builds a dashboard no one asked for but everyone needs, and quietly saves the company $50K by catching a bad contract — this is your role. Salary Range: $90,000–$160,000/year (Range shown is global. Compensation is adjusted based on your country's cost of living — major U.S. cities will be at the higher end of the range. You can explore how we calculate this here: https://www.firecrawl.dev/careers/compensation.) Equity Range: Up to 0.05% Location: San Francisco, CA or Remote (Americas, UTC-3 to UTC-10) Job Type: Full-Time or Contract Experience: 3+ years in revenue operations, billing operations, or growth ops at a SaaS or usage-based company Visa: N/A (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 the billing lifecycle end to end: Invoicing, collections, subscription management, credits, refunds, and disputes. Nothing falls through the cracks. Customers get billed correctly, on time, every time. Build revenue dashboards the team can trust: Create and maintain dashboards from raw data that give the team real-time visibility into revenue, usage, churn, and expansion. The founders should be able to answer "what are we spending and why?" in under five minutes. Run procurement and vendor operations: Manage subscriptions, contracts, and renewals. Catch wasteful spend before it compounds. Negotiate terms that make sense for a fast-growing startup, not a Fortune 500. Own operational compliance: Operate SOC 2, GDPR, and similar compliance workflows at the day-to-day level — questionnaires, audits, documentation, and vendor security reviews. You're not building the program from scratch; you're keeping it running and audit-ready. Support enterprise deal operations: Handle the operational side of enterprise deals — procurement paperwork, security reviews, custom billing arrangements, and anything else that sits between "verbal yes" and "signed contract." Use AI to move faster than one person should: Build workflows with AI tools to automate reporting, questionnaires, and repetitive ops work. You treat every manual process as a problem to be solved, not a fact of life. What We're Looking For Operationally relentless. You clear the queue. Nothing falls through the cracks. You have systems — whether it's a spreadsheet, a Notion board, or something you built yourself — that keep you on top of everything. People trust you because things get done when you say they will. Comfortable owning the billing lifecycle. You've managed invoicing, collections, subscriptions, or procurement before — ideally at a usage-based or SaaS company. You understand how billing complexity scales and how to stay ahead of it. Can build dashboards from raw data. You're not waiting for a data team to build you a report. You can pull data, structure it, and build revenue dashboards that the team actually uses to make decisions. SQL or equivalent is a plus, but what matters is that you can get from raw data to trusted insight. Has operated compliance at the operational level. You've worked with SOC 2, GDPR, or similar frameworks — not as a consultant who designed the program, but as the person who keeps it running day to day. You know what an auditor is going to ask for before they ask. Uses AI daily to multiply output. You use tools like Claude, n8n, or whatever gets the job done to automate reporting, questionnaires, and ops work. You're not intimidated by new tools — you're the first person on the team to try them. Experience with usage-based pricing and enterprise deal support. You've seen how usage-based models create billing complexity and you know how to manage it. You've helped get enterprise deals across the finish line by handling the operational details that AEs shouldn't be touching. Backgrounds that tend to do well: Revenue ops or billing ops at a SaaS or API company. Finance operations at a high-growth startup. Growth ops roles where you owned the full lifecycle from billing to reporting to compliance. People who've been the "one person who keeps everything running" at a company that was growing faster than its processes. What We're NOT Looking For Finance strategists who don't do the work. This is a hands-on role. If you want to build financial models and present to the board but don't want to chase down a missing invoice, this isn't it. People who need a team before they can deliver. You'll have tools, AI, and support — but you need to be able to own billing, dashboards, compliance, and procurement yourself. If you need a direct report for each function, you'll be frustrated here. Ops people who avoid data. If you're more comfortable with process docs than dashboards, this isn't the right fit. We need someone who lives in the numbers and can build the reporting infrastructure, not just consume it. Anyone who treats compliance as someone else's problem. If your instinct when an auditor sends a questionnaire is "who handles this?" instead of "let me knock this out" — this isn't your role. 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. Benefits & Perks Available to all employees Salary that makes sense — $90,000–$160,000/year (global), based on impact, not tenure Own a piece — Up to 0.05% equity in what you're helping build Generous PTO — 15 days mandatory, anything after 24 days, just ask (holidays excluded); take the time you need to recharge Parental leave — 12 weeks fully paid, for moms and dads Wellness stipend — $100/month for the gym, therapy, massages, or whatever keeps you human Learning & Development — Expense up to $1,000/year toward anything that helps you grow professionally Team offsites — A change of scenery, minus the trust falls Sabbatical — 3 paid months off after 4 years, do something fun and new Available to US-based full-time employees Full coverage, no red tape — Medical, dental, and vision (100% for employees, 50% for spouse/kids) — no weird loopholes, just care that works Life & Disability insurance — Employer-paid short-term disability, long-term disability, and life insurance — coverage for life's curveballs Supplemental options — Optional accident, critical illness, hospital indemnity, and voluntary life insurance for extra peace of mind Doctegrity telehealth — Talk to a doctor from your couch 401(k) plan — Retirement might be a ways off, but future-you will thank you Pre-tax benefits — Access to FSAs and commuter benefits (US-only) to help your wallet out a bit Pet insurance — Because fur babies are family too Available to SF-based employees SF HQ perks — Snacks, drinks, team lunches, intense ping pong, and peak startup energy E-Bike transportation — A loaner electric bike to get you around the city, on us Interview Process Application Review – Send us your stuff + a quick note on why this excites you. Bonus points if you can show us something you've built — a dashboard, a workflow, an ops system that made a real difference. Operations & Systems Interview (~45 min) – Walk us through how you've managed billing, compliance, or revenue operations in a previous role. We'll dig into a real scenario: how you'd approach building revenue visibility or managing billing complexity at scale. We're looking for operational depth, systems thinking, and speed — not theoretical frameworks. Founder Chat (~30 min) – Culture, pace, ownership, and how you like to work. Time for your questions too. Paid Work Trial (1–2 weeks) – Test drive the real thing: tackle a real ops challenge — build a dashboard, clean up a billing process, or audit a vendor list. Decision – We move fast after the trial. If you want to be the person who keeps a rocketship from shaking apart — and you're not afraid to own billing, dashboards, compliance, and procurement all at once — this is your shot. 👉 Apply now and let's build the machine.

Own end-to-end development and product strategy for browser interaction layer including customer research and building scalable AI agent workflows. | 3+ years shipping developer-facing products in browser automation or web scraping with strong product judgment and autonomous work ability. | Product Engineer — Interact You'll own Firecrawl's browser interaction layer — the product that turns Firecrawl from a data extraction tool into the eyes of every AI agent on the web. Interact lets developers scrape a page and then pull data by acting on it: clicking, filling forms, navigating, completing authenticated workflows, extracting data static scraping can't reach. This is our #1 product hire. You own the product decisions, not just the code. You talk to customers, figure out what they actually need (not what they say they need), make prioritization calls with incomplete information, and ship the right thing fast. You also build it — but the product judgment comes first. Salary: $180,000–$290,000/year (adjusted by location — see how) Equity: Up to 0.15% Location: San Francisco or Remote (Americas, UTC-3 to UTC-10) Experience: 3+ years shipping developer-facing products in browser automation, web scraping, or agent tooling About Firecrawl Firecrawl is the easiest way to extract data from the web — a single API call to turn any URL into LLM-ready data. 8-figure ARR, 100k+ GitHub stars, ~26 people. We're building essential infrastructure for how AI agents interact with the web. What This Role Actually Is A product owner who can engineer, not an engineer who occasionally thinks about product. You talk to customers constantly. You develop an intuition for what agent developers are actually trying to do, not just what they're asking for. You make product bets — what to build, what to skip, what to kill — with imperfect data and real tradeoffs. You also understand agentic systems deeply enough to know how agents choose and use tools, what makes an interaction API reliable vs. fragile at scale, and how to test whether agents actually prefer what you've built. Then you build it yourself. Design to deployment, one person. Day to day, you: Own the Interact product end-to-end — scrape-then-interact workflows, prompt-based interaction, session chaining, persistent profiles, live view Talk to customers and read every GitHub issue, Discord thread, and support ticket that touches Interact — not because someone asked, but because that's where the signal is Separate what customers ask for from what they actually need, and prioritize accordingly Ship fast product experiments — hypothesis, build, measure, decide in days Make prompt-based interaction reliable and magical: "click login and fill the email field" should just work, on any page, every time Dogfood relentlessly — you use the API before you ship changes to it You're a Fit If You Think product-first. You form opinions about what to build and why before anyone scopes a ticket. You can hold ambiguity and still make a call. Have deep empathy for developers. You've built things developers loved. You know the difference between "works" and "delights" at the API level. Understand the scraping and browser data space. This isn't abstract to you — you know what breaks, what's hard, and what matters. Get agentic systems. You've thought about (or built) tooling for AI agents. You understand how agents select tools, where interaction fails, and what reliable agent workflows require. Ship fast and learn faster. You write code, own features, and iterate. Ambiguity doesn't slow you down. You're Not a Fit If You Need a PM to tell you what to build Build great infra but don't care how it feels to the developer on the other end Haven't thought about how AI agents actually use browser interaction tools Optimize for technical elegance over shipping the right product Benefits & Perks Available to all employees Salary that makes sense — $180,000–$290,000/year, based on impact, not tenure Own a piece — Up to 0.15% equity in what you're helping build Generous PTO — 15 days mandatory, anything after 24 days, just ask (holidays excluded); take the time you need to recharge Parental leave — 12 weeks fully paid, for moms and dads Wellness stipend — $100/month for the gym, therapy, massages, or whatever keeps you human Learning & Development — Expense up to $1,000/year toward anything that helps you grow professionally Team offsites — A change of scenery, minus the trust falls Sabbatical — 3 paid months off after 4 years, do something fun and new Available to US-based full-time employees Full coverage, no red tape — Medical, dental, and vision (100% for employees, 50% for spouse/kids) — no weird loopholes, just care that works Life & Disability insurance — Employer-paid short-term disability, long-term disability, and life insurance — coverage for life's curveballs Supplemental options — Optional accident, critical illness, hospital indemnity, and voluntary life insurance for extra peace of mind Doctegrity telehealth — Talk to a doctor from your couch 401(k) plan — Retirement might be a ways off, but future-you will thank you Pre-tax benefits — Access to FSAs and commuter benefits (US-only) to help your wallet out a bit Pet insurance — Because fur babies are family too Available to SF-based employees SF HQ perks — Snacks, drinks, team lunches, intense ping pong, and peak startup energy E-Bike transportation — A loaner electric bike to get you around the city, on us Interview Process Application — Show us what you've shipped. A product, a GitHub link, a write-up. Intro Chat (20 min) — Get to know each other. Product Deep Dive (60 min) — How you think about product decisions, DX tradeoffs, and translating customer signal into shipped features. Technical Deep Dive (60 min) — Architecture, system design, and how you think through hard problems live. Paid Work Trial (1–2 weeks) — A real product problem. We evaluate shipping speed, product judgment, and DX quality. Decision — Fast. If you want to own the product that makes AI agents actually useful on the web — and you're the kind of person who talks to customers before writing code — this is your role.

Own and improve the developer-facing search API product by translating research into shipped features with excellent developer experience. | 3+ years applied RL, ML engineering, or model training experience with production systems, strong product and engineering fluency, and hands-on shipping of APIs. | Product Engineer — Search You'll own the developer-facing search experience at Firecrawl — taking the retrieval and ranking improvements coming out of research and shipping them as a product developers can't stop using. This isn't a pure research role and it isn't a pure backend role. You sit at the intersection: you understand how the systems work deeply enough to improve them, and you care about how they feel to use obsessively enough to make them great. At a 26-person company, the gap between research and shipped product is exactly one person. You're that person. Salary Range: $180,000-$290,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.15% Location: San Francisco, CA or Remote (Americas, UTC-3 to UTC-10) Job Type: Full-Time Experience: 3+ years in applied RL, ML engineering, or model training — with production systems 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 100k+ 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 superintelligence will use to gather data on the web. We ship fast and deep. What You'll Do Ship search improvements that developers notice. Take retrieval and ranking improvements from research and turn them into product changes that make developers say "this just works." You know that a 200ms latency improvement isn't just a benchmark win — it's a better product. You ship the whole thing: the API change, the docs update, the example that makes it obvious. Own the search API end-to-end. You're responsible for how Firecrawl's search endpoint feels to integrate, use, and build on. That means response format, latency, error handling, pagination, filtering — every surface a developer touches. You're the person who notices when something is confusing before a user files a GitHub issue about it. Dogfood relentlessly. You build things with the API before you ship them. You feel the friction before your users do. You read every GitHub issue, every Discord thread, every support ticket that touches search — not because someone asked you to, but because that's where the product signal lives. Translate research into product decisions. You work closely with the Search/IR and RL Research Engineers. You understand their work well enough to make good product calls about what to prioritize, what to expose to users, and what to keep under the hood. You ask good questions. You push back when something technically elegant would make the API worse. Run fast product experiments. You form a hypothesis about what would make search better for developers, instrument it, ship it, measure it, and decide quickly. You're comfortable making calls with imperfect data because waiting for perfect data means shipping nothing. Raise the bar on developer experience. Firecrawl's users are technical. They have high standards. They notice when response formats are inconsistent, when error messages are unhelpful, when documentation doesn't match behavior. You notice too — and you fix it before they have to ask. What We're Looking For Obsessive about developer experience. You think about DX the way a designer thinks about pixels. Latency, response structure, error messages, API ergonomics — these things matter to you on a visceral level. You've built APIs that developers loved and you know the difference between an API that works and one that delights. Speaks both product and engineering fluently. You can read a ranking algorithm and understand its implications for the search experience. You can write the API spec and implement it yourself. You don't need a PM to tell you what matters or an ML engineer to explain why a retrieval change is significant. You connect those dots on your own. Hands-on builder who ships. You write code. You own features from design to deployment. You're comfortable with ambiguity and you don't need a perfectly scoped ticket to make progress. You ship something, learn from it, and iterate. Has a feel for search as a product. You've thought seriously about what makes search good — not just fast or accurate, but genuinely useful. You understand the difference between recall and precision and why developers care about both. You have intuitions about query understanding, result ranking, and when semantic search beats keyword search — and you've built products that put those intuitions to work. Brings production instincts. You've operated systems under real load. You know what breaks first, how to instrument what matters, and how to make good latency/quality tradeoffs. You're not just building features — you're building infrastructure developers depend on. Backgrounds that tend to do well: Engineers who've owned search or discovery features at developer-tools companies. Full-stack engineers with a strong backend bias who've shipped APIs used by thousands of developers. Engineers from search infrastructure teams who got frustrated by the distance between their work and the user experience. People who've built on top of Elasticsearch, Vespa, or vector databases — and cared enough about the product layer to go deeper than the query interface. What We're NOT Looking For Great engineers who don't care about DX. If you build technically excellent systems but think API ergonomics and documentation are someone else's problem, this isn't the role. The product experience is part of the job — not an afterthought. People who need a PM. There's no product manager between you and the work. You define what good looks like, you decide what to prioritize, and you own the outcome. If that's uncomfortable, you'll struggle here. Specialists who only work on one layer. If you're only interested in backend systems and tune out when the conversation shifts to how something is exposed to developers — or vice versa — this won't be a fit. This role requires you to hold both. Slow shippers. The research team will produce improvements faster than a slow product cycle can absorb them. We need someone who can take something from "this ranking model is better" to "this is live in the API with docs and an example" in days, not sprints. People who don't use the product. If you're not the kind of engineer who builds side projects with APIs like ours, reads the docs critically, and notices when something feels off — you'll miss the signal that makes this role work. 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. Benefits & Perks Available to all employees Salary that makes sense — $180,000-$290,000/year, based on impact, not tenure Own a piece — Up to 0.15% equity in what you're helping build Generous PTO — 15 days mandatory, anything after 24 days, just ask (holidays excluded); take the time you need to recharge Parental leave — 12 weeks fully paid, for moms and dads Wellness stipend — $100/month for the gym, therapy, massages, or whatever keeps you human Learning & Development — Expense up to $1,000/year toward anything that helps you grow professionally Team offsites — A change of scenery, minus the trust falls Sabbatical — 3 paid months off after 4 years, do something fun and new Available to US-based full-time employees Full coverage, no red tape — Medical, dental, and vision (100% for employees, 50% for spouse/kids) — no weird loopholes, just care that works Life & Disability insurance — Employer-paid short-term disability, long-term disability, and life insurance — coverage for life's curveballs Supplemental options — Optional accident, critical illness, hospital indemnity, and voluntary life insurance for extra peace of mind Doctegrity telehealth — Talk to a doctor from your couch 401(k) plan — Retirement might be a ways off, but future-you will thank you Pre-tax benefits — Access to FSAs and commuter benefits (US-only) to help your wallet out a bit Pet insurance — Because fur babies are family too Available to SF-based employees SF HQ perks — Snacks, drinks, team lunches, intense ping pong, and peak startup energy E-Bike transportation — A loaner electric bike to get you around the city, on us Interview Process Application Review — Send us your work and a quick note on why this excites you. Show us what you've shipped — search features, APIs, developer-facing products. A GitHub link, a product you've built, or a write-up of something you're proud of goes a long way. Intro Chat (~20 min) — A quick conversation to get to know each other before we go deep. We'll talk about what you've been working on, what drew you to Firecrawl, and what you're looking for in your next role. Time for your questions too. Deep Dive Chat (~45 min) — Go deep on search products and APIs you've built: architecture decisions, DX tradeoffs, how you've translated technical improvements into product changes. We'll explore a live problem — how you'd take a retrieval improvement and ship it as a better developer experience at Firecrawl. We're looking for product instincts, technical depth, and the ability to hold both at once. Founder Chat (~30 min) — Culture, pace, ownership, and how you like to work. Time for your questions too. Paid Work Trial (1-2 weeks) — Tackle a real search product problem with production implications. We evaluate on shipping speed, product judgment, and how well you balance technical quality with developer experience. Decision — We move fast after the trial. If you want to own the search experience at one of the fastest-growing developer infrastructure companies in AI — and you're the kind of engineer who won't stop until it's great — this is your shot. 👉 Apply now.

| Salary Range: $90,000-$130,000/year Equity Range: 0.05%-0.15% Location: San Francisco, CA (Hybrid) Job Type: Full-Time Experience: 3+ years Visa: US Citizenship/Visa Only 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 millions in ARR and 48k+ GitHub stars by building the fastest way for developers to get LLM-ready data. Previously, we built Mendable, one of the first commercially available "chat with your data" applications. We sold to companies like MongoDB, Coinbase, Snapchat, and more. To do this, we spent a surprising amount of time building reliable infrastructure for getting clean data from the web. When we started to see our founding friends rebuilding the same thing, we thought we might be on to something. Why Firecrawl Content ownership - Shape how technical audiences discover and understand our product Real impact - Your content strategy directly drives developer adoption and growth High velocity - See your content go from idea to published to ranking in days, not months Small team, big ambition - Work directly with founders and engineers who understand content's value About the Role We're looking for an SEO & GEO Specialist who lives at the intersection of content strategy and technical execution. You'll research what developers are searching for, plan content that answers their questions, and coordinate our content machine while being ready to write technical content yourself when needed. This isn't about managing from spreadsheets—it's about understanding developer pain points, mapping content opportunities, and ensuring every piece we publish serves both search engines and our technical audience. What You'll Do Research & Strategy Conduct deep keyword research and competitive analysis to identify content gaps in the developer tools space Map search intent and build comprehensive topic clusters around web scraping, data extraction, and AI workflows Analyze SERP features, ranking factors, and algorithm updates to inform content strategy Research technical topics and translate complex concepts for various developer audiences Content Planning & Coordination Own our Linear content calendar—from ideation to publication to optimization Brief writers and editors on technical topics, ensuring accuracy and search optimization Coordinate with engineering team to validate technical content and gather product insights Manage content production pipeline, balancing SEO requirements with technical accuracy Hands-On Content Creation Write technical content when needed—tutorials, documentation, comparison guides Optimize existing content based on performance data and search trends Create programmatic content templates for scaling (API references, integration guides) Ensure all content meets both SEO best practices and developer expectations Technical SEO Implementation Conduct technical audits and implement fixes (schema markup, site structure, Core Web Vitals) Monitor and improve crawlability, indexation, and ranking performance Work with engineering to implement SEO requirements in our docs and marketing sites Build and maintain internal linking strategies and content architecture Performance & Optimization Track content performance across organic channels using GA4, Search Console, and Ahrefs Run content experiments and A/B tests to improve CTR and engagement Report on SEO metrics that matter—traffic, rankings, conversions, not just impressions Identify and act on quick wins while building toward long-term organic growth Who You Are Location: Remote—U.S. time zone Must-Haves: Proven SEO Track Record: You've ranked technical content in competitive spaces and have the case studies to prove it Technical Fluency: You can read API docs, understand code examples, and speak developer Content Strategy Experience: You've built and executed content strategies that drove measurable organic growth Research Skills: You dig deep into topics, validate information, and synthesize complex technical concepts Project Management: Comfortable juggling multiple content pieces, coordinating with stakeholders, and meeting deadlines Writing Ability: Can produce clear, technical content that ranks and resonates with developers Nice-to-Haves: Experience with developer tools, APIs, or B2B SaaS products Familiarity with Linear, GitHub, or other developer workflows Background in technical writing or developer documentation Experience with programmatic SEO and content automation Knowledge of Python, JavaScript, or other programming languages Bonus Points Built content strategies for developer-focused products that scaled to 100k+ monthly organic users Created technical content that consistently ranks top-3 for high-intent developer queries Managed content operations using Linear or similar project management tools Experience working directly with engineers and technical teams Built programmatic SEO pages using structured data and templates Active in developer communities (Stack Overflow, GitHub, Dev.to, etc.) What it means to join Firecrawl High Leverage — Your content strategy directly drives our growth trajectory Autonomy — Own the entire SEO/content domain with freedom to experiment Remote-First Culture — Work from anywhere in U.S. time zones Growth Opportunity — Early equity in a fast-growing developer tools company Creative Freedom — Test new content formats, channels, and strategies Benefits & Perks Salary that makes sense — $90,000-$130,000/year, based on impact, not tenure Own a piece — 0.10%-0.30% equity in what you’re helping build Full coverage, no red tape — Medical, dental, and vision plans that cover stuff Parental leave — 12 weeks fully paid, for moms and dads Take a break (seriously) — Unlimited PTO, minimum of 3 weeks off Gear up — Get the tools you need to do your best work, no approvals circus Wellness stipend — Use it for the gym, therapy, or whatever keeps you human SF HQ perks — Snacks, drinks, lunches, and the occasional chaotic energy Pet insurance — Because fur babies are family too Team offsites — A change of scenery, minus the trust falls Sabbatical — 3 paid months off after 4 years, do something fun and new Interview Process Application Review - Portfolio, case studies, and why Firecrawl excites you Intro Chat (30 min) - Quick alignment call with our team Technical Interview (45 min) - Deep dive into your SEO approach and past wins Content Challenge (2-3 hrs) — Research and plan a few content clusters for a technical topics Paid Work Trial (1 week) - Work on real content with our team Decision - We move fast If you love researching what developers search for, can coordinate content operations while writing technical pieces yourself, and want to build the organic growth engine for a rocket ship developer tool, this is your role.