Design a distributed customer 360 and identity resolution platform
PremiumBackend systemMedium
- Identity resolution
- Event driven architecture
- Real time synchronization
Quick answer
This backend system interview question asks you to design a distributed customer 360 and identity resolution platform. Aim for a design that meets its requirements at the stated scale, then explain its main components, data flow and trade-offs. Interviewers want to see how you scope the problem, size it and defend each choice.
The problem
Design a Distributed Customer 360 & Identity Resolution Platform (similar to Segment Personas or Salesforce Data Cloud). Enterprises collect user telemetry and records across disparate silos—websites, mobile apps, CRM databases, customer support chats, and offline purchase logs. These disconnected streams contain different identifiers (cookies, device IDs, emails, phone numbers, hashed login IDs). The platform must ingest millions of events per second, execute near-real-time identity graph merging to link anonymous and known sessions into a single canonical customer profile, and synchronize the unified profile down to downstream personalization and marketing endpoints.
What must a distributed customer 360 and identity resolution platform do?
- Ingestion Pipeline: Accept high-volume streaming telemetry and batch batch-import records containing various identifier types.
- Identity Resolution: Dynamically correlate incoming identifiers with existing identity graphs to merge or split profiles when new linkage data arrives.
What scale should you design for?
Use these numbers in your estimates.
The scale numbers unlock with this questionUnlock
Key concepts
- Identity resolution
- Event driven architecture
- Real time synchronization
- Data pipelines
- Distributed storage
How you’ll practise
- Requirements
- Estimate
- API and data
- High-level design
- Deep dives
- Wrap-up
Lala, personalized to you, gives a hint when you ask and reviews your design when you are ready.
What do interviewers look for?
In any backend system design round.
- Clarifies the requirements before drawing anything
- Uses a few numbers that actually change the design
- Draws a clear path from the client to storage
- Picks storage and caching with reasons, not by habit
- Explains what breaks first under load and how to fix it
- States trade-offs openly instead of claiming a perfect design
Questions people ask about this interview question
- Which design type is this question?
- It is a backend system question. You design a distributed customer 360 and identity resolution platform and explain your choices the way you would in an interview.
- Is this question asked at entry level?
- It is marked Medium. Entry-level engineers can practise it, but it expects you to reason about requirements and trade-offs, not only list components.
- What should I cover first?
- Start with the requirements: what the system must do, how well it must do it and which numbers change the design. Agree on scope with the interviewer before you design anything.
- Can I practise it for free?
- It is a premium question. Sign up and unlock it once for 10 credits; it then stays unlocked. When you finish, Lala, your personalized AI mentor, can review your design for 30 credits.
Related questions
Updated · Written by the SevyDevy team