Principal Customer Data Platform Engineer

Key Highlights

• Customer data architecture — from collection across web and app, through ingestion and modelling, into the activation surfaces where the business acts on it. Set the architectural patterns for client and server-side capture, and the boundary between real-time and batch.
• Identity resolution: how users, devices, accounts, and sessions are stitched together across web and app, how that resolution is exposed to downstream consumers, and how it runs in production.
• Event schema architecture, versioning, and enforcement mechanisms — contracts, validation, schema registry, CI checks — that turn agreed event definitions into reliable, governed data. Partner with Product Analytics on the taxonomy and naming conventions; you own how the platform makes them real.
• Consent architecture end-to-end: how consent is captured, propagated, stored, honoured at activation, and audited across regions and across the full chain from event collection to MarTech, so compliance is enforced architecturally rather than per-implementation.
• Establishing quality, lineage, and observability across customer-data flows so issues are detected upstream — not by analysts noticing broken numbers.