SR DevOps Engineer-multi-cluster Kubernetes/Network/Voice-Telecom Systems || REMOTE Role

REMOTE Role

1 YEAR CONTRACT+

2 INTERVIEWS

TECH ASSESSMENT

Job Description

DevOps engineer for a voice agent platform. They are going through a transformation from Monolith to Cell based arch and needs new practices enabled in the new design.

Here's a description of the stack they would help manage:

SR DEVOPS ENGINEER

10+ YEARS OF EXPERIENCE

DevOps:

·       Ideally each profile should match 80%+ of our stack, and combined cover 100%. That way they have relevant experience to share with the team and won't have to take time ramping up.

·       Pulumi (TypeScript) / Terraform IaC at scale (40+ stacks across multiple regions in AWS).

·       ArgoCD / GitOps for deploying applications across multiple clusters.

·       Progressive delivery: canary, blue/green, automated rollback, soak periods. Maps to "phased rollouts" and the canary-manager Go service.

·       CI/CD pipeline design: GitHub Actions, build pipelines for 15+ Dockerfiles.

·       Deploy tooling for on-demand environments: cell creation, preview environments, developer deployments.

SRE:

·       SLOs / error budgets in observability software (Chronosphere, Prometheus, Grafana, Datadog).

·       Capacity planning + load testing: called out in Q2 milestones (provider rate-limit audit, per-org concurrency audit, script-based load testing).

·       Kubernetes production ops: pod crash diagnosis, HPA/VPA tuning, PodDisruptionBudgets, graceful shutdown.

Required:

·       Cellular Design & Provisioning: Build and maintain fully isolated, immutable "Cells"—the fundamental building blocks of our new architecture—ensuring each contains its own compute, data, and voice processing layers. 

·       Infrastructure as Code (IaC): Develop modular Terraform/Pulumi scripts to automate the entire lifecycle of a cell, enabling us to spin up new geographic regions or tenant-specific environments in minutes. 

·       Traffic Steering & Routing: Design and manage the "Thin" Global Routing layer that handles entry points and intelligently directs voice traffic to the healthy, appropriate cell. 

·       Blast Radius Mitigation: Implement strict isolation policies (network and data) to ensure that issues within one cell are contained and do not impact the global platform. 

·       CI/CD Pipeline Evolution: Shift from a single-pipeline monolith deployment to a sophisticated, multi-cell rollout strategy (e.g., deploying to a "Canary Cell" before a global rollout). 

·       Voice-Centric Observability: Create per-cell dashboards that track not just CPU/RAM, but critical voice metrics like Mean Opinion Score (MOS), jitter, and packet loss. 

Must-Have Skills 

·       Advanced Kubernetes (K8s): Deep experience in cluster management, specifically with multi-cluster or multi-region deployments. 

·       Production IaC Experience: Mastery of Terraform, Pulumi, or CloudFormation in a production environment where "Infrastructure as Code" is the only way changes are made. 

·       Network Architecture: Strong understanding of VPC designs, Peering, Transit Gateways, and Load Balancing (Layer 4 and Layer 7). 

·       Distributed Systems Knowledge: You must understand the "Cell-Based" philosophy—sharding, bulkhead patterns, and the "Shared Nothing" architecture. 

·       Scripting & Automation: High proficiency in Python or Go for building custom tooling to manage cell lifecycles. 

Nice-to-Have Skills 

·       Voice/Telecom Protocols: Familiarity with SIP, WebRTC, RTP, or experience with platforms like Twilio, FreePBX, or SignalWire. 

·       Service Mesh: Experience with Istio or Linkerd for handling complex inter-cell communication and mTLS. 

·       Chaos Engineering: Experience using tools like Gremlin or Chaos Mesh to simulate cell failures and validate "Cell-Evacuation" procedures. 

·       Database Sharding: Understanding of how to partition databases (PostgreSQL, Mongo, etc.) across cellular boundaries. 

·       Security Compliance: Experience with SOC2 or HIPAA compliance, which is often a requirement for high-scale voice platforms.

NTH:
Cellular design is not a must. We can consider candidates with microservices experience