How to test an AEP developer before you hire

Why this matters

This matters because CVs and certifications only show past learning — not whether a candidate can actually configure and troubleshoot real AEP setups. Without a practical test, hiring managers risk hiring someone who understands theory but cannot build or fix live data flows, especially around critical components like schema design or identity resolution.

A break-fix task reveals how well a candidate diagnoses issues — like why data fails to reach Profile — which is central to day-to-day work. Without such testing, teams may face delays, data gaps, and misconfigurations that impact customer journey insights. Practical assessments ensure candidates can operate in real environments, reducing onboarding time and technical debt.

The key ideas

When hiring for Adobe Experience Platform roles, rely on practical tests rather than CVs or certifications. These documents only show what a candidate has studied, not whether they can build a real working setup. A practical test gives hiring managers a clear view of hands-on ability—like designing a schema, setting up identity, or enabling a dataset for Profile.

The best tasks reflect real-world challenges. For example, having a candidate troubleshoot why data doesn’t reach Profile shows how they diagnose issues. A break-fix scenario, where faults are planted in the system, reveals problem-solving skills that are essential in day-to-day work. These tests are scored automatically, ensuring consistency and recording each step as completed.

Before starting, clearly state whether candidates can use documentation or AI assistants. This transparency helps avoid bias and ensures fair evaluation. Tests are run in independent practice labs, without requiring an Adobe license. This setup lets hiring teams assess true technical ability—especially around schema design and Profile integration—without relying on past experience alone.

How to apply it

Start by defining the tasks in advance—such as designing a schema, setting up an identity, or enabling a dataset for Profile. These are practical, real-world tasks that reflect actual work in Experience Platform. Set a clear time limit and ensure all candidates work in a live, sandboxed environment where they can see data flow. Include a break-fix scenario where faults are intentionally planted—like a missing identity or a misconfigured dataset—so the candidate must diagnose and resolve the issue. This reveals how well they troubleshoot, which is central to the job. Use automatic checks to track progress and verify each step was completed, ensuring consistent evaluation across candidates. Before the test begins, explicitly state whether documentation or AI tools are allowed, so candidates know the rules. Run the assessment in an independent practice lab where the environment is fully functional and isolated. This setup allows for fair, objective scoring without relying on Adobe licences. The result is a practical, reliable way to assess technical ability beyond what a CV or certification shows. This method identifies candidates who can not only configure but also debug and maintain real implementations.

Mistakes to avoid

• Relying on CVs or certifications to judge technical ability is a mistake. These documents show academic background but not hands-on skill. A candidate may have studied schema design or Profile integration but fail to implement it correctly in a live environment. Always verify capability through practical tasks.

• Allowing candidates to use AI tools or documentation without clear rules leads to inconsistent results. Without predefined rules, some candidates may bypass problem-solving and rely on external sources. Set clear guidelines in advance—whether AI or documentation is allowed—and ensure all candidates follow the same rules. A break-fix task with known faults is more revealing than a theoretical question. Use automated checks to objectively measure progress and completion, reducing bias and ensuring fairness.

Quick checklist

• Confirm the candidate’s ability to design a schema and set up identity in a real AEP environment within a time limit
• Set a clear, pre-agreed task list including schema design, identity setup, and enabling a dataset for Profile
• Include a break-fix scenario where data fails to reach Profile to assess diagnostic skills
• Define in advance whether documentation or AI assistants are allowed and communicate this to candidates
• Use automatic checks to evaluate each step consistently and record completion times
• Ensure the test environment is isolated and runs in AdsBot’s independent practice labs, without requiring an Adobe license
• Limit the test to realistic, hands-on tasks that reflect actual implementation challenges, not just theoretical knowledge
• Review results through objective scoring to identify candidates who can troubleshoot and configure working implementations