AEP Developer

Position Tittle: AEP DeveloperLocation: Malvern, PAVisa: USCDuration: long TermJob Details the Adobe Experience Platform (AEP) role below. Role OverviewThis position focuses on customer data enablement, integration, and platform configuration within the Adobe Experience Platform. Key Responsibilities - Data Enablement & Integration: Design and maintain reliable data ingestion pipelines into AEP from various digital and enterprise sources. Ensure data accuracy for analytics and personalization.- Data Modeling: Create and manage XDM schemas and datasets to support standardized customer data models and document schema intent.- Identity & Profile Management: Implement identity resolution strategies to unify customer profiles while ensuring compliance with privacy and regulatory requirements.- Audience Activation: Build and maintain audience segments for cross-channel activation and experience optimization.- Platform Integration: Integrate AEP with Adobe Analytics, CJA, Adobe Target, and Adobe Journey Optimizer to support consistent reporting and experimentation.- Governance & Privacy: Apply data governance labels and consent enforcement. Support risk assessments and audits through clear documentation and data lineage.- Operational Excellence: Monitor platform stability, troubleshoot data issues, and follow enterprise change management processes.- Collaboration: Partner with Marketing, Analytics, and Engineering teams to translate business requirements into scalable technical solutions. Qualifications - Expertise in Adobe Experience Platform (AEP)- Proficiency in SQL- Experience working with APIs Please let me know if you have any questions or need further information regarding this requirement. Note From Hiring Manager: I need assistance with the AEP Developer position. We had a few interviews but the feedback indicated the candidate lacked the practical experience with AEP. I did a quick search on AEP and AJO and found this: Can someone have experience with AEP without using AJO? While Adobe often bundles these technologies together, they serve different functions: AEP is the foundational Data Engine, while AJO is an activation application built on top of it. Here is how someone can have experience in one without the other:1. Working with AEP without AJOAn individual can be an expert in AEP by focusing solely on data ingestion, modeling, and segmentation, using other applications for activation, such as: [, ]Real-Time Customer Data Platform (RTCDP): Using AEP to build profiles and segments, but sending them to external destinations (like Facebook or Google) rather than AJO.Customer Journey Analytics (CJA): Using AEP data strictly for analysis and visualization.Adobe Target: Using AEP segments for web personalization. [, , , , ]2. The Relationship Between AEP and AJOAEP is the Foundation: AJO requires AEP to function, as it uses AEP''s unified profile and data lake.Independent Data Roles: A data engineer or data architect might spend 100% of their time building schemas (XDM), setting up datasets, and configuring data ingestion within AEP without ever creating a "journey" or email in AJO.Focus on Data over Action: As one professional noted, focusing on the "AEP Mindset" involves designing data, not just configuring the applications on top of it. [, , , , ]In summary, AEP can act as a standalone data warehouse and segmentation engine, while AJO is a specific tool designed to act on that data. You can master the data side (AEP) without mastering the activation side (AJO). []