DE&A - Core - Analytics - Adobe Customer Data Platform

Role Summary The AEP CDP Data Architect is responsible for designing, governing, and evolving Adobe Experience Platform data architecture with a specific focus on Real‑Time Customer Data Platform (RT‑CDP) capabilities. This role ensures customer data is ingested, modelled, unified, governed, and activated in a scalable, compliant, and business‑ready way.

The architect acts as the owner of the AEP data layer, working closely with solution architects, engineers, marketing stakeholders, and security/privacy teams to translate business use cases into robust AEP designs that support real‑time personalization, analytics, and omnichannel activation.

At Zensar, we’re “experience-led everything”. We are committed to conceptualizing, designing, engineering, marketing, and managing digital solutions and experiences for over 130 leading enterprises. We are a company driven by a bold purpose:
Together, we shape experiences for better futures. Whether for our clients, our people, or the world around us, this belief powers everything we do. At the heart of our culture is ONE with Client - a set of four core values that reflect who we are and how we work:
One Zensar, Nurturing, Empowering, and Client Focus. Part of the $4.8 billion RPG Group, we’re a community of 10,000+ innovators across 30+ global locations, including Milpitas, Seattle, Princeton, Cape Town, London, Zurich, Singapore, and Mexico City. Explore Life at Zensar and join us to Grow. Own. Achieve. Learn. to be the best version of yourself. We believe the best work happens when individuality is celebrated, growth is encouraged, and well-being is prioritized.

We are an equal employment opportunity (EEO) and affirmative action employer, committed to creating an inclusive workplace. All qualified applicants will be considered without regard to race, creed, color, ancestry, religion, sex, national origin, citizenship, age, sexual orientation, gender identity, disability, marital status, family medical leave status, or protected veteran status.

Required Skills & Experience5+ years experience in a Data Architect role Strong hands‑on experience with Adobe Experience Platform, ideally including Real‑Time CDP & other Adobe solutions

Proven experience in data architecture, enterprise data design, or solution architecture roles.

Strong understanding of:

Event‑driven data models

Customer data modelling patternsAPIs, JSON, and data transformation concepts

Experience working with cloud data ecosystems (Azure, AWS, or GCP).Strong understanding of GDPR and privacy‑by‑design principles in customer data platforms.

Soft Skills Able to communicate complex data concepts clearly to both technical and business audiences.

Confident working in client‑facing or stakeholder‑heavy environments

Key Responsibilities Design and own the end‑to‑end AEP / RT‑CDP data architecture, including ingestion, XDM modelling, identity resolution, profile enablement, and activation.

Define Adobe XDM schemas (Profile‑enabled and non‑profile), datasets, and data flows aligned to current and future use cases.

Establish architectural standards for batch, streaming, and real‑time ingestion patterns within AEP.Ensure AEP architecture supports scalable, multi‑brand, multi‑region use cases where applicable.

Lead the design of data ingestion from various source systems

Define event vs profile modelling strategies using best‑practice XDM patterns.

Partner with Data Engineers to ensure ingestion pipelines are efficient, resilient, and documented.

Design and govern identity resolution strategies, including identity name spaces, stitching logic, and merge policies within RT‑CDP.Define profile enablement rules and activation readiness criteria

Translate business and marketing requirements into clear AEP data blueprints and solution designs.

Act as the primary AEP data authority during solution design and delivery phases.

Support delivery teams with design reviews, risk identification, and architectural decisioning.

Clearly communicate architectural trade‑offs to senior technical and non‑technical stakeholders

Posting Date: