> Markdown version of [/jobs/ext/4452312-aem-eds-architect](https://www.wearedevelopers.com/jobs/ext/4452312-aem-eds-architect). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# AEM EDS Architect

- **Company:** TekFortune INC
- **Location:** Plainsboro Township, NJ, United States
- **Experience:** Experienced
- **Contract:** Permanent contract
- **Skills:** Cloud Computing, Cyber Security, Continuous Integration, Github, Google Analytics, Cloud Services, Salesforce.Com, Git, Front End Software Development, Veeva
- **Published:** October 17, 2026
- **Apply:** https://www.careerbuilder.com/job-details/aem-eds-architect-plainsboro-nj--eb6aa8fb-e636-4723-8400-db8f2166a7f4

## About the Role

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

## Description

### Role Summary Owns end-to-end technical architecture for hybrid AEM EDS platform - defining the Hub Block Library structure, integration patterns, region-locked delivery design, and hub-and-spoke governance model across all 10 in-scope sites.### 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