Adobe Experience Platform

Role Title:Adobe Experience Platform (AEP / RTCDP) & Journey Optimizer (AJO) Technology Lead Location:Madrid (Hybrid) Language:Spanish (must)+ English (professional) Engagement:On-site client‑facing roleHaga clic en "Solicitar" a continuación para enviar su candidatura. Asegúrese de que su CV está actualizado y de que ha leído primero las especificaciones del puesto.ROLE PURPOSE Own the end‑to‑end Adobe Experience Cloud activation for BFS Customer across: • AEP / RTCDP: identity, schemas, datasets, ingestion, destinations, audience/suppression • AJO: multi‑step journey orchestration with robust eligibility, arbitration, fatigue/fallback, and error handling • CJA alignment: minimal viable data views and KPI scorecards to close the loop and optimize performanceKEY OUTCOMES (KPIs) • RTCDP audience readiness and activation to native destinations (delivery health ≥ 99% successful pushes) • Identity survivorship/recency implemented and validated (join accuracy & profile merge quality) • Journeys released on schedule (≥ 99% end‑to‑end delivery success) with measurable KPI uplift – e.g., CPA↓ via suppression, CVR↑, funded‑account rate↑, offer acceptance↑ • Governance adherence across BU waves: entry/exit gates passed; consent/approvals auditableCORE RESPONSIBILITIES A) Architecture & Governance (AEP/RTCDP) • Define and maintain the AEP/RTCDP blueprint per BU (Retail, SME, etc.) with clear entry/exit criteria • Author stewardship processes, attribute gap logs, and data contracts; enforce legal bases (GDPR/ES) • Set identity namespaces, merge policies, survivorship & recency logic with full auditability • Establish consent orchestration (purpose limitation, opt‑in/out) embedded in activation flows B) Data Modeling & Ingestion (AEP/RTCDP) • Design XDM profile/event schemas and datasets using a minimal‑viable‑first approach, extensible later • Map source systems (online/offline) and configure streaming/batch pipelines (freshness & completeness SLAs) • Validate ingestion hygiene, identity stitching, and release readiness for destinations C) Audiences, Destinations & Suppression (RTCDP) • Build high‑value audiences and suppression segments; prefer native destination configuration • Document destination hygiene (failure handling, retries, monitoring, alerting); reduce media waste D) Journey Design & Build (AJO) • Configure triggers, branching logic, channel actions; codifyeligibilityrules from RTCDP attributes/events • Implementarbitration(prioritization, suppression, mutual exclusivity) for offers and actions • Definefatigue thresholds ,fallback actions , anderror handling(retries, notifications) • Maintain reusable journey templates for BU‑by‑BU scale; run release checklists and rollback plans E) Orchestration & Content (AJO + AEM/Target) • Coordinate with AEM/Target for content containers/cards and template‑driven personalization • Ensure timing, content, and branching are governed by journey guardrails and compliance checkpoints F) Data & Measurement Alignment (RTCDP + CJA + AJO) • Partner with CJA to publishminimal viable data views , funnels/cohorts, uplift dashboards, and scorecards • Close the optimization loop: use CJA insights to adjust journey timing/logic/content and audience criteria • Document analytics playbooks (metrics dictionary, QA checks, anomaly handling) and reporting cadence G) Compliance & Governance (cross‑stack) • Embed consent/approval checkpoints throughout journeys and activations; maintain audit trails • Maintain catalog/versioning for journeys and audiences; adhere to BU entry/exit gates • Coach BU data stewards and marketers (in Spanish) on BAU runbooks and governance standardsREQUIRED EXPERIENCE & SKILLS • 8–12 years in martech/data architecture and journey orchestration;3+ years hands‑on AEP/RTCDPand2+ xiphteb years AJO • XDM modeling, identity stitching, ingestion pipelines, native destinations, segment activation • Journey design with eligibility, arbitration, fatigue/fallback, error handling at scale • Strong JSON/API and streaming/batch data patterns; governance in regulated BFS (GDPR/ES) • Spanish (B2+/native), English (B2+); excellent stakeholder leadership and Spanish‑language facilitationGOOD‑TO‑HAVE •Adobe Launch(Web SDK / Edge): consent‑aware tagging, event taxonomy, data‑layer QA •Adobe Analytics(Workspace): complementary funnels/cohorts and rapid diagnostics alongside CJA • Familiarity with AEM/Target personalization containers/cards and template‑driven deliveryBEHAVIORAL COMPETENCIES • Architecture storytelling in Spanish; governance‑first, risk‑based decisioning • Customer‑centric orchestration mindset with test‑and‑learn optimization discipline • Structured problem‑solving, decisive execution, and collaborative leadership across business/marketing/ITCOMPLIANCE & ELIGIBILITY • EU work authorization; strong awareness of GDPR/ES consent, data privacy, and channel policy • Ability to operate onsite in Spain; hybrid onsite/Teams; near‑shore cadence aligned to BU waves