Senior Network Reliability Engineer

Senior Network Reliability Engineer Skip to main content

We use cookies to enhance your experience. By continuing to browse this site you agree to our use of cookies. To find out more about the cookies we use, see our Privacy Policy# Careers Senior Network Reliability Engineer page is loaded## Senior Network Reliability Engineer Apply remote type:
Remote locations:
Zionsville, Indiana time type:
Full time posted on:
Posted 2 Days Agojob requisition :
R26 0207
** Group 1001
** is a consumer-centric, technology-driven family of insurance companies on a mission to deliver outstanding value and operational performance by combining financial strength and stability with deep insurance expertise and a can-do culture. Group
1001’s culture emphasizes the importance of collaboration, communication, core business focus, risk management, and striving for outcomes. This goal extends to how we hire and onboard our most valuable assets – our employees.
** Why This Role Matters:
** The Platform Engineering Services team at Group 1001 is building a Site Reliability Engineering practice with a network scope. We're hiring an Sr. Network Reliability Engineer who embodies Innovation and Excellence, and will apply SRE principles — code-as-source-of-truth, SLOs and error budgets, alerting on symptoms rather than causes, failure-mode-first design, and the elimination of toil — to the firm's network platform from carrier edge through cloud fabric to Kubernetes pod boundary.

This is not a "keep the lights on" role. You will systematically engineer the lights-on work out of existence, build the abstractions that let other engineering teams express network intent in code, and treat the network as a single engineered system rather than a collection of vendor consoles. You will operate inside a Dev Sec Ops  practice spanning multi-cloud, multi-region environments, and you will partner closely with Cloud and Data Platforms, the NOC/SOC, and Cyber Security to extend reliability practice across the firm.
** How You’ll Contribute:
*** Treat reliability as an engineered property. Define SLOs and error budgets for the network platform — DNS resolution, edge availability, mesh ingress success, cross-region path health — and use them to gate changes, not just to color dashboards. Lead postmortems with a focus on permanent remediation, not pattern-recognition. Alert on symptoms users feel, not on causes that may or may not produce impact.
* Move network state into code. Use Terraform (or Pulumi), Ansible, and Python to replace CLI-driven configuration with declarative, version-controlled, peer-reviewed change running through Infra CI/CD. This applies equally to the edge tier (Cloudflare), security platforms (Zscaler ZIA/ZPA, ZTNA policies, next-gen firewalls), the cloud network fabric (Transit Gateway, Cloud WAN, VPCs, Route
53, IPAM), and increasingly the Kubernetes and service-mesh layer.
* Build network policy as intent, not rule lists. Express what flows are permitted, what segments are isolated, what egress is inspected, what zones share DNS — and engineer the compilers that turn that intent into per-vendor configuration. Use Policy as Code (OPA/Rego, Sentinel, Cilium Network Policy) to catch invariant violations at plan time, not apply time.
* Infrastructure as Code (IaC):
Design, deploy, and manage network infrastructure using Terraform or Ansible, moving the firm away from manual configuration to a code-first approach.
* Engineer the cloud network platform. Operate and extend our multi-account AWS Landing Zone — Cloud WAN segmentation, Transit Gateway peering, IPAM-driven CIDR allocation, shared private DNS, cross-account telemetry pipelines. Build the platform abstractions that make a new account or service land correctly with policy and connectivity composed from declarative inputs.
* Extend platform thinking into the container tier. Kubernetes networking, service mesh (Istio, Linkerd, Consul Connect), eBPF-based observability and policy (Cilium, Hubble), and the integration points where mesh-level authz meets cloud-tier identity. Recognize that an "internal" service is one logical hop on a chain of policy enforcement points and engineer…