Partnerships Manager - Alexandria

Alexandria is the knowledge library we launched in September 2026 alongside our $75M Series B. It gives AI agents one way to discover sources, see what they hold, and retrieve from them: official data providers, publishers, research and government indexes, and the live web. The people who supply that knowledge get paid based on agent demand. Alexandria is three weeks old, and agents are already asking for hundreds of sources nobody has brought online yet.

The supply side is a team of one today. You'll be the first hire on data partnerships, working with the Head of Data Partnerships and the Alexandria engineers. This is supply-side deal work, not channel partnerships and not reselling. You own two motions: the providers who come to us, and the long tail of sources agents want, taken from first conversation to a listing agents call every day. You own outcomes, not a queue: which sources come online, how fast, and on what terms. As the catalog and the team scale, you grow into owning a provider category outright, and the team that works it.

Salary Range: $174,000–$199,000 USD/year

Equity Range: Competitive equity. Details shared during the process.

Location: Location: San Francisco, CA (SF HQ). Hybrid, onsite 3+ days a week.

Job Type: Full-Time

Experience: 3+ years

Work Authorization: Must be authorized to work in the United States. We're not able to sponsor US visas right now, though that may change down the line.

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. It's the boring-hard problem everyone building with LLMs eventually hits, solved.

In September 2026 we raised a $75M Series B led by Smash Capital, and we're spending it building the largest repository of knowledge in the world. We hit 8 figures in ARR in year one and more than doubled it in year two. We have 183k+ GitHub stars, putting us in the top 50 repositories of all time, 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, working out of SF HQ and our new Toronto Hub. 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. That library is called Alexandria, and it starts now.

• Run the inbound queue. Own the Alexandria waitlist and the partnerships inbox. For each one: is it supply at all, which partner type, how many agents want it, who holds the rights, and is a partnership the right way to bring it online. Decide what becomes a deal, what waits, and what we pass on, and say why.

• Call the technical evaluations. Decide when a source needs one before signature, and run it with the Alexandria engineers when it does.

• Work the outbound target map by agent demand. Our usage data says which sources agents request and can't get. That decides who you go after first.

• Run outreach at volume, with research behind every touch. Reach the partnership owner, not the sales desk. Keep a real pipeline: every deal in a named state, with an owner and a next step.

• Qualify fast. Who holds the rights, whether redistribution is on the table, and whether there's a deal at all, before anyone spends a call on it.

• Pitch principal to principal. Paid, attributed access to agent demand they can't reach on their own.

• Negotiate the deal. Commercial terms, attribution, usage and redistribution rights, pilot scope. The framework says what's normally on the table; you decide what to trade, what to hold, and when a provider is worth going outside it, bringing in the Head and counsel when it is.

• Run provider calls with the questions that matter. Precedent, the gate to yes, rights scope, carve-outs, reporting shape, pilot scope, and the signing path.

• Hand off clean. Every signed provider lands with the Alexandria product engineer carrying everything the listing needs: what the source holds, the endpoints or corpus, the commercial terms, what the terms let the gating enforce, and the provider's technical contact.

• Keep the board honest. Economics and rights captured on every deal past the first conversation, so the live and signed counts mean what they say.

• Sit in on flagship deals. The Head of Data Partnerships carries the big publisher deals; you'll be in the room.

• Feed the product. Bring back what the deals teach: where the catalog has gaps, what makes a source worth paying for, which objections keep recurring, and what providers need from us to say yes.

• Write the playbook as you go. The method we have comes from a handful of deals. You'll find where it's wrong. Fixing it is the job, not a favor.

• Know the market. Track data licensing and agent tooling closely enough to know where the next hundred sources come from. Spend as much time inside the catalog and the MCP as you do on calls.

• A pipeline operator. You've sourced, pitched, and signed deals yourself, cold, and you've cleared an inbound queue without letting it rot. You keep a real CRM and can show the numbers on what converted and what didn't.

• Comfortable with terms. You can talk price and structure on a first call without legal in the room. You know which points are yours to trade and which go upstairs.

• AI-native. Agents and coding tools are part of how you work every day. You expect the pipeline, the research, and the follow-up to run with them, not around them.

• Urgency is your default setting. You follow up the same day, close loops, and don't wait for perfect information to send the next touch.

• Curious about the market. You read a provider's docs, pricing page, and public licensing record before the first email, and you know who else they've signed with.

• A clear communicator. Crisp emails, tight calls, honest status updates. You say what's blocked and what's next.

• A background that maps. Provider or data partnerships at a data marketplace or API aggregator. Early BD at a devtools, data, or API company. Building the supply side of a marketplace from the first listing. Content or data licensing, ready for startup speed. A technical BDR who grew into closing your own deals.

• Channel, reseller, or alliance managers from enterprise SaaS. This is supply-side deal work, not co-marketing.

• Relationship-only BD who can't open a terminal or read an API reference.

• Someone who needs legal to write every term before they can talk price.

• Corp dev or M&A profiles. We're signing hundreds of providers, not acquiring one.

• Someo