How do I approach Machine Learning interview questions?

Machine Learning questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master machine learning interviews.

What difficulty level is this interview question?

This is a hard difficulty Machine Learning question, commonly asked during Technical Screen rounds at Uber.

What role is this question designed for?

This question is commonly asked for Data Scientist candidates at Uber during technical interviews.

Optimize Surge Notifications for Rideshare Drivers

Quick Overview

Optimize Surge Notifications for Rideshare Drivers evaluates core ML concepts, assumptions, math intuition, training/evaluation trade-offs, and practical failure modes in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

Optimize Surge Notifications for Rideshare Drivers

Scenario

A rideshare marketplace experiences airport demand spikes. When demand exceeds supply, the system can send surge-pricing push notifications to nearby drivers to entice them to reposition toward the airport.

Task

List the business pros and cons of sending surge-pricing push notifications to nearby drivers.
Design a ranking system that decides how many drivers to notify and which drivers to target. State the objective, constraints, and the core features/signals your system would use.
Explain why a simple radius-based approach is inadequate, and propose data-driven improvements.
Propose a proxy for driver ETA to the airport (if full routing is unavailable), define the metrics you would compute to evaluate the system, and justify them.
Name additional real-time and historical metrics that should influence which drivers receive the push.
If neighborhood supply–demand imbalance is a feature, describe how to detect and quantify such imbalance.

Assume push notification latency needs to be low (sub-seconds to a few seconds) and consider feature engineering, real-time signals (supply, demand, distance), fairness, and offline evaluation.

Constraints & Assumptions

Preserve the scope, facts, inputs, and requested outputs from the prompt above.
If the prompt leaves a detail unspecified, state a reasonable assumption before relying on it.
Keep the answer interview-ready: concise enough to present, but concrete enough to implement or evaluate.

Clarifying Questions to Ask

Clarify the task, data shape, labels, constraints, and evaluation metric.
State assumptions behind the math or modeling technique you choose.
Connect theory to practical training, debugging, and deployment implications.

What a Strong Answer Covers

Correct definitions and formulas where the prompt requires them.
A practical explanation of how the method behaves on real data.
Trade-offs, failure modes, diagnostics, and mitigation strategies.
Evaluation choices that match the product or modeling objective.

Follow-up Questions

How would noisy labels, class imbalance, or distribution shift affect the answer?
What would you monitor after deployment?
Which baseline would you compare against first?

Quick Overview

Task

List the business pros and cons of sending surge-pricing push notifications to nearby drivers.

Design a ranking system that decides how many drivers to notify and which drivers to target. State the objective, constraints, and the core features/signals your system would use.

Explain why a simple radius-based approach is inadequate, and propose data-driven improvements.

Propose a proxy for driver ETA to the airport (if full routing is unavailable), define the metrics you would compute to evaluate the system, and justify them.

Name additional real-time and historical metrics that should influence which drivers receive the push.

If neighborhood supply–demand imbalance is a feature, describe how to detect and quantify such imbalance.

Assume push notification latency needs to be low (sub-seconds to a few seconds) and consider feature engineering, real-time signals (supply, demand, distance), fairness, and offline evaluation.

Constraints & Assumptions

Preserve the scope, facts, inputs, and requested outputs from the prompt above.

If the prompt leaves a detail unspecified, state a reasonable assumption before relying on it.

Keep the answer interview-ready: concise enough to present, but concrete enough to implement or evaluate.

Clarifying Questions to Ask

Clarify the task, data shape, labels, constraints, and evaluation metric.

State assumptions behind the math or modeling technique you choose.

Connect theory to practical training, debugging, and deployment implications.

What a Strong Answer Covers

Correct definitions and formulas where the prompt requires them.

A practical explanation of how the method behaves on real data.

Trade-offs, failure modes, diagnostics, and mitigation strategies.

Evaluation choices that match the product or modeling objective.

Follow-up Questions

How would noisy labels, class imbalance, or distribution shift affect the answer?

What would you monitor after deployment?

Which baseline would you compare against first?

Optimize Surge Notifications for Rideshare Drivers

Quick Overview

Optimize Surge Notifications for Rideshare Drivers

Optimize Surge Notifications for Rideshare Drivers

Scenario

Task

Constraints & Assumptions

Clarifying Questions to Ask

What a Strong Answer Covers

Follow-up Questions

Write your answer

Optimize Surge Notifications for Rideshare Drivers

Quick Overview

Optimize Surge Notifications for Rideshare Drivers

Optimize Surge Notifications for Rideshare Drivers

Scenario

Task

Constraints & Assumptions

Clarifying Questions to Ask

What a Strong Answer Covers

Follow-up Questions

Write your answer