How do I approach ML System Design interview questions?

ML System Design questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master ml system design interviews.

What difficulty level is this interview question?

This is a hard difficulty ML System Design question, commonly asked during Onsite rounds at Amazon.

What role is this question designed for?

This question is commonly asked for Machine Learning Engineer candidates at Amazon during technical interviews.

Build an end-to-end ML pipeline | Amazon Interview Question

Quick Overview

Build an end-to-end ML pipeline evaluates ML product requirements, data/labeling, modeling, serving architecture, evaluation, monitoring, and trade-offs in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

Build an end-to-end ML pipeline

ML System Design: Shipment Delay Risk Scoring From a Single CSV

You are given a CSV of shipment events with the following columns:

order_id (string)
origin (string)
destination (string)
ship_date (string/datetime)
promised_date (string/datetime)
carrier (string)
weight (float)
item_count (int)
scan_events (JSON array encoded as string; each element typically has a timestamp and status)
delivered_date (string/datetime; may be null if undelivered)

Build a Python pipeline from scratch that:

Loads and validates data, handling missing values, outliers, and time zones.
Creates features (e.g., day-of-week, route, carrier stats via target encoding, and dwell times from scan_events).
Labels examples as delayed if delivered_date − promised_date > 48 hours. Justify and implement how you handle undelivered items and censoring.
Trains a baseline model (logistic regression or gradient-boosted trees) with cross-validation; reports ROC-AUC and PR-AUC; addresses class imbalance.
Calibrates probabilities and explains top features.
Outputs a CSV of top-K at-risk shipments with calibrated probabilities and reason codes.

Constraints:

Optimize for runtime < 5 minutes on 1M rows and memory < 4 GB on CPU.
Discuss strategies to speed up training/inference and ensure reproducibility.

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 users, core use cases, read/write patterns, scale, latency, availability, and data retention.
State explicit assumptions before making sizing or architecture decisions.
Prioritize the functional path first, then address reliability, security, observability, and rollout.

What a Strong Answer Covers

A scoped requirements summary with concrete non-goals and success metrics.
ML-specific data, model, evaluation, serving, and monitoring choices.
Reasoned trade-offs among simple and scalable designs, including bottlenecks and failure modes.
A validation, monitoring, migration, and launch plan appropriate for the risk level.

Follow-up Questions

What breaks first at 10x traffic or data volume?
How would you degrade gracefully during dependency failures?
What metrics and alerts would prove the design is healthy after launch?

Quick Overview

ML System Design: Shipment Delay Risk Scoring From a Single CSV

You are given a CSV of shipment events with the following columns:

order_id (string)

origin (string)

destination (string)

ship_date (string/datetime)

promised_date (string/datetime)

carrier (string)

weight (float)

item_count (int)

scan_events (JSON array encoded as string; each element typically has a timestamp and status)

delivered_date (string/datetime; may be null if undelivered)

Build a Python pipeline from scratch that:

Loads and validates data, handling missing values, outliers, and time zones.

Creates features (e.g., day-of-week, route, carrier stats via target encoding, and dwell times from scan_events).

Labels examples as delayed if delivered_date − promised_date > 48 hours. Justify and implement how you handle undelivered items and censoring.

Trains a baseline model (logistic regression or gradient-boosted trees) with cross-validation; reports ROC-AUC and PR-AUC; addresses class imbalance.

Calibrates probabilities and explains top features.

Outputs a CSV of top-K at-risk shipments with calibrated probabilities and reason codes.

Constraints:

Optimize for runtime < 5 minutes on 1M rows and memory < 4 GB on CPU.

Discuss strategies to speed up training/inference and ensure reproducibility.

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 users, core use cases, read/write patterns, scale, latency, availability, and data retention.

State explicit assumptions before making sizing or architecture decisions.

Prioritize the functional path first, then address reliability, security, observability, and rollout.

What a Strong Answer Covers

A scoped requirements summary with concrete non-goals and success metrics.

ML-specific data, model, evaluation, serving, and monitoring choices.

Reasoned trade-offs among simple and scalable designs, including bottlenecks and failure modes.

A validation, monitoring, migration, and launch plan appropriate for the risk level.

Follow-up Questions

What breaks first at 10x traffic or data volume?

How would you degrade gracefully during dependency failures?

What metrics and alerts would prove the design is healthy after launch?

Build an end-to-end ML pipeline

Quick Overview

Build an end-to-end ML pipeline

Build an end-to-end ML pipeline

ML System Design: Shipment Delay Risk Scoring From a Single CSV

Constraints & Assumptions

Clarifying Questions to Ask

What a Strong Answer Covers

Follow-up Questions

Submit Your Answer to Earn 20XP

Build an end-to-end ML pipeline

Quick Overview

Build an end-to-end ML pipeline

Build an end-to-end ML pipeline

ML System Design: Shipment Delay Risk Scoring From a Single CSV

Constraints & Assumptions

Clarifying Questions to Ask

What a Strong Answer Covers

Follow-up Questions

Submit Your Answer to Earn 20XP