Elixir Engineer (WebRTC) — Remote

We're looking for an Elixir Engineer to join our WebRTC squad and take ownership of the backend services behind our real-time communications and Voice SDK platform.

Our SDKs are supported by a set of Elixir backend services covering authentication and token management, push notification delivery, connection proxying, routing, and diagnostic logging. These services carry customer-facing traffic and are growing fast. We're looking for a dedicated backend engineer who can own them — and who brings the distributed-systems judgement the squad needs when deciding how these services should be built.

You'll be the first dedicated backend engineer on this squad. You'll work closely with our mobile and JavaScript SDK engineers, and alongside Telnyx's wider Elixir community, owning backend systems from design and implementation through deployment, monitoring, scaling, and production support.

This is a systems-focused role for someone who enjoys distributed production services, reliability problems, and understanding how applications, networks, and infrastructure interact under real load.

What You'll Do

• Design, build, and operate Elixir services supporting our real-time communications and Voice SDK products
• Own the backend systems behind authentication and token issuance, push notification delivery, connection proxying, routing, and diagnostics
• Improve the reliability, scalability, and maintainability of customer-facing services under sustained load
• Strengthen connection setup, authentication flows, session handling, and service behaviour across real-time workloads
• Build observability that makes production behaviour visible: structured logs, metrics, dashboards, alerts, and operational tooling
• Improve visibility into push notification delivery so failures to APNs and FCM are traceable rather than silent
• Diagnose production issues across application, networking, and client connectivity boundaries
• Improve deployment processes, rollout safety, and production readiness for distributed services
• Turn recurring customer and operational issues into durable engineering improvements
• Set the technical direction for these services and help raise backend practice across the squad

You'd Be A Good Fit If You Have

• Production experience with Elixir or Erlang — you've shipped and operated BEAM services, not just read about them. Comfort with OTP (GenServer, supervision trees, process design) and the Elixir ecosystem (Phoenix, Ecto, Telemetry)
• Experience with high-load, high-throughput backend systems — and the judgement to tell a sound architectural decision from a plausible-looking one
• Experience with persistent connections — WebSockets, Phoenix Channels, or similar connection-oriented systems, including session lifecycle, reconnection, and backpressure
• Experience building or operating authentication, token, or session services
• Strong experience with distributed systems and service-oriented architectures
• Experience owning services through their whole lifecycle: design, deployment, monitoring, troubleshooting, and scaling
• Experience with Kubernetes, containers, CI/CD, and modern production infrastructure
• A strong observability mindset — logging, metrics, dashboards, alerting, and root-cause analysis
• Good networking fundamentals and the ability to troubleshoot across software, networking, and infrastructure boundaries
• Strong communication skills and the ability to work with engineers across different parts of the stack

Nice to Have

• Experience with push notification infrastructure such as APNs or FCM
• Experience with DNS, edge routing, service discovery, or globally distributed systems
• Experience building internal diagnostic, observability, or troubleshooting tools
• Experience building backend services consumed by mobile or JavaScript SDKs
• Familiarity with WebRTC, VoIP, or voice/video communications — useful context, but the backend work does not require it
• Open-source contributions to the BEAM ecosystem

---

#REMOTE