You'll work directly with customers to get Firecrawl integrated, running, and scaling inside their products. That means writing real code, debugging real systems, and turning customer needs into shipped solutions , fast. This is not a support role. It's a technical ownership role with a customer face.
\nSalary Range: $160,000–$220,000/year (Range shown is for U.S.-based employees in San Francisco, CA. Compensation outside the U.S. is adjusted fairly based on your country's cost of living.)
\nEquity Range: Up to 0.10%
\nLocation: San Francisco, CA or Remote (Americas, UTC-3 to UTC-10)
\nJob Type: Full-Time
\nExperience: 3+ years or equivalent shipped systems
\nVisa: US Citizenship/Visa required
\nYou'll own technical integration delivery for priority customers , from first API call through production scale. Write TypeScript/Node.js code to build, customize, and debug integrations with payments systems, cloud platforms, and third-party APIs. Debug complex real-world issues live with customers , crawling edge cases, data pipeline failures, infra constraints. Build reusable solutions and playbooks that turn one-off customer problems into repeatable wins for the team. Translate customer friction into clear product and engineering insights and route them to the right people. Work closely with core engineering on reliability, performance, and DX improvements driven by what you're seeing in the field
\nA strong TypeScript/Node.js engineer. You write clean, production-quality code and you're fast. You've built integrations with external APIs and you understand what makes them brittle.
\nExperienced with payments and cloud platforms. You've worked with Stripe or similar billing systems. You've integrated with GCP, Vercel, or comparable cloud providers. You don't need to Google the basics.
\nSolid on backend and data fundamentals. You can design a system, model a schema, and reason about data at scale. You know when to reach for a relational database and when not to.
\nSecurity-aware. You understand the common auth patterns , OAuth, API keys, JWTs , and you know where the traps are when integrating third-party systems.
\nHigh ownership with customers. You're comfortable in ambiguous, high-stakes situations with real customers. You communicate clearly, set expectations honestly, and follow through.
\nBackgrounds that often do well: integration or platform engineers, solutions engineers who write real code, early engineers at API-first startups who owned customer-facing technical work.
\nWe're a small team doing a lot. Roles here are loosely defined on purpose , you'll own things that don't have a clear owner yet, and that's a feature, not a bug. If you need your scope fully defined before you can move, this probably isn't the right fit. If you want to build something that matters inside one of the fastest-growing AI infrastructure companies in the world, let's talk.
\nSalary that makes sense , $160,000–$220,000/year (SF, U.S.-based), based on impact, not tenure
\nOwn a piece , Up to 0.1% equity in what you're helping build
\nGenerous PTO , 15 days mandatory, anything after 24 days, just ask (holidays excluded); take the time you need to recharge
\nParental leave , 12 weeks fully paid, for moms and dads
\nWellness stipend , $100/month for the gym, therapy, massages, or whatever keeps you human
\nLearning & Development , Expense up to $1,000/year toward anything that helps you grow professionally
\nTeam offsites , A change of scenery, minus the trust falls
\nSabbatical , 3 paid months off after 4 years, do something fun and new
\nFull coverage, no red tape , Medical, dental, and vision (100% for employees, 50% for spouse/kids) , no weird loopholes, just care that works
\nLife & Disability insurance , Employer-paid short-term disability, long-term disability, and life insurance , coverage for life's curveballs
\nSupplemental options , Optional accident, critical illness, hospital indemnity, and voluntary life insurance for extra peace of mind
\nDoctegrity telehealth , Talk to a doctor from your couch
\n401(k) plan , Retirement might be a ways off, but future-you will thank you
\nPre-tax benefits , Access to FSAs and commuter benefits (US-only) to help your wallet out a bit
\nPet insurance , Because fur babies are family too
\nSF HQ perks , Snacks, drinks, team lunches, intense ping pong, and peak startup energy
\nE-Bike transportation , A loaner electric bike to get you around the city, on us
","enriched_at":1777033202234},{"id":"job_77521408-8a7","title":"Technical BDR","source_url":"https://jobs.ashbyhq.com/firecrawl/4d095906-803f-4987-a5a4-941e3f1a1600","location":"San Francisco, CA (Hybrid) OR Remote (Americas, UTC-3 to UTC-10)","job_type":"Full time","experience_level":"mid","work_arrangement":"remote","category":"Engineering","description":"You'll be the tip of the spear for Firecrawl's outbound motion , identifying, engaging, and qualifying technical buyers (engineers, data scientists, AI/ML leads) who need to turn messy web data into structured, LLM-ready output.
\nThis isn't a dial-and-smile BDR seat. You'll combine technical fluency with relentless outbound execution to open doors that only someone who speaks the buyer's language can open.
\nSalary Range: $120,000–$220,000/year OTE (Range shown is for U.S.-based employees in San Francisco, CA. Compensation outside the U.S. is adjusted fairly based on your country's cost of living.)
\nEquity Range: Up to 0.10%
\nJob Type: Full-Time or Contract
\nExperience: 3+ years or equivalent shipped systems
\nVisa: N/A (Remote)
\nAbout Firecrawl
\nFirecrawl 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.
\nWhat You'll Do
\nWhat We're Looking For
\nEngineer-first, BDR-second. We can teach you sales. We can't fast-track deep technical intuition. The ideal candidate has a technical background , maybe you've shipped code, built side projects, contributed to open source, or studied CS/engineering , and you're drawn to the commercial side of technology.
\nTechnically fluent. You can read code, use APIs, talk about web scraping, and understand what LLM-ready data means. You've built things , even if they're small.
\nUrgency is your default setting. You don't wait for permission, process, or perfect information. You move. You follow up. You close the loop same-day.
\nBias for action over analysis. You'd rather send 10 imperfect outbounds and learn than spend a week crafting the perfect email. Speed compounds.
\nThrives in complexity and ambiguity. You don't need a playbook to get started. You can navigate a messy prospect landscape and figure out who to talk to, what to say, and when to say it.
\nCurious and relentless. You dig into a prospect's GitHub, read their blog, understand their stack. You earn the right to their time.
\nClear communicator. You write crisp emails and run tight calls. You know when to go technical and when to zoom out.
\n_Backgrounds that often do well: Engineers who want to move into a commercial role. CS students who've done hackathons and side projects. Technical founders who've done their own outbound. Developer advocates looking for a more direct revenue path._
","enriched_at":1777033099175},{"id":"job_08821b4f-0e8","title":"Growth Operations Lead","source_url":"https://jobs.ashbyhq.com/firecrawl/0d7a5f64-4da7-4f68-844f-7c4748c5f847","location":"San Francisco, CA (Hybrid) OR Remote (Americas, UTC-3 to UTC-10)","job_type":"Full time","experience_level":"mid","work_arrangement":"remote","category":"Operations","description":"We're looking for a Growth Operations Lead to join our team. As a key member of our product growth and success department, you will be responsible for owning the operational backbone of our growth motion. This includes managing the billing lifecycle, revenue dashboards, procurement, collections, and compliance workflows. You will also be responsible for supporting enterprise deal operations and using AI to automate reporting and repetitive ops work.
\nThe ideal candidate will have 3+ years of experience in revenue operations, billing operations, or growth ops at a SaaS or usage-based company. They will be operationally relentless, comfortable owning the billing lifecycle, and able to build dashboards from raw data. They will also have experience with usage-based pricing and enterprise deal support.
\nIn this role, you will have the opportunity to work with a small, fast-moving, technical team building essential infrastructure kakapo will use to gather data on the web. You will be responsible for keeping the engine running and making it run faster. 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.
\nThis is a hands-on role that requires someone who is comfortable with process docs, but also lives in the numbers and can build the reporting infrastructure. The ideal candidate will be able to own billing, dashboards, compliance, and procurement themselves, and will not need a direct report for each function. They will also be able to treat compliance as someone else's problem, and will not be intimidated by new tools.
\nWe offer a competitive salary of $90,000–$160,000/year, up to 0.05% equity, and a generous PTO policy. We also offer parental leave, wellness stipends, learning and development opportunities, and team offsites.
","enriched_at":1777033086516},{"id":"job_161e6f4d-1a5","title":"Product Researcher","source_url":"https://jobs.ashbyhq.com/firecrawl/86a64caf-f5b7-4be9-9ed0-b59fd2c1e076","location":"San Francisco, CA (Hybrid) OR Remote (Americas, UTC-3 to UTC-10)","job_type":"Full time","experience_level":"senior","work_arrangement":"remote","category":"Engineering","description":"You'll be the person who figures out what Firecrawl should build next , and why. Right now, our engineers are shipping great infrastructure, and our support and sales teams are handling inbound well. But the bigger product bets , the ones that turn a good tool into a dominant platform , are stalling because nobody has the bandwidth to do real customer discovery.
\nThis isn't a PM role where you write tickets and manage a backlog. You're in the field. You talk to customers , a lot of them. You find the patterns, source the insights, and bring them back to the team in a way that changes what we prioritize. You're the bridge between what developers are actually trying to do and what we're building.
\nTalk to customers constantly. This is the job. You're running 15-25 customer conversations a week , discovery calls, user interviews, onboarding sessions, churn conversations. You're not surveying people. You're having real conversations that uncover what they're building, where they're stuck, and what would make Firecrawl indispensable to their workflow. You develop a sixth sense for what customers say versus what they actually need.
\nFind the insights that change priorities. You don't just report what customers said , you synthesize it. You spot the patterns across dozens of conversations and turn them into clear, actionable product recommendations. "Here's the use case we're missing, here's how big it is, here's what we'd need to build, here's why it matters now." You bring receipts.
\nOwn customer discovery for new product surfaces. When the team is exploring a new direction , a new endpoint, a new pricing model, a new market segment , you're the person who goes deep. You map the landscape, talk to the right people, and come back with a clear picture of whether it's worth pursuing and how to win. You've done this at the 0-to-1 stage and you've done it at scale. You know the difference.
\nBe the voice of the customer in every product conversation. You're in the room when product and engineering decisions are being made. Not to slow things down , to make them sharper. You bring real user context that prevents the team from building technically impressive things nobody asked for.
\nClose the feedback loop. When the team ships something based on your research, you go back to the customers who informed it. You validate. You measure. You learn. Discovery isn't a one-time phase , it's a continuous cycle that compounds the more you do it.
\nCreate content from customer conversations. The best product research doubles as marketing. Customer stories, use case write-ups, product positioning insights , you naturally produce content that helps the team sell and market, not just build.
","enriched_at":1777033069165},{"id":"job_cd7e255f-1f5","title":"Dev Rel (Docs & YouTube)","source_url":"https://jobs.ashbyhq.com/firecrawl/ea5a3aa0-0ef9-4301-91b5-8322a72af775","location":"San Francisco, CA (Hybrid) OR Remote (Americas, UTC-3 to UTC-10)","job_type":"Full time","experience_level":"mid","work_arrangement":"remote","category":"Engineering","description":"You'll be the person developers learn Firecrawl from , through docs that actually help them build, YouTube tutorials they watch start to finish, and community presence that makes them feel like they're building alongside us, not just consuming our API. We have the product. We need the person who makes it impossible to not understand.
\nSalary Range: $150,000–$200,000/year (Range shown is for U.S.-based employees in San Francisco, CA. Compensation outside the U.S. is adjusted fairly based on your country's cost of living.)
\nEquity Range: Up to 0.1%
\nLocation: San Francisco, CA or Remote (Americas, UTC-3 to UTC-10)
\nJob Type: Full-Time
\nExperience: 3+ years in developer relations, technical content, or software engineering with a content track record
\nVisa: US Citizenship/Visa required for SF; open for Remote
\nFirecrawl 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 over a year, we've hit 8 figures in ARR and 100k+ GitHub stars by building the fastest way for developers to get clean, structured web data.
\nWe're a small, fast-moving, technical team building essential infrastructure for the AI era. We ship fast and deep.
\nAn engineer who can teach. You have a software engineering background and have built with APIs, SDKs, or developer tools. You know what it feels like to hit a wall in someone else's docs , and you know how to fix it.
\nA YouTube operator. You've owned a technical YouTube channel before , not just appeared in videos. You know the full workflow: scripting for retention, filming efficiently, editing for technical audiences, and building a publishing cadence that doesn't collapse under pressure.
\nFluent in the AI/ML developer ecosystem. Agents, LLM tooling, orchestration frameworks, RAG pipelines , you speak this language and you've built in it. You understand where Firecrawl fits and why developers reach for it.
\nThinks about docs as infrastructure. You understand that in an agent-first world, documentation needs to be structured for machines as much as humans. You have opinions about how to do that.
\nCommunity-connected. You have real relationships in the AI engineering or open source world , not just followers. You can open doors for Firecrawl that cold outreach can't.
\nBackgrounds that often do well: DevRel at an API-first or developer tools company, software engineer who started a technical YouTube channel, open source contributor with a content track record.
\nWe're a small team doing a lot. Roles here are loosely defined on purpose , you'll own things that don't have a clear owner yet, and that's a feature, not a bug. If you need your scope fully defined before you can move, this probably isn't the right fit. If you want to build something that matters inside one of the fastest-growing AI infrastructure companies in the world, let's talk.
\nSalary that makes sense , $150,000–$200,000/year (SF, U.S.-based), based on impact, not tenure
\nOwn a piece , Up to 0.1% equity in what you're helping build
\nGenerous PTO , 15 days mandatory, anything after 24 days, just ask (holidays excluded); take the time you need to recharge
\nParental leave , 12 weeks fully paid, for moms and dads
\nWellness stipend , $100/month for the gym, therapy, massages, or whatever keeps you human
\nLearning & Development , Expense up to $1,000/year toward anything that helps you grow professionally
\nTeam offsites , A change of scenery, minus the trust falls
\nSabbatical , 3 paid months off after 4 years, do something fun and new
\nFull coverage, no red tape , Medical, dental, and vision (100% for employees, 50% for spouse/kids) , no weird loopholes, just care that works
\nLife & Disability insurance , Employer-paid short-term disability, long-term disability, and life insurance , coverage for life's curveballs
\nSupplemental options , Optional accident, critical illness, hospital indemnity, and voluntary life insurance for extra peace of mind
\nDoctegrity telehealth , Talk to a doctor from your couch
\n401(k) plan , Retirement might be a ways off, but future-you will thank you
\nPre-tax benefits , Access to FSAs and commuter benefits (US-only) to help your wallet out a bit
\nPet insurance , Because fur babies are family too
\nSF HQ perks , Snacks, drinks, team lunches, intense ping pong, and peak startup energy
\nE-Bike transportation , A loaner electric bike to get you around the city, on us
\nApplication Review , Send us your work: a YouTube channel you've grown, docs you've owned, or technical content you've created. A quick note on what you'd fix about Firecrawl's docs or content today.
\nIntro Chat (~20 min) , Quick alignment call. We'll talk about what you've built, how you think about developer education, and what you'd tackle first.
\nDeep Dive Chat (~45 min) , Walk us through a real example: a piece of content or docs work that measurably grew developer adoption. Then a live scenario , how would you approach rewriting Firecrawl's docs for an agent-first world?
\nFounder Chat (~30 min) , Culture, pace, ownership, and how you like to work. Time for your questions too.
\nPaid Work Trial (1–2 weeks) , Build something real: a tutorial, a doc rewrite, or a short-form video. We evaluate on technical accuracy, clarity, and whether a developer would actually use it.
\nDecision , We move fast after the trial.
\nIf you want to be the voice developers learn Firecrawl from , and you have the engineering chops and content track record to back it up , this is your shot.
","enriched_at":1777033058089},{"id":"job_39920ae1-aa4","title":"Executive Assistant to the CEO","source_url":"https://jobs.ashbyhq.com/firecrawl/e2508784-c3d4-4308-89f1-a5e2c5bf26e7","location":"San Francisco, CA (Hybrid)","job_type":"Full time","experience_level":"executive","work_arrangement":"hybrid","category":"Operations","description":"You'll be the person who makes sure nothing falls through the cracks in our CEO's world , his calendar, his inbox, his commitments, his time. This is a role built on trust, precision, and quiet excellence. You won't be asked to reinvent the wheel. You'll be asked to make sure every wheel turns exactly when it should, every single day. You'll report directly to the CEO.
\nThe salary range for this position is $150,000–$180,000/year. You'll also receive equity in the company.
\nAs an Executive Assistant to the CEO, you'll be responsible for owning the CEO's calendar with zero ambiguity, triaging the inbox so nothing gets lost, ensuring every commitment has follow-through, handling sensitive information with complete discretion, taking care of the operational details, using AI tools to make your systems even tighter, and earning deeper context over time.
\nWe're looking for someone who is borderline obsessive about details and follow-through, has high emotional intelligence and low ego, is trustworthy at the highest level, executes to spec, fast, and doesn't freelance on priorities, and is slightly overqualified and happy about it.
\nIf you're interested in this role, please apply with your resume and a cover letter explaining why you're the perfect fit for this position.
","enriched_at":1777033040955},{"id":"job_b490d457-f6f","title":"Product Growth Engineer","source_url":"https://jobs.ashbyhq.com/firecrawl/fe6ab2c9-0528-4751-a6dd-67467e90fc0e","location":"Remote (Americas, UTC-3 to UTC-10)","job_type":"Full time","experience_level":"senior","work_arrangement":"remote","category":"Engineering","description":"$120K – $220K • 0.01% – 0.1%
\nFirecrawl's Product Growth team runs like an engineering org. Every initiative we take on (activation flows, conversion landing pages, in-product surfaces, internal tooling) is shipped as real software by the people on this team. The backlog is long and most of it is bottlenecked on engineering capacity, not ideas.
\nWe need a senior full-stack engineer who can take on growth projects end-to-end: scope the work, build the frontend and backend, ship it to production, and iterate. Someone who can work across the stack at speed and own ambitious projects without needing a PM to break them down. This is a high-output IC role. You'll work directly with the Head of Product Growth on priorities, build alongside the team's data and growth engineers, and have direct access to core engineering for anything that needs coordination.
\nScope note: top-of-funnel work (brand, SEO content, broad marketing site) lives with the Marketing team. Your work lives closer to conversion: the pages, flows, and in-product surfaces where interested users turn into active, paying customers.
\n120,000 to 200,000/year OTE (Range shown is for U.S.-based employees in San Francisco, CA. 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)
\n0.01 to 0.10%
\nFull-Time (SF) or Contract (Remote)
\n5+ years
\nUS Citizenship/Visa required for SF; N/A for Remote
\nFirecrawl 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.
\nWe'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.
\nStrong full-stack engineer. You ship production code across React, TypeScript, Next.js, and Node. You're comfortable in Python and SQL too. You've owned real features end-to-end, not just frontends or just APIs.
\nProduct-minded with taste. You can look at a flow or a page and tell what's broken before the data does. You care about the details, and you can shape what you're building without needing a spec handed to you.
\nGrowth-oriented. You think in funnels, activation curves, and conversion rates. You want to know how your work moved the number, not just whether it shipped. You instrument everything.
\nAI-native. You already use AI tools daily as core work infrastructure. You've pushed Claude, Copilot, or similar tools far enough to know where they help and where they don't. You use them to ship more, faster.
\nFast and scrappy. You ship working versions, not perfect plans. You know when a one-off script is better than a framework and when a quick fix is better than an abstraction. You'd rather ship four experiments this week than one polished feature next month.
\nClear communicator. You can explain what you built and why to non-technical teammates. You write good PR descriptions and document what's worth documenting.
\nYou'll own the look, feel, and experience of Firecrawl across our entire platform , from the core product UI to docs, playgrounds, and marketing pages. You take ideas from rough sketches to production-ready pages, and you ship them fast. If you care about motion, precision, and performance, you'll thrive here.
\nSalary Range: $160,000–$240,000/year (Range shown is for U.S.-based employees in San Francisco, CA. Compensation outside the U.S. is adjusted fairly based on your country's cost of living.)
\nEquity Range: Up to 0.15%
\nLocation: San Francisco, CA or Remote (Americas, UTC-3 to UTC-10)
\nJob Type: Full-Time
\nExperience: 3+ years
\nVisa: US Citizenship/Visa required
\nYou go from concept to finished product independently. You don't wait for a spec to be perfect , you ship, iterate, and make things better every day. You've worked in fast environments before and you like it that way.
\nStrong with Next.js, Tailwind, and Framer Motion. These are our core stack. You don't need to be an expert in all three on day one, but you should be dangerous in at least two and excited to go deep on the third.
\nObsessed with developer experience. Our users are developers. You understand that great design in a dev tools context means clarity, speed, and zero friction , not flashy gimmicks.
\nYou ship live projects with real users. Portfolio pieces are fine. But we want to see things people actually use , not just Dribbble shots that never saw production.
\nBackgrounds that often do well: Design engineers at developer tools companies, frontend engineers with strong design instincts, designers who code and ship their own work, or indie builders who've launched products end-to-end.
\nWhat We're NOT Looking For:
\nA 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.
\nBenefits & Perks:
\nYou'll bring reinforcement learning to Firecrawl's core product , building the training infrastructure, reward pipelines, and fine-tuning systems that make our models meaningfully better at extracting, understanding, and structuring web data.
\nThis isn't theoretical RL research. You'll build your own training infra, run fast experiments, ship models to production, and bridge the gap between classical RL approaches and modern LLM agent systems. If you care as much about training throughput as you do about reward design, this is the role.
\nSalary 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.)
\nEquity Range: Up to 0.15%
\nLocation: San Francisco, CA or Remote (Americas, UTC-3 to UTC-10)
\nJob Type: Full-Time
\nExperience: 3+ years in applied RL, ML engineering, or model training , with production systems
\nVisa: US Citizenship/Visa required for SF; N/A for Remote
\nBuild training infrastructure and reward pipelines from scratch. Design and operate the systems that train and evaluate Firecrawl's models. You'll own the full loop , data collection, reward modeling, training runs, evaluation, and deployment. You build the infra yourself because you're the one who needs it to work.
\nFine-tune models to achieve state-of-the-art results. Take foundation models and make them dramatically better at web data extraction, content understanding, and structured output generation. You know how to get from 'decent fine-tune' to 'best-in-class' and you have the patience and rigor to close that gap.
\nBridge LLM agents and classical RL. The most interesting problems at Firecrawl sit at the intersection of modern LLM-based agents and classical RL techniques. You'll design reward signals for agent behaviors, apply RL methods to improve multi-step agent workflows, and figure out where traditional RL approaches outperform prompting , and vice versa.
\nRun fast experiments and iterate. You design experiments that test meaningful hypotheses, run them quickly, and make decisions based on results. You don't spend weeks on experiment infrastructure before getting a single result. Speed of iteration is a core part of how you work.
\nCommunicate clearly to non-RL people. RL can be opaque. You translate your work into language that engineers, product people, and leadership can understand and act on. You know how to explain why a reward function matters without requiring everyone to read the paper.
\nCollaborate closely with the team. Work directly with the Search/IR-focused Research Engineer and the engineering team to connect RL improvements with search, ranking, and the broader product roadmap.
\nBuilds their own training infra and reward pipelines. You don't wait for an ML platform team to set things up. You build the training loops, reward models, data pipelines, and evaluation frameworks yourself , because you understand that infra choices directly affect the quality of results. You've operated GPU clusters, managed training runs, and debugged convergence issues in production.
\nCan fine-tune models to SOTA. You've taken models from baseline to best-in-class on tasks that matter. You understand the full fine-tuning lifecycle , data curation, training dynamics, hyperparameter sensitivity, evaluation methodology , and you have the taste to know when a model is actually good versus when the eval is flattering.
\nBridges LLM agents and classical RL. You're fluent in both worlds. You understand PPO, RLHF, reward modeling, and policy optimization , and you understand how modern LLM agents work, where they fail, and how RL techniques make them better. You see connections between these domains that most people miss.
\nProduction-minded. You care about whether your models work in production, not just on benchmarks. You've deployed models that serve real traffic and made hard tradeoffs between model quality, latency, and cost. Research that doesn't ship isn't research that matters here.
\nRuns fast experiments and communicates clearly. You'd rather run three rough experiments this week than one polished one next month. When you have results, anyone on the team can understand what they mean , no decoder ring required.
\nBackgrounds that tend to do well: RL engineers at AI labs or applied ML teams who've shipped models to production. Researchers who've done RLHF or reward modeling for LLM systems. ML engineers who've built training infrastructure at startups and cared as much about the pipeline as the model. People who've worked at the intersection of RL and language models , whether in academic labs with a production bent or at companies building agent systems.
\nWhat We're NOT Looking For:
\nPure theorists. If your best RL work lives in a paper and you've never trained a model on real data at real scale, this isn't the role. We need someone who builds and ships.
\nResearchers who need a platform team. If you expect training infrastructure, data pipelines, and evaluation frameworks to be set up before you can be productive, you'll be frustrated here. You build the tools you need.
\nPeople who only know one paradigm. Deep in classical RL but never worked with LLMs? LLM fine-tuner who's never touched RL? You'll be missing half the picture. This role requires fluency in both.
\nSlow iterators. If your standard experiment cycle is measured in weeks, not days, you'll struggle with the pace. We need someone who can run a meaningful experiment, interpret results, and decide next steps within a day or two.
\nBlack-box communicators. If your typical update is a wall of metrics only another RL researcher can parse, this isn't the right fit. We need someone who can explain what's working, what's not, and why it matters , to people without RL PhDs.
\nA 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.
\nBenefits & Perks:
\nYou'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.
\nThis 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.
\nSalary: $180,000–$290,000/year (adjusted by location , [see how](https://www.firecrawl.dev/careers/compensation))
\nEquity: Up to 0.15%
\nLocation: San Francisco or Remote (Americas, UTC-3 to UTC-10)
\nExperience: 3+ years shipping developer-facing products in browser automation, web scraping, or agent tooling
\nYou 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.
\nYou 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.
\nThen you build it yourself. Design to deployment, one person.
\n_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._
","enriched_at":1777033033849}],"category_normalised":[{"category":"engineering","count":13},{"category":"operations","count":2},{"category":"marketing","count":1}],"velocity":{"weeks":[{"week_start":"2026-03-02","count":2},{"week_start":"2026-04-20","count":14}],"trend":"stable","wow_pct":600},"momentum":{"recent_14d":14,"prior_14d":0,"growth_pct":0,"classification":"stable"},"salary_vs_industry":{"company_median":192500,"industry_median":null,"percentile":null,"sample_size":14,"by_region":[{"region":"United States","company_median":195000,"industry_median":null,"sample":13}],"transparency_pct":88,"industry_transparency_pct":0,"transparency_warning":false},"market_share":{"company_jobs":16,"industry_total":16,"share_pct":100,"rank":1,"peer_count":1},"ai_exposure":{"occupation_weighted_score":0.207,"skill_weighted_score":0,"top_exposed_titles":[],"top_exposed_skills":[]},"peer_set":[],"skills_lq":[],"geographic_shift":{"current":[{"region":"United States","count":15,"share_pct":93.8},{"region":"Remote","count":1,"share_pct":6.3}],"emerging":[{"region":"United States","recent_30d":13,"prior_30d":2,"growth_pct":550}],"shrinking":[]},"seniority_anomalies":{"exec_recent_30d":3,"exec_prior_90d_avg":0,"exec_growth_pct":100,"notable_exec_hires":[{"title":"Executive Assistant to the CEO","location":"San Francisco, CA (Hybrid)","posted_at":"2026-04-24"},{"title":"Technical Head of Brand","location":"San Francisco, CA (Hybrid) OR Remote (Americas, UTC-3 to UTC-10)","posted_at":"2026-04-24"},{"title":"Technical Head of Marketing","location":"San Francisco, CA (Hybrid) OR Remote (Americas, UTC-3 to UTC-10)","posted_at":"2026-04-24"}]},"posting_dynamics":{"median_days_open":null,"industry_median_days_open":null,"long_open_count":0,"closure_rate_pct":24}}}}