# Consultant, Site Reliability Engineer — Nationwide

- Location: United States
- Posted pay: $118k–$222k/yr
- Posted: Nov 19, 2026
- Status: open (checked Nov 21, 2026)
- Apply (employer's site): https://nationwide.wd1.myworkdayjobs.com/Nationwide_Career/job/Ohio---Columbus-Three-Nationwide-Plaza/Consultant--Site-Reliability-Engineer_101295
- Employer record: https://visajobs.io/company/nationwide-insurance.md

## Sponsorship history
- Tier: Employer history only
- With this exact title: 0

## Description
If you’re passionate about being part of a dynamic organization that enables a Fortune 100 company with nearly $70 billion in annual sales to drive innovation and adopt new technologies that deliver business results, then Nationwide’s Technology team could be the place for you! At Nationwide®, “on your side” goes beyond just words. Our customers are at the center of everything we do and we’re looking for associates who are passionate about delivering extraordinary care. The Site Reliability Engineer (SRE) will help improve the stability, availability, performance, and operability of Nationwide’s Imaging & Workflow (IW) application portfolio. The role will focus on services including AWD-NF, Vision, Views, Capture, NRS, and URBO, and will partner closely with IW product, application development, infrastructure, and platform teams.
The SRE will bring a production-first perspective to the full-service lifecycle: understanding how applications behave in production, identifying and reducing reliability risks, strengthening operational readiness, and helping teams deliver changes safely. This role is hands-on and collaborative. It applies practical SRE principles in a way that supports business needs, customer and associate experience, security, and the delivery commitments of IW teams.
Key responsibilities
Reliability, service health, and observability
Establish and maintain a clear view of service health, including availability, latency, error rates, capacity, dependencies, and other relevant production signals.
Assess existing monitoring and observability coverage; identify blind spots, noisy alerts, unclear ownership, and signals that do not lead to an actionable response.
Implement and improve instrumentation, dashboards, alerts, and service health reporting using New Relic and other team-standard tools as appropriate.
Make alerts actionable by defining meaningful thresholds, routing and escalation expectations, and response guidance in partnership with the teams that own each service.
Identify reliability risks across application components and their dependencies, including databases, messaging, APIs, infrastructure, and deployment platforms.
Service-level objectives and reliability planning
Partner with product and engineering teams to define and evolve service-level indicators (SLIs) and service-level objectives (SLOs) that reflect user and business outcomes.
Use production signals, incidents, service-level performance, and operational trends to identify and prioritize reliability improvements.
Help teams make informed trade-offs among reliability, performance, security, resilience, and delivery speed, using evidence from production wherever possible.
Contribute to reliability reviews and planning for existing services, significant changes, and new initiatives, identifying operational requirements and risks early.
Help establish appropriate reliability targets and service expectations with stakeholders; document assumptions, ownership, and escalation paths.
Incident response and continuous improvement
Investigate complex production incidents across application and infrastructure boundaries; help coordinate response, mitigation, communications, and service restoration with the appropriate owners.
Use logs, metrics, traces, deployment history, and other available evidence to support timely diagnosis and informed recovery decisions.
Participate in incident reviews and document contributing factors, impact, timeline, and lessons learned in a blameless, improvement-oriented manner.
Track corrective actions through completion and validate that changes reduce recurrence, improve recovery, or lower operational risk.
Identify patterns in incidents, alerts, and support demand to address systemic causes rather than relying on repeated manual intervention.
Automation, deployment, and recovery
Automate repeatable operational tasks, health checks, diagnostics, and reliability controls to reduce manual effort and operational toil.
Partner with application and platform teams to improve deployment safety, including release validation, change visibility, rollback or recovery readiness, and post-deployment checks.
Strengthen recovery practices by identifying and testing appropriate recovery procedures, dependencies, and operational handoffs.
Contribute to resilience and capacity practices, including failure-mode analysis, resource utilization review, and service behavior under expected operating conditions.
Promote consistent, maintainable automation that fits the team’s approved platforms, security controls, and support model.
Operational readiness and knowledge sharing
Ensure services have practical, current runbooks covering health checks, common failure modes, triage, escalation, mitigation, and recovery steps.
Improve operational documentation so that service ownership, dependencies, support boundaries, and critical procedures are clear to the teams that respond to issues.
Collaborate with service owners to include operational readiness in design and delivery practices, rather than treating it as a post-release activity.
Share SRE practices, incident learnings, and reusable approaches across IW teams; coach teams in building services that are easier to observe, operate, and recover.
Support a culture of continuous learning, clear ownership, and measurable reliability improvement.
Qualifications and capabilities
Experience supporting business-critical applications in production and contributing to service reliability, incident response, or operational improvement.
Ability to troubleshoot complex issues across application, database, middleware, API, messaging, and infrastructure layers, collaborating with the relevant technical owners.
Practical experience with monitoring and observability, including the ability to turn production signals into useful dashboards, actionable alerts, and diagnostic insights.
Demonstrated ability to automate repeatable work using scripting, configuration, or team-approved

> History, not a promise: past H-1B filings do not mean an employer will sponsor you or a given role. Data: U.S. DOL OFLC LCA disclosure (FY2024–FY2026 for role counts, certified LCAs) and the USCIS H-1B Employer Data Hub. Not legal advice. Methodology: https://visajobs.io/methodology
