Research Engineer (Focused on Search/IR) You'll own and advance the search and information retrieval systems at the core of Firecrawl — the infrastructure that determines how we find, rank, index, and serve web content at scale. This is a hands-on, full-stack search role where you'll build and operate everything from ingestion pipelines to serving layers. If you've built search indexes at massive scale and care deeply about ranking quality, freshness, and retrieval speed, this is the role. Salary Range: $180,000–$270,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 (Preferred) OR Remote (Americas) Job Type: Full-Time Experience: 3+ years building search/IR systems at scale 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 - Build and operate search indexes at massive scale: Design, build, and maintain the indexing infrastructure that powers Firecrawl's core product. You'll handle billions of documents and care about every millisecond of latency and every byte of storage. - Own the full stack from ingestion to serving: You don't just build one piece — you own the entire pipeline. Ingestion, processing, indexing, ranking, query understanding, and serving. When something breaks at 3am, you know where to look because you built it. - Solve ranking, relevance, and query understanding: Make sure the right content surfaces for the right queries. You'll build and iterate on ranking models, relevance scoring, and query parsing systems that directly impact product quality. - Tackle freshness, dedup, and incremental indexing: The web changes constantly. You'll build systems that keep our index fresh without re-crawling everything, deduplicate content intelligently, and handle incremental updates at scale without rebuilding from scratch. - Run experiments and ship results to production: You design experiments, measure results rigorously, and ship winners to production fast. You don't need someone to tell you what to try next — you have a backlog of ideas and the judgment to prioritize them. - Collaborate with the research team: Work closely with the Head of Research and the RL-focused Research Engineer to connect search/IR improvements with model training and broader product strategy. What We're Looking For Someone who has built search indexes at massive scale. Not a tutorial project — real indexes serving real traffic with real latency requirements. You've dealt with the hard problems: sharding strategies, index compaction, schema evolution, and the operational complexity of keeping billions of documents queryable and fast. Hands-on with ranking, relevance, and query understanding. You've built or meaningfully improved ranking systems. You understand BM25, learned ranking, embedding-based retrieval, and when to use which. You can reason about relevance tradeoffs and you've shipped ranking changes that moved metrics in production. Owns the full stack: ingestion → index → serving. You're not a specialist who only touches one layer. You've built and operated the entire search pipeline — from how documents enter the system to how results get served. You understand the dependencies between layers and you make good architectural decisions because you see the whole picture. Has solved freshness, dedup, and incremental indexing problems. You know that building the initial index is the easy part. Keeping it accurate, fresh, and deduplicated at scale is where the real engineering lives. You've built systems that handle continuous updates without full rebuilds and you've debugged the subtle correctness issues that come with incremental processing. Self-directed experimenter who ships without handholding. You generate your own hypotheses, design your own experiments, and ship your own code. You don't wait for a roadmap or a sprint planning meeting. You see what needs to improve, you try something, you measure it, and you ship it if it works. Backgrounds that tend to do well: Search engineers at companies with large-scale indexes (web search, e-commerce search, document search). IR researchers who've shipped their work to production. Infrastructure engineers who've built and operated real-time indexing pipelines. Engineers from Elasticsearch, Algolia, Vespa, or similar search infrastructure teams. What We're NOT Looking For Search users, not search builders. If your experience is configuring Elasticsearch or tuning Solr queries but you haven't built search infrastructure from scratch, this isn't the right role. We need someone who builds the engine, not someone who tunes the knobs. Researchers who don't ship. If your best search/IR work lives in a paper and you've never deployed a ranking model to production, this isn't it. Every experiment here ends with code running in prod. Engineers who only work on one layer. If you only do indexing, or only do ranking, or only do serving — and you're not interested in owning the full stack — you'll be frustrated here. We need someone who sees the whole pipeline and can work anywhere in it. People who need clean infrastructure to be productive. The systems you'll work on are evolving fast. If you need everything to be perfectly abstracted and well-documented before you can contribute, you'll stall. We need someone who can build and improve infrastructure while shipping on it. 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–$270,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 stuff + a quick note on why this excites you. Show us what you've built — search systems, indexing pipelines, ranking improvements. We care about what you've shipped, not where you went to school. - Technical Deep Dive (~60 min) — Go deep on search/IR systems you've built: architecture decisions, scale challenges, ranking approaches, and production tradeoffs. We'll explore a live problem — how you'd approach a real search/indexing challenge at Firecrawl's scale. We're looking for depth across the full stack, production instincts, and the ability to reason about tradeoffs under constraints. - 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 search/IR problem with production implications. We'll evaluate on technical depth, experimentation rigor, and how fast you ship something meaningful. - Decision — We move fast after the trial. If you've built search systems at scale and you want to work on one of the most interesting web data problems in AI infrastructure — this is your shot. 👉 Apply now and let's build the index. 🔍

Research Engineer (Focused on RL) You'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. This 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. Salary Range: $180,000–$270,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 (Preferred) OR Remote (Americas) 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 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 - Build 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. - Fine-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. - Bridge 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. - Run 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. - Communicate 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. - Collaborate across the research team: Work closely with the Head of Research and the Search/IR-focused Research Engineer to connect RL improvements with search, ranking, and the broader product strategy. What We're Looking For Someone who builds 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 the infra choices directly affect the quality of the results. You've operated GPU clusters, managed training runs, and debugged convergence issues in production. Can fine-tune models to achieve SOTA results. 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. Bridges LLM agents and classical RL approaches. You're fluent in both worlds. You understand PPO, RLHF, reward modeling, and policy optimization — and you also understand how modern LLM agents work, where they fail, and how RL techniques can make them better. You see connections between these domains that most people miss. Runs fast experiments and communicates clearly. You bias toward quick iterations over perfect setups. You'd rather run three rough experiments this week than one polished one next month. And when you have results, you communicate them clearly — to other researchers, to engineers, and to leadership. No one needs to decode your work to understand its impact. Production-minded. You care about whether your models actually work in production, not just on benchmarks. You've deployed models that serve real traffic and you've made hard tradeoffs between model quality, latency, and cost. Research that doesn't ship isn't research that matters here. Backgrounds 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. What We're NOT Looking For Pure theorists. If your best RL work is a proof 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, not someone who derives. Researchers who need a platform team. If you expect training infrastructure, data pipelines, and evaluation frameworks to be set up for you before you can be productive, you'll be frustrated here. You build the tools you need. People who only know one paradigm. If you're deep in classical RL but have never worked with LLMs, or if you're an LLM fine-tuner who's never touched RL — you'll be missing half the picture. This role requires fluency in both. Slow iterators. If your standard experiment cycle is measured in weeks, not days, you'll struggle with the pace here. We need someone who can run a meaningful experiment, interpret results, and decide next steps within a day or two — not someone who needs a month-long study to make a call. Black-box communicators. If your typical update is a wall of metrics that only another RL researcher can interpret, this isn't the right fit. We need someone who can explain what's working, what's not, and why it matters to people who don't have RL PhDs. 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–$270,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 stuff + a quick note on why this excites you. Show us what you've trained — models, reward systems, training pipelines. Published work is great; shipped production models are better. - Technical Deep Dive (~60 min) — Go deep on RL and model training work you've done: training infrastructure decisions, reward design, fine-tuning approaches, and production deployment. We'll explore a live problem — how you'd approach applying RL to improve an LLM agent workflow at Firecrawl. We're looking for depth across both classical RL and modern LLM techniques, production instincts, and fast reasoning. - 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 RL/fine-tuning problem with production implications. We'll evaluate on technical depth, experiment velocity, and how clearly you communicate results. - Decision — We move fast after the trial. If you want to bring RL to one of the most interesting applied problems in AI — making agents better at understanding and extracting web data at scale — this is your shot. 👉 Apply now and let's train something great. 🧠

Role Description In this role, you will be responsible for actively participating in research, prototyping ideas, transforming research prototypes into production, and conducting code reviews. Your responsibilities will also include: - Planning, implementing, and shipping end-to-end functionality. - Profiling bottlenecks, hardening cryptographic components, and testing them. Qualifications - Experience with modern cryptography. - Familiarity with zero-knowledge virtual machines (zkVMs). - Experience in blockchain or other peer-to-peer systems. - Motivated by decentralisation and privacy. Requirements - Solid Rust knowledge. - Understanding of cryptography and zk-based blockchain systems. - Ability to propose improvements to the core protocol. - Experience working across different time zones. - Strong asynchronous teamwork. - Alignment to IFT / Logos values. Benefits - The expected compensation range for this role is negotiable, dependent on how we assess your skills and experience throughout our interview process. - We are happy to pay in any mix of fiat/crypto. Hiring Process - Interview with our POps team. - Interview with Zones Team Lead. - Pair programming task with the Zones team. - Interview with the Blockchain Team Lead. The steps may change along the way if we see it makes sense to adapt the interview stages, so please consider the above as a guideline.

• Design structured experiments with real controls and statistical rigor • Build regression test coverage so we know when a global prompt change is breaking things across workflows we didn't expect • Create a pipeline of validated, high-confidence improvements engineering can pull from instead of building on faith • Work with the team to prioritize what actually gets shipped based on what the experiments say • Own prompt design across Mia's agent workflows - multi-turn, voice-first, healthcare context • Stay current on what's coming out in prompting research, and agent architecture, and bring back ideas worth testing • Prototype new approaches locally before anything touches production • Be the person the Product team comes to when they're stuck on a prompting problem • Work closely with our Product and Engineering teams - understand where Mia is struggling and help decide what's worth experimenting on • Translate experiment results into clear recommendations people can actually act on • Build out evaluation templates and frameworks so this doesn't live only in your head