Estimate infrastructure or operational capacity needed for Uber One at global scale

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 is evaluating what it would take to support Uber One as a global membership program across mobility, delivery, and related marketplace use cases. The estimate should account for both digital infrastructure needs, such as subscription management, entitlement checks, payments, promotions, notifications, and support systems, as well as operational capacity implications across riders, eaters, couriers, drivers, merchants, and local markets.

Frame the problem as a global-scale guesstimate: define what “capacity” means, choose the relevant units of measurement, and estimate the volume of users, transactions, membership events, support contacts, and marketplace interactions Uber One may generate. The focus is not to design the product, but to size the systems and operations needed to reliably serve members while preserving marketplace liquidity, driver/courier experience, reliability, safety, and unit economics.

Your estimate should make assumptions explicit, separate global averages from market-specific variation, and identify which inputs would most change the answer. Consider how Uber One usage may differ across ride-hailing, food delivery, grocery, and other services, and how subscription benefits could affect trip frequency, peak demand, support load, and supply-side operational needs.

The experience should consider:

- The scope of capacity being estimated: compute/API load, payment and billing operations, customer support, local operations, driver/courier supply, or a clearly defined combination.

- The primary unit of estimation, such as monthly active members, daily transactions, entitlement checks, support contacts, concurrent requests, or operational headcount.

- The addressable population and adoption assumptions across major Uber markets, including differences between mature and emerging markets.

- Member behavior assumptions, including trip/order frequency, benefit redemption rate, cross-product usage, churn, and seasonality.

- Driver and courier implications, including incremental demand, peak-time pressure, incentives, reliability expectations, and local marketplace balance.

- Sensitivity of the estimate to key variables such as penetration rate, order frequency, support contact rate, benefit complexity, and geographic rollout pace.

- Sanity checks against marketplace scale, payment volume, operational staffing ratios, and expected reliability thresholds.

- Constraints such as latency, uptime, fraud prevention, regulatory differences, local payment methods, and customer support language coverage.

The goal is to produce a structured, defensible estimate of the infrastructure or operational capacity Uber would need for Uber One at global scale, showing clear assumptions, logical decomposition, and practical checks rather than a single unsupported number.