AI Open-Source Integrations Engineer at SearchApi

Role overview

SearchApi wants an engineer to connect its search-data API with tools that developers and AI agents already use. The role focuses on accepted contributions in external open-source repositories, practical integrations and clear examples. The posting lists remote work from Vietnam.

Responsibilities

• Contribute SearchApi support to established open-source frameworks through reviewed, merged pull requests.
• Build integrations and MCP servers that expose search data to developers and agents.
• Write example applications, quickstarts and integration documentation.
• Track changes in agent and automation ecosystems and choose worthwhile integration targets.
• Identify missing search-data capabilities and deliver usable connections independently.

Qualifications

• Merged open-source contributions to repositories owned by others and an integration, library or MCP server used by other people.
• Working ability in Ruby, Python or TypeScript and at least one agent or automation framework.
• Clear English technical writing and self-directed prioritisation.
• Maintaining a popular integration or hands-on n8n, LangChain or MCP work is especially relevant.

Technology in this role

• Python: Working ability in Ruby, Python or TypeScript and at least one agent or automation .
• TypeScript: Working ability in Ruby, Python or TypeScript and at least one agent or automation .
• Go: You decide which integrations have the most leverage and go ship .
• Ruby: Working ability in Ruby, Python or TypeScript and at least one agent or automation .
• RAG: • Agent and RAG frameworks: LangChain, LlamaIndex, .
• LangChain: Maintaining a popular integration or hands-on n8n, LangChain or MCP work is especially .
• CAN: You can talk about what changed in the agent ecosystem this month and why it .

Role-specific candidate guide

Preparation notes based on the employer’s stated responsibilities and qualifications.

Understanding the scope. This AI Integrations Engineer (Open Source · Web Search) position at SearchApi is best assessed through the work described in the employer’s posting, rather than the title alone. The available role overview says: “SearchApi wants an engineer to connect its search-data API with tools that developers and AI agents already use. The role focuses on accepted contributions in external open-source repositories, practical integrations…” Read that statement together with the responsibilities below to understand the likely balance between delivery, coordination and technical decision-making. The role belongs to the AI and data area, but that label is only a guide to the work; the employer’s own requirements remain decisive. Before applying, check the original listing for reporting lines, product or team assignment, employment terms and any details that may have changed since this copy was checked. Where this page says a fact is not specified, treat it as an open question rather than an implied promise.

What the responsibilities signal. The posting specifically names “Contribute SearchApi support to established open-source frameworks through reviewed, merged pull requests.”; “Build integrations and MCP servers that expose search data to developers and agents.”; “Write example applications, quickstarts and integration documentation.”. For each duty, identify a project where you performed comparable work and be ready to describe the context, your own contribution, constraints, decisions, and measurable result. Explain how you moved from the initial need to implementation, review, release or operational follow-through, where those stages apply. If the work involved other teams or users, distinguish your decisions from the group’s contribution. Avoid presenting a technology keyword as proof by itself: connect it to the problem you solved, the scale or complexity involved, and what changed after your work. The source may contain additional duties; review it directly before preparing your application.

How to read the requirements. The listed qualifications include “Merged open-source contributions to repositories owned by others and an integration, library or MCP server used by other people.”; “Working ability in Ruby, Python or TypeScript and at least one agent or automation framework.”; “Clear English technical writing and self-directed prioritisation.”. Mark each requirement as demonstrated, adjacent experience or a genuine gap, then use a concise example for the first two categories. A strong example explains what you personally owned, how you made trade-offs, how you validated the result and what you learned. If the posting specifies years of experience, language ability, certifications, location or eligibility, address those facts plainly in your CV or application rather than relying on the employer to infer them. Do not claim a qualification from exposure alone. For a requirement you do not meet, describe relevant transferable experience accurately and ask the recruiter whether it is mandatory.

Technology and working evidence. The technology terms associated with this listing are Python, TypeScript. Treat this as a set of posting-derived signals, not a guarantee that every tool is used daily or that the list is complete. For each term relevant to your experience, prepare one concrete example: the system or workflow, the part you owned, the alternatives considered, and how you tested reliability, security, performance or usability as appropriate. If you have not used a named tool, explain the closest related system you have worked with.

Benefits

• The employer lists fully remote work, equity, profit sharing, learning across a growing SaaS product and periodic team retreats.

About SearchApi

SearchApi provides an API for structured, real-time data from web search, shopping, video and other search sources. Its posting describes a small, remote-first engineering team building a Ruby on Rails product.

Browse job categories

Related jobs

• Java Product Support Engineer at Sonatype — Sonatype
• Salesforce Developer — Keyloop
• Senior Java Product Support Engineer at Sonatype — Sonatype
• Senior Software Engineer (Backend) at TeamSnap — TeamSnap
• Senior Software Engineer at Voltus — Voltus
• Software Engineer II — Clearer.io