Turn this role into an interview — a resume and cover letter built around what this employer wants.
Openkrill is seeking a Senior Software Engineer to help steer the platform that powers real-time AI-powered conversations in emergency-response contexts.
You will own complex backend, real-time systems and architecture, integrating LLM and HITL workflows while ensuring reliability and auditability in production environments.
Your opportunity
Our client is a small, talent-dense AI product team building conversational, agentic systems for emergency response. The team began as a seed-stage startup focused specifically on public-safety communications and was acquired in 2026 by a global public-safety technology company, where it now operates as a specialized division within its broader AI organization.
Their initial wedge is deceptively simple: public-safety answering points are chronically understaffed, yet highly trained 911 telecommunicators spend meaningful amounts of time handling calls that are not emergencies. The platform uses voice AI to autonomously handle designated non-emergency interactions, gather information, answer questions, route callers and upscale appropriately, allowing human operators to concentrate on situations where their judgment matters most.
The startup proved that use case independently. The acquisition gives the team something much harder for an early-stage company to manufacture: distribution into established emergency-response infrastructure and the opportunity to integrate its technology across a much broader suite of command-centre products. The group is now a strategically important part of a larger effort to introduce useful, human-centred AI throughout emergency response (from the initial call through dispatch and field operations).
The engineering environment has retained much of its startup character. The team remains relatively small, engineers have substantial ownership, and the company is growing the group materially following the acquisition. This role sits in a division focused on the systems that make the voice agent itself work rather than primarily building downstream customer integrations.
The team actively prototypes with emerging technologies (voice-to-voice models) and new inference architectures, but a compelling demo is not sufficient reason to rebuild a mission-critical system. Public-safety customers need reliability, auditability and the ability to understand why a system behaved the way it did. Today, the platform deliberately separates speech-to-text, reasoning and text-to-speech into modular components, allowing individual providers to be changed or failed over independently rather than making the entire product dependent on a single inference provider.
That means some of the most interesting engineering work lives in the space between the models: orchestrating real-time conversations, managing latency and interruption, integrating deterministic software with probabilistic systems, designing graceful failover, tracing model behaviour and maintaining a product that still works when an upstream AI provider does not.
As a Senior Software Engineer, you’ll help set technical direction for this platform and own difficult problems across real-time AI pipelines, backend systems, telephony and production infrastructure. You’ll also join a team that encourages engineers to use AI agents in their development workflows wherein humans remain accountable for quality, judgment and the software operating in production.
The platform combines conventional distributed software, real-time communications infrastructure and a modular voice-AI pipeline. The technologies below represent the broader system engineers are building within rather than a checklist of tools every engineer is expected to use day to day.
The stack is intentionally modular. Individual speech, inference and voice providers can be substituted or failed over independently, and the team expects its technology choices to continue evolving as the underlying capabilities improve. They’re well aware of the frontier capabilities (such as GPT‑Live) and are constantly evaluating them against their use case.