Senior Systems Engineer

Responsibilities Domain ownership: Own the operational health of one or two infrastructure domains (e.g., server platforms, virtualization, cloud infrastructure, identity, backup and recovery, specialty business systems). Keep them measurably healthy and improving. Major incident leadership: Lead major incident response, drive technical resolution, coordinate responders, communicate to stakeholders, and own the post‑incident review and corrective actions. Patching and DR programs: Own the patching program for assigned domains—cadence, exception handling, reporting, continuous improvement. Own disaster recovery execution: maintain and exercise DR runbooks, coordinate tests, and ensure recovery objectives are met and evidenced. Server lifecycle at scale: Drive capacity planning, refresh cycles, configuration baselines, and decommissioning of legacy systems. Monitoring and observability: Operate and improve monitoring and observability across managed systems—tune alerting, eliminate noise, build dashboards, and contribute to anomaly‑detection and AIOps initiatives. Cross‑team initiatives: Lead initiatives that span Platform Engineering, Cybersecurity, Networking, and application teams—controlled rollouts, hardening efforts, platform migrations. Land them without breaking production. Standards and patterns: Define and document operational patterns, runbooks, and standards the team executes against and the auditors review. Mentorship: Pair with Systems Engineers, run technical reviews, give substantive feedback, and grow the next tier. Quality of output from less senior engineers is part of your scope. Operational partnership: Be the senior partner with Platform Engineering, Cybersecurity, Networking, and IT Service Management when they need operational input. Solve problems with them, not at them. Specialty systems: Provide operational ownership of specialty business systems and legacy platforms supporting business‑critical applications. Security and Audit: Apply and validate security baselines, lead remediation of high‑severity findings, and keep your domains' evidence map current. Automation: Push toward repeatable, codified operations (IaC, automated evidence collection, scripted runbooks) instead of one‑off manual work. On‑call: Participate in and serve as senior escalation for the on‑call rotation, including after‑hours support for high‑severity incidents, change windows, and disaster recovery events. Requirements 5+ years in systems engineering, systems administration, or infrastructure operations, including time in a senior individual contributor or technical lead capacity. Strong fundamentals across multiple infrastructure domains (server platforms, virtualization, cloud infrastructure, networking, identity, backup and recovery). Experience operating production workloads in at least one major cloud platform. Demonstrated experience leading major incidents and disaster recovery exercises. Ability to produce clear architecture, operational, and decision documentation that holds up under audit and peer review. Excellent written and verbal communication; able to explain trade‑offs across technical and business audiences in plain language. Comfortable mentoring less senior engineers and owning quality‑of‑output for one or more domains. Comfortable serving as senior escalation in an on‑call rotation. Core Competencies Demonstrates expertise in operational health management of infrastructure domains, including server platforms and cloud infrastructure, while leading major incident responses and disaster recovery initiatives. Proficient in mentoring engineers and producing clear documentation for operational standards and audits. #J-18808-Ljbffr Aprio