From vague prompt to ML system, in 45 minutes
Usually one conversation: turn a product prompt into an objective, labels, features, a model, metrics and a serving plan, before the time runs out. The Diagram tab draws the pipeline components as the question is asked, so you can spend the minutes on the decisions.
At a glance
Usually one 45-minute conversation. You turn a vague product prompt into an end-to-end ML system: objective, data and labels, features, model, offline and online evaluation, serving and monitoring. Meta (third-party copy) (opens in a new tab); DarkInterview (opens in a new tab); Aced, 2026 (opens in a new tab); Personal blog, 2024 (opens in a new tab)
- Length
- 45 minutes
- Meta (third-party copy) (opens in a new tab); Hello Interview (opens in a new tab); DarkInterview (opens in a new tab)
- ML design rounds in a Meta loop
- One at E4, one or two at E5, two at E6
- Aced, 2026 (opens in a new tab); Personal blog, 2024 (opens in a new tab)
- Most common prompts
- Ranking, recommendation and harmful content
- Meta (third-party copy) (opens in a new tab); Aced, 2026 (opens in a new tab); Reddit, 2025 (opens in a new tab)
- What Meta grades
- Five signals, from problem navigation to deployment
- Meta (third-party copy) (opens in a new tab)
- Most reported failure
- Running out of time before evaluation
- DarkInterview (opens in a new tab); Reddit, 2024 (opens in a new tab); Blind (opens in a new tab)
- Also in some ML loops
- A classic backend design round
- Aced, 2026 (opens in a new tab); Blind, 2024 (opens in a new tab); cswork.org, 2025 (opens in a new tab)
The 45 minutes, phase by phase
Three prep frameworks split the round in the same order and in similar proportions. A fourth, aman.ai, uses the same order without giving times.
Hello Interview (opens in a new tab); DataInterview (opens in a new tab); DarkInterview (opens in a new tab); aman.ai (opens in a new tab)
- Minutes budgeted
- Top of a range
- The rest of the round
- Each bar runs from 0 to 10 minutes.
Frame the problem
Ask about users, scale, latency and which labels already exist. Settle the business objective, then turn it into an ML task such as ranking or classification. Hello Interview (opens in a new tab); DarkInterview (opens in a new tab); Personal blog, 2024 (opens in a new tab)
- Hello Interview
- 5–7 minutes
- DataInterview
- 5 + 5 minutes
- DarkInterview
- 5–7 minutes
DataInterview splits this into requirements, then the ML problem definition. DataInterview (opens in a new tab)
Sketch the pipeline
Data to prediction to action, including the feedback loop that sends outcomes back into training. Hello Interview (opens in a new tab); DarkInterview (opens in a new tab)
- Hello Interview
- 2–3 minutes
- DataInterview
- No separate step
- DarkInterview
- 3–5 minutes
Data and features
Where the labels come from (explicit or implicit feedback, weak labels), problems like class imbalance and cold start, and a short, prioritised feature list. Meta (third-party copy) (opens in a new tab); DarkInterview (opens in a new tab); Personal blog, 2024 (opens in a new tab)
- Hello Interview
- 10 minutes
- DataInterview
- 8 minutes
- DarkInterview
- About 10 minutes
Choose the model
A baseline first, then two or three options compared, one chosen, and its loss and training explained. Hello Interview (opens in a new tab); DarkInterview (opens in a new tab)
- Hello Interview
- 10 minutes
- DataInterview
- 8 minutes
- DarkInterview
- About 10 minutes
Evaluate and serve
Often cut short for time
Offline metrics such as nDCG or precision@K, an online A/B test tied to the business metric, batch or real-time serving, latency and cost. DarkInterview (opens in a new tab); Personal blog, 2024 (opens in a new tab)
- Hello Interview
- 7 minutes
- DataInterview
- 10 minutes
- DarkInterview
- About 8 minutes
DataInterview says to give serving at least 8 minutes. DataInterview (opens in a new tab)
Monitor and go deep
Often cut short for time
Drift, retraining, feedback loops and cold start, or wherever the interviewer wants more depth. Hello Interview (opens in a new tab); DarkInterview (opens in a new tab)
- Hello Interview
- The rest of the round
- DataInterview
- 5 minutes
- DarkInterview
- The rest of the round
Where the time runs out
Candidates most often report dropping metrics, deployment or monitoring because they ran out of time, and DarkInterview calls it the most common failure. DarkInterview (opens in a new tab); Reddit, 2024 (opens in a new tab); Blind (opens in a new tab)
For Meta, one guide says to save the most time for model choice and evaluation, and warns that interviewers may cut a section short. Another treats deployment as “if time permits” and suggests practising the whole round in 35–40 minutes. Aced, 2026 (opens in a new tab); Personal blog, 2024 (opens in a new tab)
If the round runs longer
In 60-minute rounds, DarkInterview gives the extra time to the model and to deep dives. DarkInterview (opens in a new tab)
Single reports describe a one-hour Flipkart round with “why this?” after every step, and an Uber round on driver ETAs that ran about 90 minutes and mixed in ML trivia. LeetCode Discuss, 2025 (opens in a new tab); cswork.org, 2025 (opens in a new tab)
Five signals Meta grades, and how each is lost
A third-party copy of Meta’s MLE prep guide names five signals. All five centre on ML decisions rather than databases or APIs. Meta (third-party copy) (opens in a new tab); DarkInterview (opens in a new tab)
| Signal | What Meta’s guide asks for | Where candidates slip |
|---|---|---|
| Problem Navigation | Meta’s guide asks for: Organise the problem space, and tie the business context to your ML decisions. | Where candidates slipSkipping clarification and going straight into the design. Hello Interview (opens in a new tab); DarkInterview (opens in a new tab) |
| Training Data | Meta’s guide asks for: How you’d collect training data, and its constraints and risks. | Where candidates slipNone singled out in our sources. Expect to cover where the labels come from, class imbalance and cold start. Meta (third-party copy) (opens in a new tab); DarkInterview (opens in a new tab); Personal blog, 2024 (opens in a new tab) |
| Feature Engineering | Meta’s guide asks for: The relevant features, and which of them matter most. | Where candidates slipOne framework warns against long feature lists with no priorities. DarkInterview (opens in a new tab) |
| Modeling | Meta’s guide asks for: Justify the model, explain how it’s trained, and anticipate its risks. | Where candidates slipNaming an architecture in the first minutes, or reaching for the most complex model. Candidates describe “why this, why not that” at every step. Hello Interview (opens in a new tab); DarkInterview (opens in a new tab); Reddit, 2026 (opens in a new tab); LeetCode Discuss, 2025 (opens in a new tab) |
| Evaluation & Deployment | Meta’s guide asks for: Consistent evaluation and deployment, with metrics you can justify. | Where candidates slipChoosing metrics that aren’t tied to the business objective. Meta (third-party copy) (opens in a new tab); DarkInterview (opens in a new tab) |
At E6, two rounds and more depth
E6 reports describe two ML design rounds: one end-to-end design, and one deep dive into a domain or your past work. One guide says the level is decided mainly by the design and behavioural rounds. Personal blog, 2024 (opens in a new tab); Reddit, 2025 (opens in a new tab); LeetCode Discuss, 2024 (opens in a new tab)
One E6 candidate was told they stayed too high-level on model training. Their feedback named clear framing, trade-offs, iteration and experimentation, and operational constraints at scale. Reddit, 2025 (opens in a new tab)
What else graders want
Clarify the goal, justify trade-offs, start simple and iterate, and think about how the system fails after launch. Reddit, 2026 (opens in a new tab)
Cover the whole pipeline before going deep, because structure and reasoning count for more than the exact solution. DarkInterview (opens in a new tab); LeetCode Discuss, 2024 (opens in a new tab)
Theory still comes up
Meta’s guide tells candidates to brush up on overfitting and regularisation. One Uber candidate’s design round asked about XGBoost tree depth and dropout, and one LinkedIn loop ran a separate AI-fundamentals round. Meta (third-party copy) (opens in a new tab); LeetCode Discuss, 2025 (opens in a new tab); cswork.org, 2025 (opens in a new tab)
What you’ll be asked to design
Four families of prompt, from the reports and guides behind this page. Most public detail comes from Meta, so the other companies’ rows are often one candidate’s experience.
Ranking and recommendation
The biggest group. Meta’s own examples and most candidate reports sit here. Meta (third-party copy) (opens in a new tab); Aced, 2026 (opens in a new tab); Reddit, 2025 (opens in a new tab)
- Meta
A personalised news ranking system, or a product recommendation system (both examples in Meta’s guide)Meta (third-party copy) (opens in a new tab)
- Meta
Instagram Reels ranking, or Facebook comments rankingAced, 2026 (opens in a new tab)
- Meta
“People You May Follow” or friend recommendationsMeta (third-party copy) (opens in a new tab); Personal blog, 2024 (opens in a new tab)
- Meta
Rank places for someone who has just arrived in a new cityAced, 2026 (opens in a new tab); LeetCode Discuss, 2024 (opens in a new tab)
- LinkedIn
A cold-start recommender, or skill and course recommendations with metrics monitoringLeetCode Discuss, 2025 (opens in a new tab); cswork.org, 2025 (opens in a new tab)
- Uber
Recommendations for new Uber Eats users, in one candidate’s reportReddit, 2025 (opens in a new tab)
Harmful content and integrity
The other common Meta family. One commenter says Meta asks either a recommender or a harmful-content problem, and not always about a Meta product. Reddit, 2025 (opens in a new tab)
- Meta
Detect harmful contentAced, 2026 (opens in a new tab); Reddit, 2025 (opens in a new tab)
- Meta
Detect guns, or ads for weaponsReddit, 2025 (opens in a new tab); LeetCode Discuss, 2024 (opens in a new tab)
- Google
Detect copyright violations on YouTubeTaro, 2025 (opens in a new tab)
Prediction and language
Outside the feed: estimates, risk decisions and text, mostly from single reports. LeetCode Discuss, 2025 (opens in a new tab); interviewexperiences.in, 2026 (opens in a new tab); cswork.org, 2025 (opens in a new tab)
- Uber
Predict and update driver ETAs in real time, including 10 minutes on GPS error, in one candidate’s reportcswork.org, 2025 (opens in a new tab)
- Flipkart
Approve EMI credit for users with no history, for a Data Scientist 2 roleLeetCode Discuss, 2025 (opens in a new tab)
- Google
A Google Reviews-like system with an NLP pipeline, weighing BERT and LLMs against smaller modelsinterviewexperiences.in, 2026 (opens in a new tab)
Evaluation and LLM systems
A newer group, where designing the evaluation is the question. Aced, 2026 (opens in a new tab); Reddit, 2026 (opens in a new tab)
- Meta
An evaluation framework for ads ranking (an example in Meta’s guide)Meta (third-party copy) (opens in a new tab)
- Meta
LLM systems, which a 2026 guide says some Meta design rounds now focus onAced, 2026 (opens in a new tab)
- Research lab
One 2026 thread on a research-lab round advises spending most of the time on the evaluation pipelineReddit, 2026 (opens in a new tab)
How it differs from backend system design
A 2026 commenter called it “still system design, just with an ML spine”: the same structure every time, with the depth in the ML decisions. Reddit, 2026 (opens in a new tab)
Backend design round only
- Solution design
- Technical excellence
- Technical communication
Graded in both
- Problem navigation
ML design round only
- Training data
- Feature engineering
- Modeling
- Evaluation and deployment
- The infrastructure is assumed
- One framework says to stay out of database choices and API schemas in applied-ML rounds, because the infrastructure is taken as given. DarkInterview (opens in a new tab)
- More to cover on the ML side
- Training versus inference architecture, data quality and validation, model metrics and A/B test setup. A candidate with no backend design experience called the round “pretty different and much more focused on ML”. Reddit, 2025 (opens in a new tab)
- Less standard between companies
- Frameworks note that ML design varies more from company to company than classic system design does. DarkInterview (opens in a new tab)
Some ML loops add a classic design round too
- One LinkedIn MLE loop included a key-value store design. cswork.org, 2025 (opens in a new tab)
- Recruiters told a Meta and Google ML-infrastructure candidate to expect both ML design and infrastructure design. Blind, 2024 (opens in a new tab)
- A 2026 guide says specialised Meta loops, such as computer vision, can pair an AI design round with a full system design round. Aced, 2026 (opens in a new tab)
Formats reported at companies
Meta is where most public detail comes from. Elsewhere, treat each row as one or two candidates’ experience.
| Company | Format reported | Source |
|---|---|---|
| MetaMLE, E4–E6, 2024–26 | 45-minute ML design rounds, mostly ranking, recommendation or harmful content. One guide says one round at E4 and E5 and two at E6; another says E6 and some E5 loops get two. One 2024 E6 candidate says the hiring committee rejected them over less-than-perfect coding scores and one ML round. Meta’s hiring FAQ says outside AI tools aren’t allowed; only the tools inside its interview environment may be used. | Meta (third-party copy) (opens in a new tab); Aced, 2026 (opens in a new tab); Personal blog, 2024 (opens in a new tab); LeetCode Discuss, 2024 (opens in a new tab); Meta Careers (opens in a new tab) |
| GoogleMLE, L4–L5, 2025–26 | One ML design round in a loop of four or five, alongside coding, ML fundamentals or Googleyness. Candidates report YouTube copyright detection and a Google Reviews-like NLP system. Google’s virtual-interview guide says using AI during an interview means disqualification. | Taro, 2025 (opens in a new tab); interviewexperiences.in, 2026 (opens in a new tab); Google (opens in a new tab) |
| LinkedInSWE-ML and MLE, 2025 | One loop had an AI system design round on a cold-start recommender, plus a recommender design in the hiring manager round. Another had two design rounds: recommendation with monitoring, and a key-value store. | LeetCode Discuss, 2025 (opens in a new tab); cswork.org, 2025 (opens in a new tab) |
| UberMLE and SDE-ML2, 2025 | Single reports. One candidate’s round on real-time driver ETAs ran about 90 minutes and mixed in ML trivia. Another candidate was asked for new-user recommendations on Uber Eats. | cswork.org, 2025 (opens in a new tab); Reddit, 2025 (opens in a new tab) |
| PinterestMLE, 2024 | One candidate’s report: two ML design rounds, both end-to-end pipelines, plus two coding rounds. | Taro, 2024 (opens in a new tab) |
| FlipkartData Scientist 2, 2025 | One candidate’s one-hour “Depth in Data Science” round was framed as ML system design: approving EMI credit for a new feature with no user history, with “why this?” at every step. | LeetCode Discuss, 2025 (opens in a new tab) |
| AmazonApplied Scientist | Amazon lists four 55-minute loop interviews: technical topics, problem solving and coding, depth and breadth, and a tech talk. One 2025 candidate says the “science application” round is a role-specific case study, formally not ML system design, and that over half their loop was Leadership Principles. Amazon’s remote-interview page says interviews run on Zoom or Amazon Chime; Assisted Voice works on Zoom, not Chime. Business Insider reported internal guidelines telling candidates not to use GenAI tools during interviews unless explicitly permitted. | Amazon Jobs (opens in a new tab); Reddit, 2025 (opens in a new tab); Amazon Jobs (opens in a new tab); Business Insider, 2025 (opens in a new tab) |
Usually 45 minutes. That’s the length in a third-party copy of Meta’s MLE prep guide, and the Hello Interview and DarkInterview frameworks budget for it too. Single reports describe a one-hour round at Flipkart and an Uber round that ran about 90 minutes.
Keep preparing
- System design roundsThe backend round some ML loops add.
- Staff engineer interviewsTwo design rounds, and how the level is set.
- ML engineer interview questionsThe fundamentals asked alongside design.
- Meta interviewsCompany-specific preparation.
- Machine learning engineer questionsCommon questions with sample answers.
- Applied scientist questionsCommon questions with sample answers.
Sources
Last reviewed . Candidate reports are paraphrased, and formats vary by team, location and year.
- Software Engineer, Machine Learning: full-loop interview prep guide (PDF, third-party copy)Meta (third-party copy) (opens in a new tab)
- Applied Scientist interview prepAmazon Jobs (opens in a new tab)
- ML system design delivery frameworkHello Interview (opens in a new tab)
- ML system design playbook frameworkDataInterview (opens in a new tab)
- The ML system design interview frameworkDarkInterview (opens in a new tab)
- ML system design frameworkaman.ai (opens in a new tab)
- Meta machine learning engineer interview guideAced, 2026 (opens in a new tab)
- Meta MLE interview preparation guidePersonal blog, 2024 (opens in a new tab)
- Has anyone recently done the Meta ML system design interview? (r/leetcode)Reddit, 2025 (opens in a new tab)
- Meta E6 ML engineer interview feedback (r/leetcode)Reddit, 2025 (opens in a new tab)
- MLE E5 interview experience at Meta (r/leetcode)Reddit, 2024 (opens in a new tab)
- ML system design interview prep strategies (r/leetcode)Reddit, 2025 (opens in a new tab)
- Tips for an ML system design round? (r/cscareerquestions)Reddit, 2026 (opens in a new tab)
- Chances of passing a Meta E5 loopBlind (opens in a new tab)
- Meta vs Google E5 offers (ML infrastructure)Blind, 2024 (opens in a new tab)
- Meta E6 offer (machine learning)LeetCode Discuss, 2024 (opens in a new tab)
- Meta phone screen and full loop (E6, machine learning)LeetCode Discuss, 2024 (opens in a new tab)
- LinkedIn Software Engineer, Machine Learning interview experienceLeetCode Discuss, 2025 (opens in a new tab)
- Flipkart Data Scientist 2 interviewLeetCode Discuss, 2025 (opens in a new tab)
- Google Machine Learning Engineer interview, Tel Aviv, April 2025Taro, 2025 (opens in a new tab)
- Google ML Engineer (L4/L5) interview experienceinterviewexperiences.in, 2026 (opens in a new tab)
- Uber MLE interview: ML design on driver ETAs, then a coding problemcswork.org, 2025 (opens in a new tab)
- LinkedIn MLE onsite with a key-value store design roundcswork.org, 2025 (opens in a new tab)
- Pinterest Machine Learning Engineer interview, San Francisco, November 2024Taro, 2024 (opens in a new tab)
- Amazon Applied Scientist interview experience, offer accepted (r/leetcode)Reddit, 2025 (opens in a new tab)
- Meta E6 (staff) interview guide: design-round competenciesHello Interview, 2026 (opens in a new tab)
- An Uber SDE-ML2 interview journey (r/leetcode)Reddit, 2025 (opens in a new tab)
- Guidelines for virtual interviews at Google (candidate guide)Google (opens in a new tab)
- Hiring process FAQMeta Careers (opens in a new tab)
- Remote interviewAmazon Jobs (opens in a new tab)
- Amazon’s guidelines on AI use in job interviews (press report)Business Insider, 2025 (opens in a new tab)
Spend the 45 minutes on the decisions
Your first 30 minutes are free. After that it’s $5 an hour, pay as you go, with no subscription.
Start free — 30 minutes, no card