Senior VoIP Operations & Reliability Engineer; Carrier-Class Voice Platform

Why This Role Matters: Voice is unforgiving. A dropped call, a one‑way audio path, or a registration storm is visible to every customer  team can build the platform, but building it and running it are two different disciplines, and ambition without operational hardening is fragile. We need someone who has lived through real VoIP failures, learned from them, and can stand shoulder to shoulder with the developers to make sure the platform survives contact with production.

If you want ownership of a modern, open‑source, carrier‑class platform from design review through 3am incident to the postmortem that makes it stronger, we want to talk to you.

About The Role: Our software team is building a next‑generation carrier‑class voice platform. They are strong programmers, but they are not experienced operators, and there is a world of difference between code that works and infrastructure that stays up under real carrier load. We need a seasoned operator to close that gap and work hand in hand with the development team.

You are the person who has actually run this kind of system in production. You know the failure modes that do not show up in a code review, the things that break at 2am, and what it really takes to keep customers from ever noticing. Your job is to bring that operational reality into the platform from the inside: pairing with the programmers as they build, making sure the design can be operated, and then owning the platform in production with zero customer downtime.

There is an architectural side to this. You will sit in design reviews and push the team toward decisions that are operable, resilient, and testable, not just elegant in code. But the core of the role is operational: you are the experienced hand who keeps every system up, who owns every failure scenario end to end, and who instills operational discipline in a team by being on‑call and training juniors to handle any incidents.

You should be equally comfortable pairing with a developer to make a service observable and failure‑aware, and at 3am driving an incident to resolution. We need that judgment, with years of real VoIP operations behind it. In the meantime, this is not a future‑only role. We already run a live Kamailio and Asterisk production system carrying real customer traffic today, and your first and most immediate mandate is to help harden it: shore up its reliability, close its failure gaps, and keep it solid while the next‑generation platform is being built.

Day‑to‑day production stability of the current system comes first.

Harden the current production system (immediate priority)

• Take ownership of the reliability of our live Kamailio and Asterisk production system from day one, while the next‑generation platform is still in development.
• Assess the current system end to end and find its weak points: single points of failure, brittle failover, missing redundancy, capacity headroom, and the failure scenarios it does not yet handle gracefully.
• Close those gaps incrementally and safely, without disrupting live customer traffic: add redundancy and failover, tighten configuration, and remove fragility.
• Add the observability the current system is missing so problems are caught before customers feel them, and stand up alerting, dashboards, and SIP capture against the live fleet.
• Stabilize day‑to‑day operations: triage and resolve recurring issues, document the system as it actually runs, and write the runbooks that do not exist yet.

Work hand in hand with the development team

• Pair with the programmers throughout development as the operational voice in the room: review designs, challenge assumptions, and find the failure modes that code reviews miss.
• Make operability a build‑time requirement, not an afterthought: push for the logging, metrics, health checks, graceful shutdown, retry behavior, and failure handling that the team needs to add for the platform to survive production.
• Transfer operational knowledge to the team: help developers understand how their code behaves under load and failure, and raise the whole group's instinct for production reality.
• Map the full failure surface of the platform (node failure,…