Job Description & Details
This is a heavy-duty tracking and data architecture gig where you will be elbows-deep in migration work, moving legacy setups over to the Adobe Experience Platform. If you enjoy untangling messy data layers and getting Web SDK to behave properly, this contract gives you a clear runway to do just that over the next several months.
What You'll Actually Be Doing
You will spend your days architecting tracking plans, auditing existing legacy implementations, and executing migrations to Adobe Web SDK and AEP. Expect to coordinate closely with developers and stakeholders to map out schemas and XDM data objects correctly the first time, ensuring downstream reporting doesn't break during the transition. You'll be troubleshooting data collection bugs in Adobe Launch and validating that events fire precisely when they are supposed to across complex web applications.
The Core Tech Stack
You need absolute fluency in Adobe Analytics, Adobe Launch (Data Collection), and Web SDK. This isn't a basic reporting role; you must intimately understand AEP components like schemas, datasets, and XDM because the entire project hinges on your ability to migrate legacy architecture cleanly. Having a broader grasp of the Adobe Experience Platform beyond just the migration scope will definitely make your life easier here.
Interview Expectations
Be ready for the hiring manager to throw a scenario at you where a critical event payload fails to map correctly to an XDM schema in AEP, asking you to walk them through your exact debugging workflow from the browser console to the data collection layer. They want to see that you can troubleshoot under pressure without breaking existing production analytics. You should also expect a deep dive into how you handle data governance and identity stitching when moving from legacy eVars and props over to modern Web SDK payloads.
Application Advice
Skip the generic marketing speak on your resume and put your specific migration metrics front and center, highlighting the exact number of properties or domains you have transitioned to Adobe Web SDK. Make sure keywords like Adobe Launch, XDM schemas, and data collections are explicitly visible in your experience section so you can easily clear the initial automated keyword filters.