Adobe Campaign is one of the harder marketing technology roles to hire for, and most interview guides you will find make it harder. They are still written for Campaign Classic — schema questions, workflow activities, JavaScript in a delivery. Those questions are fine. They just no longer separate the candidates.
The platform moved. Campaign v8 did not add features on top of Classic; it changed where data lives and where campaigns execute, and in doing so it removed capabilities that Classic developers built entire integration patterns around. A candidate who has run a v7-to-v8 migration and one who has only worked on Classic will answer identically on schemas and diverge completely on architecture.
Ask about the architecture first. Everything else in an Adobe Campaign interview is downstream of whether the candidate understands where the data actually is.
These are the questions we use when we screen Adobe Campaign developers, and what a strong answer sounds like.
Start with the architecture, not the syntax
Adobe’s own transition documentation is blunt about the shift: Campaign v8 relies on a hybrid architecture, and if you are coming from Classic v7, all deliveries now go through the mid-sourcing server.
The deeper change is storage. In an Enterprise deployment, Campaign v8 splits into two databases: a local Campaign database for the user interface, real-time messaging and unitary queries, and a cloud Snowflake database for campaign execution, batch queries and workflow execution. Adobe calls this Full Federated Data Access, and describes it simply — all data is now remote on the cloud database.
Question: Walk me through where data lives in a Campaign v8 Enterprise deployment, and which operations hit which database.
This is the single most efficient question in the loop. A candidate who has worked on v8 will separate the local instance from the cloud database without prompting and will tell you which side batch execution lands on. A candidate who has only worked on Classic will describe one database, because on Classic there is one.
It is also worth knowing that the cloud side is Snowflake. Campaign developers who have picked up real cloud data warehouse fluency are a materially different hire from those who have not — they debug performance problems the rest of the team escalates.
Ask what the migration broke
Migration questions work because they are unfakeable. Someone who has done one remembers what stopped working; someone who has read about one remembers the marketing.
Three things in Adobe’s documentation make excellent yes-or-no probes.
Internal routing. Adobe states that internal routing is not possible in Campaign v8, and the external account has been disabled accordingly. Ask a candidate how they handled routing on their last v8 project. If they describe an internal routing setup, they either have not worked on v8 or were not close to the delivery configuration.
Delivery status timing. On v8, delivery statuses are not instantly updated — a technical process runs on the marketing instance and updates them in a timely manner. Ask: how did you handle reporting that depended on delivery status? Strong candidates have a real answer, usually involving reporting lag they had to explain to a stakeholder. It is a small detail that only shows up when you have shipped on the platform.
Deployment model. Campaign v8 is available only as a Managed Cloud Service and cannot be deployed on-premise or hybrid. Candidates who spent their careers on on-premise Classic installations sometimes have not internalised this, and it changes what they can and cannot control.
Probe the guardrails, because that is where the work is
Adobe publishes a guardrails and limitations page for Campaign v8, and it is the best interview prep document available to a hiring manager. Three items in it generate better questions than anything in a generic question bank.
| Guardrail | What Adobe states | What to ask |
|---|---|---|
| Data replication | No bi-directional data replication is provided; replication happens only from the Campaign local database to the cloud database | How did you handle a use case that needed data written back to the local database? |
| Consent processing | Opt-in, opt-out and mobile registration are asynchronous processes, processed each hour through a technical workflow | How did you set expectations with compliance or marketing on unsubscribe timing? |
| Duplicates | Duplicates need to be handled manually by end-users | What was your deduplication process, and who owned it? |
The replication question is the strongest of the three. One-directional replication invalidates a whole family of patterns that worked on Classic, and a developer who has hit that wall will describe the redesign in specifics. A developer who has not will tell you replication is bi-directional, or hedge.
The consent question matters for a different reason. Hourly asynchronous processing of opt-outs is a real operational constraint, and someone who has managed it has had the conversation with a compliance stakeholder. That is a maturity signal as much as a technical one — the same signal we look for across marketing operations hires.
Test the interface transition separately
Campaign v8 introduced a web user interface alongside the client console, and the transition is incomplete by design. Adobe’s FAQ states that the Campaign Client Console can be used in parallel to the new interface, and that there are capabilities not available in the new user interface for now.
The workflow documentation is more specific: workflow activities that are not yet supported in the Campaign web user interface are read-only and displayed as incompatible activities. The workflow still runs. You simply cannot edit those activities from the web.
Question: Your team is standardising on the web UI. A legacy workflow contains activities the web interface shows as incompatible. What do you do?
The answer you want is unglamorous: keep the client console for those workflows, plan the rebuild deliberately, do not rewrite working automation to satisfy a tooling preference. Candidates who immediately propose rebuilding everything in the web UI are telling you how they will spend your first quarter.
Separate the platform from the adjacent stack
Adobe Campaign rarely runs alone. It sits next to Experience Platform, often alongside Marketo, and increasingly next to Journey Optimizer. Candidates vary enormously in how much of that surface they have actually touched.
Two questions worth asking:
- Which systems fed audiences into Campaign at your last role, and who owned that pipeline? This tells you whether they were a builder or a recipient — both are hireable, but for different roles.
- What did you own end to end, and what did you hand off? Campaign developers who have only ever executed someone else’s segmentation are a different hire from those who built it.
Be honest with yourself about which one the role needs. The most common Adobe Campaign hiring mistake we see is a job description that describes an architect and a compensation band that pays for an executor.
What a strong answer actually sounds like
Across every question above, the same tell separates real experience from rehearsed experience.
Rehearsed answers are clean. They describe how the platform is supposed to work, in the order the documentation presents it. Real answers are messier and contain a constraint — a thing that did not work, a stakeholder who had to be told something they did not want to hear, a workaround that survived into production.
When a candidate says the migration went smoothly, ask what slipped. There is always something. A candidate who cannot name one is either very junior or narrating a project someone else ran.
How to run the loop
Adobe Campaign talent is scarce, and scarcity punishes slow processes. Three conversations is the ceiling:
- Platform screen. Where does data live in v8, and what did the migration break. Twenty minutes tells you most of it.
- Applied round. One real problem from your environment — a workflow, a replication constraint, a deduplication mess. Ask them to talk through the approach rather than write code cold.
- Stakeholder conversation. Campaign developers sit between marketing and engineering. If they cannot explain hourly opt-out processing to a non-technical stakeholder, that is the job, not a detail.
If you are still on Classic v7 and hiring now, hire for both. Adobe has said Classic v7 will reach end of support, and a Classic-only hire is a hire you will be making again on a shorter timeline than you would like. The candidates who can work across both are the ones worth moving quickly for — and in a pool this thin, moving quickly is most of the advantage. That is as true here as it is anywhere else in technical recruiting.
