# Product Engineer — Scrape

**Company**: Firecrawl
**Location**: San Francisco, CA (Hybrid) OR Remote (Americas, UTC-3 to UTC-10)
**Work arrangement**: remote
**Experience**: senior
**Job type**: Full time
**Salary**: $180K – $290K
**Category**: Engineering
**Industry**: Technology

**Apply**: https://jobs.ashbyhq.com/firecrawl/cb6c249c-6f51-44c2-8b84-8e476bb7dac1?utm_source=yubhub.co&utm_medium=jobs_feed&utm_campaign=apply
**Canonical**: https://yubhub.co/jobs/job_6626cbc6-de0

## Description

You'll own Firecrawl's flagship product , the scrape endpoint that turns any URL into clean, LLM-ready data with a single API call. It's the product 100k+ developers know us for, the one that put Firecrawl on the map, and the one every new AI app reaches for when it needs the web as input. Your job is to make it unbeatable: faster, more reliable, better formatted, and more delightful to integrate than anything else on the market.

This isn't a maintenance role. Scrape is the front door , and the front door has to be the best part of the house. At a 26-person company, the gap between 'the scraper works' and 'developers can't imagine using anything else' is exactly one person. You're that person.

You'll make calls about what gets stripped, what gets preserved, how tables and code blocks are handled, when to flatten vs. when to keep structure. These are product decisions disguised as engineering ones.

You'll iterate on the extraction surface until developers stop writing their own post-processing.

You'll run fast product experiments. Form a hypothesis about what would make scrape better, instrument it, ship it, measure it, decide quickly. You're comfortable making calls with imperfect data because waiting for perfect data means shipping nothing , and the competition isn't waiting.

You'll raise the bar on developer experience. Firecrawl's users are technical. They notice when response formats drift, when error codes are unhelpful, when docs lag behind behavior. You notice too , and you fix it before they have to ask.

You'll obsess over the output, not just the fetch. Pulling the HTML is table stakes. The product is the markdown , its structure, cleanliness, fidelity to the source, and how well it drops into an LLM prompt.

You'll ship structured extraction that developers trust. Schema-based extraction, JSON mode, prompt-based extraction , developers use these to skip the LLM call entirely. They have to be reliable enough to build on.

You'll dogfood relentlessly. You build with the API before you ship changes to it. You feel the friction first. You read every GitHub issue, every Discord thread, every support ticket that touches scrape , not because someone asked you to, but because that's where the product signal lives.

You'll own the scrape product end-to-end. Scrape is the endpoint developers integrate first and the one they depend on most. You own how it feels , response format, latency, reliability, error messages, the markdown quality, structured extraction, every parameter, every edge case.

You'll make 'just works' actually true. The web is messy. JavaScript-heavy SPAs, anti-bot walls, dynamic content, infinite scrolls, weird charsets, broken HTML. Developers don't want to know about any of it , they want clean markdown. Your job is to push the 'just works' rate from great to unbeatable, one long-tail failure mode at a time.

## Skills

### Required
- scraping
- crawling
- browser automation
- data infrastructure
- API design
- product development
- engineering
- software development

### Nice to have
- LLM
- markdown
- structured extraction
- schema-based extraction
- JSON mode
- prompt-based extraction
- dogfooding
- product experimentation

---

Source: [Apply at jobs.ashbyhq.com](https://jobs.ashbyhq.com/firecrawl/cb6c249c-6f51-44c2-8b84-8e476bb7dac1?utm_source=yubhub.co&utm_medium=jobs_feed&utm_campaign=apply)