Senior Platform / DevOps Engineer (Real-time Media, WebRTC, Edge + Cloud)

Senior Platform / DevOps Engineer (Real-time Media, WebRTC, Edge + Cloud)
Job title: Platform / DevOps Engineer (WebRTC, Edge + Cloud)
\n Location: Bengaluru (Hybrid/Office)
\n Employment type: Full-time
\n Experience: 5–12+ years (flexible for strong fit)
About the role
\n We’re building and operating a LiveKit-like real-time communications platform (WebRTC) that must scale to millions of calls with edge PoPs for ultra-low latency and multi-region cloud reliability . This is a hands-on, high-ownership role focused on production systems, performance, and resilience.
\n We’re especially interested in engineers who’ve seen scale in real-time/streaming infra.
What you’ll do
\n Own reliability and performance of signaling, SFU/media nodes, TURN , routing, failover, and capacity planning
\n Build and run multi-region Kubernetes platforms with secure networking and zero-downtime deployments
\n Design edge + cloud architecture: PoPs, global routing, failover, autoscaling, DR
\n Implement SLOs/SLIs , incident response, postmortems, and operational excellence
\n Create strong observability : metrics, logs, tracing, and real-time QoE/latency metrics

\n
• Ship Infrastructure-as-Code and automation: Terraform, Helm, GitOps, CI/CD
\n

Required skills
\n Strong production experience with Kubernetes at scale (multi-cluster/multi-region)
\n Strong Linux + networking fundamentals (UDP/TCP, NAT, conntrack, DNS, load balancing)

\n
• Experience with IaC + delivery : Terraform, Helm, GitOps (ArgoCD/Flux), CI/CD
\n
• Proven on-call ownership for high-availability systems
\n

Nice to have

\n
• WebRTC/RTC operations: ICE, STUN/TURN, SFU scaling, packet loss/jitter tuning
\n
• Edge/PoP and traffic management experience (global routing, Anycast/DNS strategies)
\n
• Cost optimization for bandwidth-heavy workloads
\n
• Experience operating realtime/streaming systems at very high concurrency
\n

What success looks like
\n You can keep a real-time system stable through traffic spikes, packet loss, ISP variability, zone/region failures

\n
• You think in terms of latency budgets, concurrency, bandwidth, packets/sec , not just pods and nodes
\n
• You build platforms that are observable, automatable, and easy to operate
\n