Role: CMS Architect (SAP Commerce Cloud, Headless)
Duration: 6+ Months Remote
US Remote
Key Responsibilities
· Lead architecture definition for a headless CMS-driven ecosystem supporting:
· Web storefront
· Native mobile applications
· Define content model and content delivery strategy across channels
· (authoring, localization, personalization, reuse)
· Determine optimal frontend architecture, including:
· Full headless vs hybrid (coexistence with accelerator)
· SSR/static rendering considerations
· Performance and SEO implications
· Define integration approach between CMS and:
· SAP Commerce (OCC APIs)
· Firebase / mobile app layer (or its replacement)
· Martech tools (Tealium, Optimizely, Coveo)
· Evaluate and recommend:
· Need and scope of a BFF layer (where it adds value vs unnecessary complexity)
· API orchestration vs direct integrations
· Develop a phased migration strategy, including:
· Coexistence of legacy and new experiences
· Rollout sequencing across brands/domains
· Provide TCO and operational model guidance, including:
· Build vs run costs
· Team structure and skill implications
· Support CMS selection, ensuring architectural alignment during RFP process
Required Experience:
· Deep experience with headless CMS platforms (Contentful, Contentstack, Optimizely CMS, Magnolia, etc.)
· Strong background in SAP Commerce Cloud (Hybris) or similar enterprise commerce platforms
· Proven delivery of multi-channel (web + mobile app) content architectures
· Experience designing hybrid architectures (not just greenfield headless builds)
· Solid understanding of:
· API-first and event-driven architectures
· SSR / CDN / edge delivery models