Compute and Platform Recovery Architect

• Design the recovery topology. Active, active and active, passive cluster design across two production data centres, so that node, cluster and site failure are survivable inside the committed recovery window for tier one compute.
• Own dual site compute. Own the compute layer of the dual data centre design so that either site can carry full factory load.
• Protect virtualisation continuity. Recovery design for the virtualisation estate, including platform transition risk. Recovery must hold through a hypervisor or licensing change rather than break because of one.
• Solve high performance compute continuity. Define what recovery actually means for high performance compute, where classical disaster recovery assumptions fail. Decide what is recovered, what is rebuilt, and what is deliberately accepted as loss.
• Produce the evidence. Design and execute compute recovery tests against the committed window, and produce the evidence pack that supports enterprise readiness reporting.
• Scale the reference model. Carry the compute reference model into additional manufacturing sites as the programme extends across the region.
• Direct without managing. Set and enforce compute resilience requirements for the managed service provider in region, validate delivered service directly, and provide technical direction and mentoring to compute and data centre engineers.

REQUIRED QUALIFICATIONSWe are looking for the right capability rather than a specific number of years. The experience indication below is typical, not a filter; an engineer who has genuinely done this work in less time will be considered.

• Typically ten or more years in infrastructure engineering, with deep hands on virtualisation and enterprise compute.
• You have personally designed and executed a multi site compute failover, with evidenced results against a defined recovery objective. Authoring a plan does not meet this bar.
• Real depth in clustering, hypervisor level high availability, storage attached compute dependencies, and the genuine failure modes of each.
• Credible in at least one adjacent domain: storage, network or cloud.
• You have set a technical standard that other teams adopted without reporting to you.
• Able to operate with substantial autonomy at distance from your reporting line., * Semiconductor, or another continuous operations manufacturing environment where downtime carries direct production cost.
• High performance or engineering compute exposure.
• Hypervisor platform migration at enterprise scale.
• Effective working across United States and Asia time zones without losing influence., * Typically ten or more years in infrastructure engineering, with deep hands on virtualisation and enterprise compute.
• You have personally designed and executed a multi site compute failover, with evidenced results against a defined recovery objective. Authoring a plan does not meet this bar.

• Real depth in clustering, hypervisor level high availability, storage attached compute dependencies, and the genuine failure modes of each.

• Credible in at least one adjacent domain: storage, network or cloud.

Work Location: Hybrid remote in Irvine, CA 92603