Staff Cloud Infrastructure Architect

Position Summary

The Staff Cloud Infrastructure Architect shapes resilient, secure, and scalable cloud foundations that accelerate Empower's growth, protect business operations, and improve technology economics. This role owns architecture standards, reference patterns, modernization roadmaps, and technical decisions across Azure, AWS, networking, platform engineering, and Infrastructure-as-Code, partnering with Security, Quality, Data, and Application teams. AI serves as a force multiplier to increase delivery speed, operational scale, engineering quality, and decision-making through intelligent automation, predictive insights, and problem resolution. Success requires navigating Empower's hyper-growth, highly regulated 503A/503B environment with disciplined risk management, audit readiness, and execution. The role demands strategic thinking, execution rigor, learning agility, and leadership to convert ambiguity into infrastructure capabilities that support compliant innovation, reliability, and performance while raising architectural standards and engineering accountability enterprise-wide.

Responsibilities

Cloud Strategy and Architecture

• Strategic Architecture: Define cloud architecture principles, target states, and reference patterns across Azure and AWS, translating business priorities into sequenced modernization roadmaps. Apply AI-assisted analysis to compare options, model cost, performance, and risk, and improve decision quality. Own major technical choices, document tradeoffs, and guide teams toward scalable, resilient platforms that support Empower's regulated growth, operational continuity, and rapidly evolving product, data, manufacturing, and customer experience needs across the enterprise.
• Platform Modernization: Architect the migration of on-premises and data center workloads to cloud-native services, balancing speed, compliance, reliability, and total cost. Use AI-enabled discovery, dependency mapping, and workload assessment to accelerate planning and reduce execution risk. Establish repeatable patterns for landing zones, connectivity, identity, compute, storage, and recovery.