Senior Staff Engineer - Cloud and Application Continuity

IS3 Solutions; Milpitas (CA); On-site; USD 140,000 - 170,000; Full time

Job summary

IS3 Solutions is seeking an experienced cloud resilience engineer to translate business recovery objectives into actionable application designs. You will define multi-region failover patterns and balance on-premises factory systems with cloud services, ensuring the recovery architecture meets business objectives.

You will build and maintain a recovery-oriented pattern library, map complex dependencies, and conduct rigorous application-tier failover testing to validate resilience in production

Qualifications

• Typically ten or more years in infrastructure or cloud engineering.
• Experience designing and testing cloud or hybrid failover for production workloads.

Responsibilities

• Design landing zone resilience across multi-zone and multi-region environments.
• Build a pattern library for app design including active, passive, and failover patterns.
• Engineer the hybrid seams between on-premises factory systems and cloud services.
• Create the cloud recovery environment enabling immutable recovery models.
• Map dependencies across application and integration layers including SaaS and third parties.
• Test application tier failover, not just infrastructure-level tests.
• Maintain design standards and document exceptions when recovery objectives cannot be met.

Skills

Cloud architecture

Infrastructure as code

Recovery automation

Dependency mapping

Influence without authority

Tools

Terraform

Job description

Recovery is only real at the application tier. An infrastructure that comes back without its applications has recovered nothing. You own the continuity design of the cloud estate and the recovery architecture of tier one applications.

You are the engineer who translates a business recovery objective into something an application team can actually build to, and who rejects a design that cannot meet it. Just as importantly, you are the engineer who will say plainly when a stated recovery objective is not economically achievable, and who brings the alternative rather than the problem.

WHAT YOU WILL DO

• Design landing zone resilience. Multi zone and multi region design, failover patterns, and the recovery position of cloud hosted tier one workloads.
• Build the pattern library. Active, active, active, passive, and which applies when. The library becomes the default for new application design.
• Engineer the hybrid seams. Design for the points where on premises factory systems depend on cloud services and the reverse. These seams are where most recovery plans actually fail.
• Build the cloud recovery environment. Engineer the cloud based recovery capability that supports the immutable recovery model.
• Map the real dependencies. Own the application and integration layer of the dependency map, including software as a service and third party dependencies.
• Test at the application tier. Run application level failover testing, not infrastructure only tests that prove nothing to the business.
• Hold the design line. A tier one application design that cannot meet its stated recovery objective does not proceed without a documented, accepted exception.

REQUIRED QUALIFICATIONS

We 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 or cloud engineering, with deep public cloud architecture in AWS or Azure, or both.
• You have designed and tested cloud or hybrid failover for production workloads, with evidenced recovery times you can speak to.
• Genuine application tier fluency: dependency mapping, state, data consistency on failover, session and integration behaviour.
• Infrastructure as code and recovery automation in production.
• A track record of influencing application and product teams without authority over them.

PREFERRED QUALIFICATIONS

• Manufacturing execution or factory critical application recovery.
• Landing zone build from a blank sheet.
• Chaos or fault injection engineering in production.

LEVEL EXPECTATIONS

• Works across teams on ambiguous problems that have no established playbook.
• Establishes patterns and standards adopted by application and platform teams.
• Influence extends well beyond the immediate team.