Director, Enterprise Architecture; EA

Additional Information About the Role

• Title: Director, Enterprise Architecture (EA)
• Reports to: Chief Technology Officer (CTO)
• Direct reports: Core EA team (Enterprise Architects) and a federated EA operating model – provides dotted‑line leadership to Federated Enterprise Architects in Security, Data and other business domains in the future.
• Team size / scope: Leads a small Core EA team (typically 3–6) and drives alignment across a broader federated architecture community (Solution Architects and Domain Architects embedded in delivery and domain teams).

Position Summary: The Director, Enterprise Architecture (EA), reports to the VP and Chief Technology Officer (CTO) and is the senior leader accountable for BJC’s enterprise-wide architectural direction (principles, governance, strategy, reference architectures, lifecycle management, and cross-domain coherence). This role leads the Core EA team in a federated EA operating model, defines and governs enterprise architecture principles and standards, and ensures coherent cross-domain decision-making across applications, data, security, infrastructure, and integration.

The Director of EA partners closely with business and technology leadership, business relationship management, portfolio/program leadership, and domain capability owners to translate strategy into actionable roadmaps that accelerate delivery while reducing enterprise risk and fragmentation. This role ensures that architecture is a facilitator of execution, not a centralized bottleneck, by establishing clear decision rights, reusable guidance, and pragmatic governance.

• Enterprise strategy to architecture translation:
  Partner with executive leadership and key stakeholders to translate business strategy into enterprise architecture direction, target states, and prioritized roadmaps.
• Own the EA governance model and decision rights:
  Define and run EA governance to promote speed, coherence, and value; ensure architectural decisions are made by the right role (enterprise, solution, domain) at the right time.
• Define enterprise principles, standards, and reference architectures:
  Establish and maintain enterprise-wide principles, standards, and reference models that enable consistent solution design and reduce fragmentation.
• Cross-domain alignment and arbitration:
  Facilitate cross-domain decision-making; arbitrate architectural conflicts and tradeoffs across applications, data, security, infrastructure, and integration.
• Roadmaps, lifecycle management, and modernization:
  Lead creation of enterprise modernization roadmaps and lifecycle strategies (e.g., platform and technology lifecycle management) aligned to business capabilities and risk posture.
• Architecture as a force multiplier for delivery:
  Ensure Solution Architects and Domain Architects have clear guardrails, patterns, and reusable assets so delivery teams can move quickly while remaining enterprise aligned.

• Lead the Core EA team:
  Build, mentor, and manage a high-performing EA core that serves as the custodian of enterprise direction, governance, standards, and best practices.
• Enable the federated architecture community:
  Establish operating rhythms, forums, and collaboration mechanisms that align Enterprise Architects positioned in other teams (e.g., Security, Data) and architects embedded in delivery.
• Develop architecture talent and role clarity:
  Maintain clear role boundaries across Enterprise, Solution, and Domain Architects (and Domain SMEs), including expectations, artifacts, and engagement points.
• Stakeholder engagement and influence:
  Communicate architecture direction in business-relevant terms; build trust with leaders by balancing risk management with delivery pragmatism.

• Steward enterprise capabilities:
  Ensure enterprise-level ownership exists for critical cross-cutting capabilities (e.g., Integration Architecture, Enterprise Application Architecture, Enterprise Data Architecture, Enterprise Security Architecture, Enterprise Infrastructure Architecture) and that these capabilities produce actionable standards, patterns, and…