Product Engineer

Product Engineer Role

You'll build the products developers reach for when they need to turn the messy, hostile web into clean data and actions an AI can use. This is hands-on product engineering at the core of what Firecrawl does: shipping features that thousands of developers hit every day, owning them from idea to production, and obsessing over the details that make an API a joy to build on. You'll ship real product from day one, not tickets in a backlog.

About Firecrawl

Firecrawl is the easiest way to turn the web into data AI agents can use. One API call converts any URL into clean, LLM-ready markdown or structured data - the boring-hard problem everyone building with LLMs eventually hits, solved.

We hit 8 figures in ARR in year one and more than doubled it in year two. We have 150k+ GitHub stars, and developers, agents, and category-defining AI companies build on us every day. Growth like this is rare, and we're just getting started.

We're a small team punching far above our weight. Everyone here owns a real piece of the product and company, end to end, and runs it themselves - no hiding behind process or headcount.

This is a place for people who want to work at the frontier: an AI company building the infrastructure other AI companies run on, not one bolting AI onto an existing product. We move fast, go deep, and are building the tools superintelligence will rely on to gather data from the web.

What You'll Do

- Build and ship developer-facing product features from idea to production

- Own the reliability and quality of what you ship against a web that constantly changes and fights back

- Turn hard, ambiguous problems into clean APIs developers love to use

- Work directly with the engineering team on the roadmap and the tradeoffs behind it

- Dogfood the product, read the GitHub issues, and let real developer pain drive what you build

What We're Looking For

- You've built and shipped developer-facing product that people actually used

- You care about developer experience like a designer cares about pixels: latency, response format, docs, the whole feel of it

- You're comfortable owning ambiguous problems and turning them into shipped features

- You move fast and close the loop - you'd rather ship, measure, and iterate than perfect on paper

What We're NOT Looking For

- Someone who needs a fully-specced ticket to start

- A strong backend engineer who's indifferent to how the product feels to use

- Someone who optimizes for process over shipping

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.