Senior Technical Consultant/Architect - ACC/AJO

The opportunity:

We seek Senior Consultants and Architects with deep, hands-on expertise in Adobe Campaign Classic (ACC), Adobe Campaign Standard (ACS), Adobe Experience Platform (AEP), and Adobe Journey Optimizer (AJO) to help enterprise customers modernize campaign and customer-journey programs. The role leads discovery, current-state assessment, target-state architecture, implementation, integration, testing, coexistence, cutover, and enablement. You will understand how customers use ACC or ACS today, identify use cases suited to AJO, and redesign them for AEP and AJO. Some functionality must be rebuilt, redesigned, retained, or handled through an integration or alternative solution. Candidates must explain product boundaries, assess feature and use-case fit, surface gaps early, and set realistic customer expectations. In AJO, a migrated use case lands on AJO Journeys (profile-centric, event-driven orchestration on AEP Real-Time Customer Profile) or AJO Orchestrated Campaigns (campaign-centric, batch, multi-step workflows on the AEP relational data store). Candidates must design and build on both, and recommend the right path per use case.

What you'll be doing:

• Lead discovery workshops with marketing, campaign operations, data, architecture, security, mobile, and IT stakeholders.
• Inventory the Campaign estate: use cases (batch, scheduled, transactional, event-triggered, real-time); assets (campaigns, workflows, audiences, deliveries, templates, content blocks, personalization, typologies, suppression rules, reporting); data (schemas and extensions, custom resources, relational data, targeting dimensions, identifiers, consent, opt-out, quarantine, bounce, engagement history); and infrastructure (on-premises or Managed Services hosting, network access, firewalls, file transfer, decommissioning needs).
• Reverse-engineer custom logic and document the business rules: technical and marketing workflows (query, enrichment, split, deduplication, reconciliation, update data, JavaScript code activities), custom JavaScript, JSSP, SOAP/JS API calls, SQL functions, stored procedures, custom relational structures, typology rules, input forms, web applications, landing pages, subscriptions, Message Center, Triggers/pipeline, offer logic, external accounts, APIs, middleware, and enterprise integrations.
• Map each use case and dependency to an AJO/AEP target pattern and classify it as reuse, redesign, rebuild, integrate, defer, or retain elsewhere. For custom logic, decide whether to re-express it in AEP/AJO (data model, Query Service, custom actions, external services), redesign or rebuild it separately, or retain it in Campaign.
• Choose the execution path per use case based on the target customer experience, not the shape of the source Campaign workflow. Use AJO Journeys when each profile should progress individually based on behaviour, events, or elapsed time, including many scheduled and recurring Campaign workflows rebuilt as Read Audience or business-event journeys. Use Orchestrated Campaigns for relational or multi-entity data, complex audience construction and enrichment, exact pre-send counts, and multi-level sending. Use action campaigns for simple scheduled or API-triggered sends. Document the rationale, combined patterns, and license prerequisites.
• Surface product-fit gaps and operational impacts before committing to scope or feature-parity claims. Advise when Campaign coexistence or another path fits better.
• Develop phased roadmaps, effort estimates, dependency plans, risks, and customer decision points.
• Design the AEP foundation: XDM schemas and field groups (profile, event, lookup); identity namespaces, identity resolution, profile enablement, and data relationships; datasets, sources, destinations, batch and streaming ingestion, and event design; data quality and governance; audience qualification and segmentation; and Query Service or other processing for transformation, aggregation, and enrichment.
• Replace common Campaign data patterns with AEP capabilities: Federated Audience Composition on Snowflake, Google BigQuery, Databricks, or other warehouses; computed attributes for profile-level aggregates; Data Distiller for scheduled SQL transformations; merge policies; and profile and segmentation guardrails.
• Design customer experiences and build AJO journeys and campaigns across batch and event-driven engagement: event- and segment-triggered orchestration, conditions, actions, custom actions, message content, personalization, and decisioning.
• Apply journey and campaign governance and optimization: business rules, frequency capping, quiet hours, journey priority and arbitration, conflict management, wave sending, content experimentation, and decisioning policies and rankings.
• Define security, access, permissions, governance, and operational controls.
• Configure AJO channels end to end: email, mobile and web push, in-app, web, code-based experiences, content cards, inbox, live activities, SMS/MMS, RCS, WhatsApp, LINE, and direct mail. Cover channel configurations, subdomains, API credentials, feedback webhooks, mobile app and SDK dependencies, channel-specific data and consent requirements, and template approval rules.
• Connect messaging providers: native SMS providers, bring-your-own-provider setups with provider payloads, inbound keyword handling, delivery receipts, and opt-in/opt-out webhooks and flows; and Channel Builder custom channels for non-native platforms or customer-owned gateways, covering endpoint, authentication, throttling, payload structure, and monitoring.
• Design and build integrations using supported APIs, source connectors, file exchange, middleware, or Adobe solution integrations, including custom actions that call external systems from journeys with request/response schemas, authentication, capping, throttling, retries, and error handling.
• Implement event and API-triggered patterns: unitary and business events, API-triggered and transactional campaigns, Journey and Campaign APIs, and streaming ingestion via HTTP API.
• Select and configure the journey entry pattern per use case: unitary-event journeys for behavioural and transactional signals; audience qualification journeys on streaming audiences for real-time lifecycle moments; Read Audience journeys, one-shot or recurring with incremental read, for scheduled and batch-initiated programs that previously ran as recurring Campaign workflows; and business-event journeys that release an audience when an operational event occurs. Configure identity namespaces, reentrance and wait periods, exit criteria, and time zones.
• Build multi-step journeys where each customer progresses at their own pace: Wait activities; the Optimize activity for conditions, path targeting, and path experiments; reaction events on opens and clicks with timeout paths; Update Profile; Content Decision for offers; external data sources and custom actions for real-time lookups and system writebacks; and Jump activities to split complex programs into reusable journeys.
• Use supplemental identifiers, where enabled, to run one journey instance per entity and personalize with its attributes. Decide when per-entity use cases fit journeys versus orchestrated campaign multi-level sending.
• Support phased migration and coexistence from the journey canvas, including Adobe Campaign v7/v8 and ACS actions that let AJO orchestrate while Campaign transactional messaging delivers, until channels and content move to native AJO.
• Design within journey guardrails and flag gaps to the customer early.
• Design the data model with AEP relational schemas: tables, primary and composite keys, version descriptors, ENUMs, data governance labels, identity fields mapped to identity namespaces, and links with correct cardinality to recipient and profile entities.
• Configure target dimensions, including the profile target dimension linking XDM profile and experience event data to relational data; decide what belongs in the profile store versus relational tables to avoid duplication.
• Set up Change Data Capture ingestion from supported sources and plan deletion handling and latency.
• Build multi-step canvases with targeting, flow control, and channel activities, including multi-entity segmentation and multi-level sending personalized with enriched relational attributes. Configure scheduling, recurring runs, and pre-send count validation.
• Design within orchestrated campaign guardrails and flag gaps to the customer early.
• Translate the ACC/ACS relational data model to AEP: map recipient, custom, and relational tables to XDM profile, experience event, and lookup schemas, or to relational schemas for orchestrated campaigns; define primary and secondary identities, relationships, cardinality, and denormalization trade-offs.
• Migrate historical and operational data via batch backfill, delta loads, and reconciliation reports. Map ACC/ACS denylist and subscription data to the AEP Consent and Preferences field group and AJO subscription lists; load quarantined and bounced addresses into the AJO suppression list so blocked recipients stay blocked from day one.
• Rebuild Campaign workflow logic according to the chosen path. For journeys, express targeting as AEP audiences and computed attributes, recurring workflows as scheduled Read Audience journeys, and waits, splits, and tests as Wait and Optimize activities. For orchestrated campaigns, rebuild queries, enrichments, splits, union/intersection/exclusion, deduplication, change dimension, and reconciliation as canvas activities. Move logic neither canvas supports to the source system, Query Service or Data Distiller, or external services.
• Re-architect lifecycle programs built in Campaign as chained or recurring workflows into journeys, replacing workflow-based state tracking with journey state, reentrance rules, and exit criteria.
• Convert ACC/ACS HTML content, templates, and personalization to AJO content templates and Handlebars/PQL. Validate matching output with seed and test profiles.
• Map Message Center, Triggers/pipeline, and other transactional or signal-driven flows to AJO unitary-event journeys or API-triggered campaigns, and typology, pressure, and fatigue rules to AJO business rules, frequency capping, suppression rules, and quiet hours.
• Migrate ACC Interaction offer logic to AJO Decisioning, including decision items, collections, selection strategies, ranking formulas or AI models, and capping.
• Rebuild Campaign landing pages, subscription and preference centers, web and survey forms, ACC web applications, and JSSP pages as AJO landing pages, subscription lists, or customer-owned web front ends connected through AEP APIs, writing consent and preferences back to AEP.
• Establish development, test/stage, and production delivery practices with Git version control and a sandbox strategy. Support controlled promotion and release management with AEP sandbox tooling packages.