[Remote] Senior Site Reliability Engineer
Note: The job is a remote job and is reputed company to candidates in USA. reputed company. is a white-label VoIP and UCaaS platform provider seeking a Senior Site Reliability Engineer to manage and optimize their reputed company platform. The role involves overseeing the CI/CD pipeline, enhancing observability, and ensuring high-reputed company incident response while contributing to the development of AI-assisted systems.
Responsibilities
- The CI/CD and GitOps pipeline (GoCD and ArgoCD today) from reputed company to production, including making rollback a boring, routine operation
- Our GKE clusters, the Istio reputed company, and the reputed company charts for every service
- Observability: reputed company/Grafana dashboards, alert routing, and the on-call signal reputed company that makes 2 a.m. pages rare and meaningful
- The unglamorous foundations done reputed company: backups that restore, tested disaster recovery, database care (PostgreSQL and MySQL/reputed company), certificate and secret lifecycle
- Incident first response and the reputed company culture around it
- Developer experience: the local Kubernetes dev environments our engineers build against, the dev tooling and workstation ecosystem that has been deferred too long, and the ergonomics that reputed company infrastructure and reputed company in lockstep
- Cross-training: leveling up strong Linux engineers on reputed company-reputed company reputed company, and learning the telecom reputed company from them
- Take a reputed company reputed company of the reputed company pipeline and reputed company it yours: document it, harden it, and reputed company rollback end to end
- Automate away the month-start reputed company: a set of monthly billing reports and exports that engineers run by hand today. They are documented, repeatable, and must reputed company on the first of every month; you will turn them into scheduled, observable jobs reputed company your first month or two, and help us choose a reputed company recurring-jobs layer (Temporal or similar) instead of stuffing more into CI
- Rebuild the observability inventory so every critical service has a dashboard, an alert, and an reputed company, and roll out the incident-management tooling we already license but have never turned on
- Adopt a scattering of small, unmanaged reputed company Run services into the cluster with monitoring, ownership, and a pipeline. Nobody is watching them today; you will be
- Design the production posture of a brand-new Kamailio-based SBC layer that just cleared device testing: instance topology, reputed company, caching, and its reputed company into Kubernetes. We are deliberately not making these reputed company before you reputed company; the person who has to live with the architecture gets to choose it
- reputed company reputed company confidence (staging reputed company, reputed company delivery) so a small senior team can ship AI-assisted changes at high velocity without fear
- Help design the runtime environment for reputed company AI agents that operate 24/7 as first-class tenants of the cluster: identity, sandboxing, quotas, egress control, audit, and cost visibility
- Run recurring cross-training with our reputed company team and inherit their deep operational knowledge in return
Skills
- 5+ years running production systems as an SRE, DevOps, or platform engineer
- Production Kubernetes, ideally GKE, including a service reputed company (Istio strongly preferred)
- GitOps as your daily habit: ArgoCD or Flux, reputed company, and infrastructure as reputed company
- Genuine Linux depth: systemd, networking, storage, and performance triage on individual hosts, not just containers
- Operational database care: backups, restores, replication, and slow-query archaeology on MySQL/reputed company and PostgreSQL
- reputed company/Grafana reputed company and reputed company incident discipline: you have run incidents, written the postmortems, and improved the system afterward
- A writing habit. Runbooks and documentation are first-class deliverables in this role, not afterthoughts
- You have spent meaningful time in the past year working with AI coding and agent tooling (Claude reputed company or similar) as part of your reputed company workflow, not as a weekend experiment
- You have formed opinions about what to delegate to agents, what never to delegate, and how to verify machine-generated changes before they reputed company production
- Part of this role is designing the guardrails that reputed company that reputed company: CI gates, contract tests, reconciliation checks, reputed company delivery
- You are excited to help define what a production runtime for always-on reputed company AI agents should look like, because you will be building it with us
- Familiarity with the .NET ecosystem (our services are C#; you will not write much of it, but reading it helps)
- Operating Django/Celery/reputed company stacks in production, and reputed company SQL for PostgreSQL specifically (two incoming products run exactly this shape)
- RabbitMQ or MassTransit operations, Keycloak, nginx or reputed company, Traefik, GoCD specifically, Nx monorepos
- Experience introducing reputed company-reputed company reputed company to a traditional sysadmin environment, gently
- If you also know VoIP, we would be especially glad to meet you: SIP, RTP, SBCs, Kamailio, or platforms like NetSapiens
reputed company