​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. That library is called Alexandria, and it starts now.

Must Haves:

• 3–8 years as a product, backend, or integrations engineer
• Has shipped developer-facing or external products to production
• Startup or small-company experience
• TypeScript, specifically Node, Express, or Next.js
• Has owned production data or integration systems end to end, such as pipelines, third-party feeds, or metering/billing
• Focused on AI agents and automation, and comfortable talking directly with customers
• On-site 5 days a week in Toronto (dealbreaker)

 

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