AD - Enterprise Architecture

Who You Are

• 10+ years of software engineering experience with 3+ years in a domain or enterprise architecture capacity
• Deep command of distributed systems design, microservices patterns, and cloud-native architecture on AWS
• Demonstrated ability to build pattern libraries and reference architectures
• Experience embedding NFRs such as reliability, performance, and security into architecture patterns
• Strong communication skills: able to write architecture guidance that is precise without being prescriptive
• Track record of earning technical trust across engineering teams without formal authority
• Technical Requirements: Distributed systems design — DDD, microservices, event-driven architecture, CQRS, saga patterns, hexagonal architecture
• Cloud-native architecture on AWS — EKS, Fargate, Lambda, Aurora, DynamoDB, EventBridge, SQS/SNS
• NFR patterns — circuit breakers, bulkheads, retry/backoff, rate limiting, graceful degradation, SLO/SLI design
• API design and governance — REST, gRPC, API versioning, contract-first development
• CI/CD and observability — GitHub Actions, ArgoCD, OpenTelemetry, distributed tracing, structured logging

Role Overview

• Own the enterprise application pattern library and help teams apply standards consistently across service boundaries, integration, resilience, and fault tolerance
• Create reference architectures, starter templates, and decision guides that make recommended choices easier to understand and apply
• 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

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, starter templates, and decision guides that are easy for teams to adopt
• Reduce ambiguity by making recommended architecture choices clear, practical, and repeatable
• Run enablement sessions, office hours, and working groups that help standards become part of normal engineering practice

Build Security and Reliability in from the Start

• Embed secure-by-design practices into application patterns from the beginning, not as a late-stage review activity
• Build reliability and observability expectations into architecture patterns through SLOs, SLIs, and measurable operating targets
• Partner with platform and security teams on shared patterns for service mesh, API gateway, secret management, and pipeline controls
• Lead modernization through partnership

Skills that will help you stand out

• AI/ML integration patterns — LLM embedding, RAG architectures, model abstraction layers, agentic workflow design
• Modernization strategy — strangler fig, anti-corruption layers, data sync for monolith decomposition
• Data mesh — domain data ownership, data product interfaces, federated governance
• Platform transitions — EventBridge migration and API Gateway modernization (both in-flight)