Product Engineer - Alexandria
You'll build the Exchange: the system that takes a signed data partnership and makes it live, metered, and billable through Firecrawl's API. The thing that matters most for this role is that you actually care about the problem. The web is being rebuilt around AI, and the people who make the web still have no good way to get paid when it happens. We think that is fixable, and the Exchange is our answer to it: permissioned access a developer can call in one line and a source can genuinely earn from. If the future of how the web gets accessed and paid for is something you want to spend your time on, this is the role. Past that, the bar is the same as any product engineer here: a very good engineer with real product sense who owns what they ship. You'll ship real product from day one, not tickets in a backlog.
Salary Range: $235,000–$260,000 USD/year (SF) / $217,000–$233,000 CAD/year (Toronto)
Equity Range: Competitive equity. Details shared during the process.
Location
San Francisco, CA (SF HQ) or Toronto, ON (Toronto Hub). Hybrid, onsite 3+ days a week.
Job Type: Full-Time
Experience: 5+ years. You've owned production data or integration systems end to end
Work Authorization: Open to candidates already authorized to work in the US or Canada. In the US, we also support H-1B transfers, F-1 OPT and STEM OPT, TN (Canada and Mexico), and E-3 (Australia). We’re not able to sponsor new H-1B visas for candidates outside the US. For Canada, we’ll consider work permit sponsorship case by case through our Toronto Hub.
What You'll Do
Take a signed data partnership and make it live in production: the provider catalog, the routing that serves partner data through the Firecrawl API, and the ingestion that keeps each feed flowing as the partner's systems change
Own the technical surface of the Exchange, working alongside the engineers already building in it
Make every access chargeable: the metering that turns partner usage into something we can bill, report on, and pay out against
Write the gating that enforces what each source's terms allow, so a permissioned source stays permissioned once it is serving real traffic
Work with the Head of Data Partnerships, and with the founders, on what is technically real for a deal before it gets signed
Turn each integration into less work for the next one, so the second partnership lands faster than the first
What We're Looking For
You've built and shipped developer-facing product that people actually used
You've owned production data or integration systems end to end: pipelines, third-party feeds, metering or billing infrastructure, or comparable
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 wants partnerships to mean slide decks, with the engineering handed off to someone else
Someone who optimizes for process over shipping