Integrations Engineer (SDK)

Voice is becoming the primary interface for technology. For the first time in history, we can use natural language to control and interact with our devices, services, and applications, and we're only at the beginning of the adoption of Voice and Physical AI across industries. Current voice interactions, however, still lack a fundamental human skill: nuanced understanding of audio scenes and environments. Navigating complex auditory scenes, distinguishing between multiple voices, or focusing on a main speaker are all part of the challenge of "teaching machines to hear like human beings."

At ai-coustics, we're building the audio intelligence layer and developer tooling to enable more robust and intelligent voice agents and Physical AI applications. Today, Voice AI companies like Perplexity, PolyAI, LiveKit, AssemblyAI or Telli use our SDK to prepare their agents for real-world acoustic challenges. Our models power thousands of agents worldwide and process millions of hours each month.

We are backed by leading early-stage investors including Connect Ventures, Partech, Inovia Capital, as well as angel investors from HuggingFace, DeepMind and Amazon with deep expertise in AI and developer infrastructure. These partners share our vision and are helping us build a world-class team operating with high levels of responsibility and velocity. We look for people who take ownership, think systemically, and want to solve challenging real-world problems in close collaboration with our customers.

We're looking for an Integrations Engineer to make our SDK easy to adopt on the platforms voice agent developers actually build on. Our core SDK is native and ships with wrappers for Python, Node.js, C, C++, Rust and WebAssembly, plus plugins for LiveKit Agents and Pipecat. You will own the plugins and the public surface of the language wrappers, keep them released in lockstep with the core SDK and work with upstream open-source maintainers so our integrations stay first-class.

You sit in the SDK team and work closely with developer relations and with customers who integrate us.

You may not be a great fit if…

• You want to work on DSP or model development in the native core
• You prefer building one product over maintaining several integrations
• You don't want to talk to customers and partner engineers
• You see open-source contribution as a side activity rather than part of the job
• Remote-first is a hard requirement for you