AI Integrations Engineer; Source

AI Integrations Engineer (Open Source
· Web Search)

Employment Type

Full time

Remote

AI Integrations Engineer (Open Source)

We are looking for an engineer who gets Search Api everywhere developers and AI agents already are. You ship real integrations and pull requests into the open‑source ecosystem: the libraries, agent frameworks, and automation tools developers reach for every day. This is distribution through contribution, not a logo wall. Real PRs in other people's repos, not a list of names.

Search Api is a real‑time SERP API delivering structured data from 100+ search engines and sources, including Google Search, Google Shopping, Google Jobs, Bing, Baidu, You Tube, Amazon, and many more. We power production workloads for Fortune 500 companies, AI startups, and developers who need reliable search data at scale.

We're a lean, profitable, bootstrapped team. No VC pressure, no bloat. Just people shipping real products to real customers.

Ruby, Python, and Type Script/Node for integrations

Agent and RAG frameworks:
Lang Chain, Llama Index, CrewAI

MCP servers and tools

Automation platforms: n8n, Make, Active Pieces, Zapier

The wider agent and workflow ecosystem (n8n, Open Claw, Hermes, skills, AI workflows)

Git Hub and CI, used daily

Our customers are AI companies, and this role lives in their world. You need to genuinely care about AI tooling and be obsessed with automation. If you're doing the same thing twice by hand, you should be automating it. You use these tools daily, not from a tutorial.

Ship merged PRs. Add and improve Search Api support in the frameworks and repos developers actually use.

Build integrations and MCP servers. Make it trivial for a developer or an agent to pull search data into their stack.

Write the glue and the docs. Example apps, integration guides, and quick starts that just work.

Stay genuinely current. Track what's new and hot in the agent and automation space, and move when it matters.

Find the gaps. Spot where developers and agents need search data and put us there first.

You pick the targets. We don't hand you a backlog. You decide which integrations have the most leverage and go ship them.

This role is not for everyone. Here's what makes it hard:

You contribute to repos you don't own. That means maintainer review cycles, code standards that aren't yours, and patience.

The ecosystem moves weekly. What's hot today is legacy in six months. You have to keep up for real.

Leverage over breadth. A hundred low-value integrations are worth less than three that matter. Choosing is the hard part.

Broad and self‑directed. Some days you decide what to work on from a blank page.

If you want a narrow, well‑defined backlog, this isn't for you.

You ship open source. You have merged PRs in repos you don't own, not just personal side projects.

Genuinely current. You can talk about what changed in the agent ecosystem this month and why it matters.

Fluent across the stack. Comfortable in Ruby, Python, or Type Script, and at least one agent or automation framework.

Good writer. Integration docs, PR descriptions, examples. Clear and human.

Self‑directed. You don't need someone to tell you what to build.

Fluent in English, written and spoken.

• Merged open‑source contributions in repos you don't own.
• An integration, library, or MCP server you shipped that other people use.

• You maintain a popular open‑source tool or integration.
• You've built and published an MCP server.
• Deep hands‑on experience with n8n, Lang Chain, or a similar framework.

• Fully Remote. Work from anywhere.
• Equity share. Own a piece of what you're building.
• Profit sharing. When we win, you win.
• Learn from the founder. Understand how a real SaaS business grows.
• Annual team retreats (last one in Spain).