Questions › Technical PM › Uber
Design a privacy-safe personalization system for Wallet
- Technical PM
- Uber
- Medium
- 10 min
Problem Statement Description
Product context: Uber is a mobility and delivery platform; its products include rides, Uber Eats, grocery and retail delivery, freight, driver and courier tools, and marketplace pricing.
Uber wants to make Wallet more useful for restaurant-related experiences, such as helping restaurant merchants, operators, or relevant Uber Eats users see timely wallet actions, balances, credits, payment options, promotions, refunds, or payout-related information without exposing sensitive financial, business, or behavioral data unnecessarily.
Your task is to design a privacy-safe personalization system for Wallet in this context. The system should determine what personalized wallet content or actions to show, when to show them, and how to support personalization while respecting user consent, data minimization, financial-data sensitivity, regional privacy requirements, and Uber’s marketplace reliability expectations.
This is a Technical PM design question. Focus on the product requirements, system interfaces, data flows, privacy and security constraints, experimentation approach, observability, and trade-offs between personalization quality, operational complexity, latency, trust, and compliance.
The experience should consider:
- The primary users and workflows, such as restaurant owners/managers managing payouts, credits, promotions, billing, refunds, or payment methods.
- What personalization means in Wallet and which surfaces, triggers, or recommendations are in scope.
- What data may be used, what data should be restricted, and how consent, retention, purpose limitation, and user controls should work.
- APIs, data pipelines, identity mapping, eligibility logic, and decisioning services needed to power the experience.
- Reliability, latency, fallback behavior, auditability, and observability requirements for financial-adjacent experiences.
- Privacy, security, fraud, abuse, and compliance risks across global markets.
- Rollout strategy, experimentation, success metrics, guardrails, and rollback criteria.
The goal is to define a technically credible product design that enables useful Wallet personalization for Uber’s restaurant ecosystem while preserving user trust, protecting sensitive data, and supporting scalable global operations.
What this question tests
- Technical Fluency
- Systems Thinking
- API/Data Judgment
- Reliability Awareness
Practise this question under interview conditions. Answer it out loud against a timer with an AI interviewer that asks follow-ups, then review the scored report.
Related Technical PM questions
- What API and data model would support a new Transit workflow for commutersUber · Technical PM · Medium
- How would you improve reliability and latency for AdsUber · Technical PM · Medium
- What API and data model would support a new Transit workflow for commutersUber · Technical PM · Easy
- How would you improve reliability and latency for AdsUber · Technical PM · Easy
- Explain the technical trade-offs of adding AI capabilities to Uber EatsUber · Technical PM · Easy
- Design a privacy-safe personalization system for FreightUber · Technical PM · Easy
All Technical PM questions · Product manager interview questions by skill area