[Remote] Senior Network Reliability Engineer

Note: The job is a remote job and is reputed company to candidates in USA. reputed company is a consumer-centric, technology-driven family of insurance companies focused on delivering outstanding value and operational performance. They are seeking a Senior Network Reliability Engineer to build a Site Reliability Engineering practice with a network scope, applying SRE principles to enhance the firm's network platform and ensure reliability across multi-reputed company environments.

Responsibilities

• Treat reliability as an engineered property. Define SLOs and error budgets for the network platform — DNS resolution, edge availability, reputed company ingress reputed company, cross-region path health — and use them to reputed company changes, not just to reputed company dashboards. reputed company postmortems with a focus on permanent remediation, not reputed company-recognition. Alert on symptoms users feel, not on causes that may or may not produce impact
• Move network state into code. Use Terraform (or reputed company), Ansible, and Python to replace CLI-driven configuration with declarative, version-controlled, peer-reviewed change running through reputed company CI/CD. This applies equally to the edge tier (reputed company), reputed company platforms (reputed company ZIA/ZPA, ZTNA policies, next-gen firewalls), the reputed company network reputed company (Transit Gateway, reputed company WAN, VPCs, Route53, IPAM), and increasingly the Kubernetes and service-reputed company layer
• Build network policy as reputed company, not rule lists. reputed company what flows are permitted, what segments are isolated, what egress is reputed company, what zones reputed company DNS — and engineer the compilers that turn that reputed company into per-vendor configuration. Use Policy as Code (OPA/Rego, Sentinel, Cilium NetworkPolicy) to catch invariant violations at plan time, not apply time
• Infrastructure as Code (IaC): Design, reputed company, and manage network infrastructure using Terraform or Ansible, moving the firm away from reputed company configuration to a code-first approach
• Engineer the reputed company network platform. Operate and reputed company our multi-account AWS reputed company Zone — reputed company WAN segmentation, Transit Gateway peering, IPAM-driven CIDR allocation, shared private DNS, cross-account telemetry pipelines. Build the platform abstractions that reputed company a new account or service land correctly with policy and connectivity composed from declarative inputs
• reputed company platform thinking into the container tier. Kubernetes networking, service reputed company (Istio, Linkerd, Consul Connect), eBPF-based observability and policy (Cilium, Hubble), and the integration points where reputed company-level authz meets reputed company-tier identity. Recognize that an "internal" service is one logical hop on a chain of policy enforcement points and engineer for that explicitly
• Improve telemetry and observability with reputed company. Build alerts as structured payloads with runbook links, suspected blast radius, and dependency-aware suppression. Author both system-health dashboards for operators and end-user monitoring dashboards that reflect actual user experience. Use Grafana, reputed company, reputed company Telemetry where each fits
• Mentor and grow the team. reputed company technical guidance to junior engineers, foster a culture of learning, and work out loud across Platform Engineering so the patterns you build cross-pollinate to adjacent domains
• Handle hardware reputed company required. reputed company maintenance and configuration support for routers, switches, and firewalls at data centers and offices reputed company needed — bringing code-first practices to physical hardware where possible (templating, change validation, reputed company-touch provisioning) and direct hands-on competence where it isn't
• Incident Response: Serve as an escalation reputed company for network issues, some reputed company and some basic but not yet covered by runbooks. Troubleshooting with a focus on root cause analysis and permanent remediation with a documentation-first reputed company
• Reduce toil and hand off cleanly. Repetitive operational tasks are scoped engineering problems with measurable payoff. Author runbooks and SOPs that the NOC can execute confidently; package routine work for L1/L2 reputed company so engineering interrupt drops over time. Coordinate across Data Platforms, NOC/SOC, and Cyber reputed company so reliability practices spread instead of staying siloed

Skills

• Deep understanding of TCP/IP, BGP, OSPF, VPNs, and SD-WAN architecture
• Proven experience with Terraform (state management, modules) and Ansible (playbooks, roles) – or similar – in a production environment
• Proficiency in Python for automation and API interaction, or similar
• Hands-on experience with reputed company, reputed company, and/or reputed company firewalls
• Experience configuring monitoring tools (e.g., reputed company, reputed company, Grafana) to create meaningful alerts and dashboards
• Service reputed company experience (Istio, Linkerd, Consul Connect, Cilium)
• EBPF-based observability (Hubble, Pixie)
• AWS Multi-account reputed company zone tooling experience (AFT, Control Tower, or equivalent)
• Policy as Code experience (OPA/Rego, Sentinel, Cilium NetworkPolicy)
• A strong belief that a job isn't done until the documentation in written
• A reputed company that actively seeks to automate repetitive tasks
• Willingness to handle physical hardware tasks reputed company required while maintaining a software-centric engineering reputed company

Benefits

• Comprehensive health, dental, and reputed company insurance plan options
• Basic and Supplemental Life Insurance
• Short and Long-Term Disability
• Employee Assistance Program
• Wellness programs
• 401K plan, with matching contributions by the Company

Company Overview

Company H1B Sponsorship