AD - Enterprise Architecture

We’re looking for an Application Domain Lead to shape how software is designed and delivered across the enterprise. This senior individual contributor role sits within Enterprise Architecture and connects architecture direction with practical engineering execution. You will define reusable patterns, standards, and guidance that help teams make consistent technical decisions, embed non-functional requirements early, and build secure, reliable systems without unnecessary friction. You Might Be Who We're Looking For If... You’re the person on your current team who sees the same architectural mistakes repeated across squads and wants to solve them once, at the pattern level. You’ve spent years designing and building distributed systems, and you’ve seen good teams make avoidable decisions when they did not have clear, practical guidance. You stay close to the work. You can evaluate trade-offs at the whiteboard and in a pull request, and you’ve built reference architectures or pattern guidance that teams adopted. You’re comfortable engaging in detailed architecture discussions and helping teams identify the patterns they should use. You’ve operated without formal authority and earned trust through technical depth, clear thinking, and a track record of enabling rather than blocking. You know how to guide teams through competing priorities, exception requests, and concerns about standardization while helping the organization move toward consistent, practical patterns. You're comfortable working across diverse teams and technologies, quickly learning new languages, tools, and platforms while championing approaches that benefit the broader organization.

Overview: Own the enterprise application pattern library and help teams apply standards consistently across service boundaries, integration, resilience, and fault tolerance. Establish practical NFR guidance, including reliability targets, SLO/SLI design, performance baselines, and observability expectations. Create reference architectures, starter templates, and decision guides that make recommended choices easier to understand and apply. Help teams learn and adopt AI-enabled SDLC practices, including responsible use of coding assistants, architecture decision support, testing acceleration, and secure delivery guardrails. Partner with the Web Enablement team, promoting understanding and consistent adoption of PDS, NSK, and WSK. Partner with platform engineering and security teams to embed secure-by-design practices into APIs, service communication, secret management, and delivery pipelines. Guide modernization efforts across cloud migration, platform consolidation, API modernization, and legacy decomposition. In this role, you will focus on four outcomes: setting practical application standards, driving architecture consistency, enabling engineering teams, and building security and reliability into delivery from the start. Set practical application standards Define and maintain the enterprise application pattern library, covering both functional architecture (domain decomposition, service boundaries, data ownership) and non-functional requirements (availability, latency, throughput, fault tolerance). Establish NFR baselines for reliability, performance, availability, and observability, so they are built into reusable patterns. Author authoritative guidance on integration patterns, event-driven architecture, and API design that teams can adopt without ambiguity. Drive architecture consistency Help product squads, domains, and platform teams apply patterns consistently without creating bottlenecks. Use architecture reviews to reinforce good patterns, surface drift early, and coach teams toward convergence. Maintain the architecture decision record process, so important technical decisions are documented, reviewed, and traceable. Enable engineering teams Create reference architectures,