AEM EDS Architect

Key Responsibilities

• Define and own the target architecture for AEM Edge Delivery Services (EDS) across Genmab's 8 public sites, including Content Bus / Code Bus design and multi-site/multi-region structure
• Design the Hub Block Library governance model — the sync mechanism between hub and spoke repos, PR-based propagation, and branch protection standards
• Architect integration patterns for Salesforce (CRM/Health Cloud), SFMC, OneTrust, GA4/GTM, DocCheck/OneKey, Coveo, and IRMS MAX Web/Veeva PromoMats
• Define the region-locked delivery architecture (Fastly service + shield configuration per region) to satisfy EU-in-EU/US-in-US data residency requirements
• Own the technical boundary and handoff design between AEM EDS
• Produce reference architecture diagrams, target-state documentation, and technical decision records for client and internal stakeholders
• Provide technical governance oversight through Discovery, Build, and Hypercare
• Act as primary technical point of contact for Genmab's platform/InfoSec teams on architecture questions (e.g., instance strategy, data residency mechanics)
• Guide the AEM EDS Lead Developer and Admin + Frontend roles on implementation standards

  Required Skills & Experience

• 14+ years in enterprise web/CMS architecture, including 2+ years hands-on with AEM EDS
• Deep understanding of composable/JAMstack architecture, Git-based CI/CD (GitHub Actions), and CDN/edge delivery (Fastly or equivalent)
• Experience architecting multi-site, multi-region platforms with region-specific compliance/data residency requirements
• Familiarity with Salesforce (Experience Cloud, Health Cloud), OneTrust, GA4/GTM integration patterns
• Experience in regulated industries (pharma/life sciences preferred) — understanding of MLR approval workflows, HCP-gating, GDPR
• Strong stakeholder communication skills — able to present architecture decisions to both technical and business audiences
• Prior experience with hybrid CMS/DXP transitions (e.g., legacy platform to modern composable stack) a strong plus

  Nice-to-Have

• AEM as a Cloud Service (headful) experience, to bridge decisions across the hybrid EDS + AEM Sites model
• Experience with Universal Editor / document-based authoring models
• Prior experience in a hub-and-spoke or multi-region governance operating model