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 Technical Screen rounds at Jane Street.

What role is this question designed for?

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

Predict future time-series values | Jane Street Interview Question

Quick Overview

This interview question evaluates ML product requirements, data/labeling, modeling, serving architecture, evaluation, monitoring, and trade-offs in a realistic interview setting. A strong answer for Predict future time-series values states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

Predict future time-series values

End-to-End Time-Series Forecasting (PyTorch)

Context

You are given one or more regularly sampled numeric time series and optional exogenous covariates (calendar features, prices of related assets, etc.). The goal is to forecast the next H time steps.

Assume:

Input time steps are ordered and may contain missing values/outliers.
Forecast horizon H and input context length L are to be chosen by you.
You should avoid data leakage and use time-aware validation.

Task

Design and implement an end-to-end forecasting solution:

Choose and justify a model architecture suitable for multi-step forecasting.
Implement the training loop in PyTorch, including dataset/windowing and evaluation.
Explain data preparation, hyperparameters, and design decisions.
Describe an evaluation strategy (splits, baselines, metrics, and backtesting).

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

Context

You are given one or more regularly sampled numeric time series and optional exogenous covariates (calendar features, prices of related assets, etc.). The goal is to forecast the next H time steps.

Assume:

Input time steps are ordered and may contain missing values/outliers.

Forecast horizon H and input context length L are to be chosen by you.

You should avoid data leakage and use time-aware validation.

Task

Design and implement an end-to-end forecasting solution:

Choose and justify a model architecture suitable for multi-step forecasting.

Implement the training loop in PyTorch, including dataset/windowing and evaluation.

Explain data preparation, hyperparameters, and design decisions.

Describe an evaluation strategy (splits, baselines, metrics, and backtesting).

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?

Predict future time-series values

Quick Overview

Predict future time-series values

Predict future time-series values

End-to-End Time-Series Forecasting (PyTorch)

Context

Task

Constraints & Assumptions

Clarifying Questions to Ask

What a Strong Answer Covers

Follow-up Questions

Submit Your Answer to Earn 20XP

Predict future time-series values

Quick Overview

Predict future time-series values

Predict future time-series values

End-to-End Time-Series Forecasting (PyTorch)

Context

Task

Constraints & Assumptions

Clarifying Questions to Ask

What a Strong Answer Covers

Follow-up Questions

Submit Your Answer to Earn 20XP