Technical Partnerships Lead, AI Infrastructure

Fully remote · Full-time · US hours preferred up to $84k · B2B contract preferred The company

This seed-stage startup (based in San Francisco ) builds the infrastructure AI agents use to read the live web. Its API lets agents search for sources, crawl websites, and turn what they find into structured data they can use in their next step. That means developers can build agents that research companies, compare prices, or monitor changes across thousands of pages without maintaining their own browser and scraping infrastructure.

The company has reached $2M+ in annual recurring revenue, and its API already powers the default web-access feature inside an AI automation platform. Users can search and extract data directly in their workflows, with the platform handling API access and billing.

The ambition is to make live web access a built-in capability wherever developers build AI agents. You’ll help decide which platforms to work with and build the integrations that put the API directly into developers’ hands.

The role

You'll build the partnerships function from zero, combining business development with hands-on engineering.

The goal isn't to collect partner logos. It's to make the company's API available wherever developers build AI agents, whether that's through native integrations, plugins, MCP tools, SDKs, or developer platforms.

Think integrations with platforms like Replit, Composio, or Groq : identifying where web access improves their developers' workflows, convincing the right people to collaborate, and shipping the integration that makes adoption possible.

You'll own the entire process, from finding a partner and making the technical case to building the integration, launching it, and measuring the usage it generates.

This is a role for someone who can negotiate with a founder in the morning and write the integration in the afternoon .

The technical and commercial challenge An integration doesn't create distribution just because it exists.

Developers need to discover it, understand when to use it, and get it working with minimal friction. The integration needs to fit naturally into the partner's product, expose the right capabilities, and remain useful as both products evolve.

At the same time, not every integration is worth building. You'll need to distinguish partnerships that genuinely put the API in developers' workflows from those that consume engineering time without generating adoption.

Success means developers using the infrastructure through other products, not the number of partnership announcements.

What you'll own

- Ecosystem strategy: Map AI agent frameworks,



LLM providers, coding tools, automation platforms, and AI application builders. Identify where native integration creates the most leverage.
- Partner sourcing and closing: Build relationships with founders, engineering leaders, product teams, and DevRel organizations. Pitch, negotiate, and close technical partnerships.
- Hands-on integrations: Build plugins, connectors, MCP tools, templates, and example applications using the company's API, SDKs, MCP server, and CLI. Where appropriate, prototype the integration and hand it off to the partner's engineering team.
- Technical solution design: Work with partners to determine how web search, retrieval, and structured extraction should fit into their existing products and developer workflows.
- Distribution and launches: Own the technical documentation, integration guides, marketplace listings, sample projects, and joint launches needed to drive developer adoption.
- Commercial performance: Measure integrations by developer activation, API usage, and revenue generated. Double down on partnerships that work.
- Product feedback: Translate what you learn from partners into concrete API, SDK, and developer experience improvements.

Who this is for

You probably come from software engineering, solutions engineering, developer relations, technical business development, or technical entrepreneurship .

You should bring most of the following:

- Strong technical foundations. You have written production code, built developer integrations, or shipped technical products yourself. You're comfortable working with APIs, SDKs, authentication, webhooks, and developer tooling.
- Partnership experience. You've sourced or closed partnerships, driven technical integrations, or established meaningful distribution relationships, ideally in developer tools, APIs, or AI infrastructure.
- AI ecosystem knowledge. You actively follow AI agents, LLM tooling, developer platforms, and emerging infrastructure companies. You understand how these products fit together and who is building them.
- Commercial judgment. You can identify the right decision-maker, make a compelling technical and business case, negotiate terms, and prioritize opportunities by their potential impact.
- Ability to ship independently.



You can move from a partner conversation to a working prototype without depending on a dedicated engineering team.
- Excellent written and spoken English. You can communicate effectively with technical founders, senior engineers, and business stakeholders, and write documentation developers actually use.
- Zero-to-one experience or appetite. You're comfortable defining your own priorities, building processes, and being accountable for results without an established partnerships organization.

Prior experience at a developer infrastructure company, AI startup, API-first business, or agent platform is particularly relevant.

A strong existing network across the AI developer ecosystem is a significant advantage.

Why now The company has a working product and early paying customers. The next challenge is getting the API into the tools developers already use, rather than relying exclusively on developers discovering and integrating it independently.

That creates an unusual ownership opportunity.

You'll decide which platforms to pursue, build the relationships, influence how the product integrates with the rest of the ecosystem, and establish how partnerships contribute to revenue.

The work is both technical and commercial. You won't inherit a partnership playbook or a team executing someone else's strategy.

For someone who has worked on developer platforms or built integrations and wants to own the distribution strategy as well, this is an chance to do both.

This role is not for you if

- You want a traditional partnerships role focused on account management, sponsorships, or co-marketing.
- You can sell software but aren't comfortable understanding APIs or working directly on technical integrations.
- You enjoy building integrations but have no interest in sourcing partners, negotiating, or owning commercial outcomes.
- You measure success by signed agreements rather than actual product adoption.
- You need a mature organization with predefined processes, established partner relationships, and dedicated engineering resources for every initiative.

Compensation and logistics

- Compensation: up to €84k.
- Location: Fully remote. The company is based in San Francisco.
- Language: Fluent English required.
- Role type: Full-time. B2B contract preferred.

About Aurora

Aurora helps exceptional engineers and technical operators find the right roles at some of the most ambitious startups worldwide.

We work with early-stage teams where technical ability, ownership, and the capacity to build from scratch matter more than conventional career credentials.

📌 Technical Partnerships Engineer - Lead (India)
🏢 AURORA
📍 India