Manager, Software Engineering DevOps

To be considered for this position, applications and resumes are accepted only through our careers site by directly applying to the posted job. We do not accept unsolicited resumes or sales solicitations from staffing agencies. Any OCC employee wishing to submit a referral must do so through their Workday account. Any resume submitted outside of an active job posting will not be considered for employment.

What You'll Do:

The Manager, Environment Operations (EnvOps) will lead and optimize the L1 and L2 support functions responsible for full production-level environment support across application deployments, middleware, and platform infrastructure. This role drives incident response quality, implements SLA governance, leads alert reduction and MTTR improvement initiatives, and delivers actionable operational metrics to leadership. The Manager ensures the team operates at a high standard of readiness — triaging, resolving, and escalating environment issues with speed, accuracy, and full documentation discipline.

Primary Duties and Responsibilities:

To perform this job successfully, an individual must be able to perform each primary duty satisfactorily.

Incident Management & Environment Support:

• Lead L1 and L2 support engineers in all incident response activities including triage, investigation, coordination, resolution, closure, and post-incident reporting.

• Oversee technical analysis of environment incidents across application deployments, middleware, and platform layers while coordinating response activities with internal engineering, platform, and application development teams.

• Serve as Tier 3 escalation point for complex incidents beyond L2 capability — triaging, directing, and driving resolution across Platform (k8s, Kafka, TFE), S&I (deployment, middleware, storage, network), Security (Vault, certs, secrets), and App Dev teams.

• Own the full incident lifecycle — from first alert through to RCA documentation and permanent fix or accepted workaround.

• Drive post-incident reviews for all P1 and P2 incidents, ensuring root cause is identified, documented, and actioned — not filed.

SLA Governance & Operational Standards:

• Define, publish, and enforce SLA targets across all severity levels:

  • P1 (Critical): 15-minute response, 2-hour resolution

  • P2 (High): 30-minute response, 4-hour resolution

  • P3 (Medium): 2-hour response, 8-hour resolution

  • P4 (Low): 4-hour response, 24-hour resolution

• Monitor SLA compliance in real time; escalate breaches immediately and report trends to leadership on a sprint cadence.

• Ensure incident priority classifications are accurate, consistent, and applied at point of triage — not revised post-resolution.

• Publish monthly SLA compliance reports to leadership with trend analysis and improvement actions.

Alert Tuning & MTTR Improvement:

• Lead alert tuning and noise reduction initiatives across monitoring toolsets — on-call engineers are paged for situations requiring human judgement, not system noise.

• Track and publish the alert-to-incident ratio each sprint; hold the team accountable to a visible and improving trend.

• Drive continuous improvement on Mean Time to Resolve (MTTR) — analyzed by environment, severity, and team tier; reported quarterly with commentary on trend and action.

• Identify recurring incident patterns and open Problem records; drive permanent fixes, not repeated workarounds.

• Lead automation and tooling initiatives to reduce toil, accelerate triage, and eliminate manual steps from the support workflow.

Documentation & Knowledge Management:

• Ensure accurate, complete documentation for every incident — symptoms, steps taken, diagnostics, resolution, and RCA where applicable.

• Own the runbook library — every novel resolution produces a runbook published to L1 before the incident is closed; coverage gaps are tracked and closed sprint-on-sprint.

• Maintain environment configuration documentation and operational procedures in a current, accessible, and team-reviewed state.

Supervisory Responsibilities:

• Lead a team of 6–10 L1 and L2 support engineers and contingent labor within the Environment Operations function.

• Manage team scheduling to ensure full coverage of production support windows including on-call rotations, shift handoffs, and escalation availability for 24×7 support responsibilities.

• Perform all talent management functions including performance reviews, direct and timely feedback, go