Company interview guide
Reddit Machine Learning Interview Guide (2026)
A live model-building screen on a small dataset, then practical coding, ML fundamentals, ranking-system design and a hiring manager round.
Reddit's machine learning interview loop has 8 reported stages, from recruiter call to data science track: product and experiment case; typical length: 2-6 weeks.
Roles covered: ML Engineer and Data Scientist. The question bank holds 15 questions reported from Reddit interviews, 5 of them free to solve in your browser.
- Interview process length
- 2-6 weeks
- Stages
- 8
- Reports linked to bank questions
- 18
- Bank report dates
- Feb 2022–Sep 2026
- Questions in bank
- 15 (5 free)
- Last reviewed
- October 2026
How the Reddit interview loop works
A recruiter call, one technical screen of roughly 45-60 minutes (for ML engineers, building a model on a provided dataset), then a virtual onsite of about four one-hour rounds, often scheduled in a single block. Some 2026 candidates were moved from a specific team's opening into a general ML engineer pool before the onsite, so questions may cover ranking even if you applied to another area. Results tend to come within days, but several candidates report slow or missing follow-up, so keep your recruiter in the loop.
The Reddit interview process, stage by stage
01Recruiter call
Short call, about 30 min
A conversation about your background and the role, sometimes with a basic ML sanity question. For data science roles the first call is often with the hiring manager instead of, or right after, the recruiter.
What it tests
- How your experience fits the team or the general ML pool
- Motivation for Reddit and its products
- Logistics: level, location, timeline
How to prepare
- Ask exactly what the screen covers (modeling in a notebook or general coding) and whether searching for syntax is allowed.
- Ask whether you are interviewing for a specific team or a general pool; it changes which domains the onsite may probe.
A recruiter or HR call opens the process in 5 ML-role and 6 data-science reports; the first step is shared across tracks, so both are counted.
02Technical screen: build a model from a dataset
About 45-60 min, live in a notebook with scikit-learn; data often arrives as JSON you turn into a dataframe
The ML engineer screen in every report since 2024 that names its content: you get a small, clean tabular dataset (one recurring version predicts clicks from hours spent on post categories) and must build, compare and evaluate classifiers end to end, then answer follow-ups on model choice, metrics and features. Reports from 2020-2023 describe a general coding screen instead, including JSON data processing.
What it tests
- Loading and shaping data quickly (JSON to dataframe, encoding categoricals)
- Building a baseline, then comparing logistic regression, tree ensembles and boosting
- Choosing and justifying metrics for a binary click label
- Follow-ups: why this model, what you would do with more time, high-cardinality features and cold start
- Working steadily under tight time
How to prepare
- Rehearse a full sklearn pipeline (split, baseline, two or three models, metrics) until it takes under 30 minutes.
- Start with a dummy baseline and a simple model before tuning; candidates say time is very tight and cross-validation can be skipped.
- Even if searching for syntax is allowed, keep it rare; one candidate believes heavy searching counted against them.
- Prepare crisp answers on calibration, AUC vs log loss, and how embeddings handle new items.
Free reported questions for this stage
- Notebook Click Model: Baseline, Model Comparison and Follow-UpsClassical MLMediumSolve
15 ML-role reports describe one technical screen; 9 had building a model on a given dataset (8 since 2024), while four from 2020-2023 had general or data-processing coding.
03Onsite: coding
1-2 x about 60 min; practical problems, sometimes pair programming; one 2026 report says AI tools were not allowed
Problems are mostly practical rather than classic puzzle questions: process structured data, aggregate logs, filter a comment tree, or extend an object-oriented design. Some loops instead run two standard algorithm rounds of medium difficulty. One 2026 candidate failed after finishing only part of a multi-part problem, so pace matters.
What it tests
- Tree and graph traversal on product-like data such as comment threads
- Clean, object-oriented code that is easy to extend
- Careful data transformation and aggregation without bugs
- Standard data-structure problems (strings, linked lists, hash maps)
How to prepare
- Practise multi-part problems and aim to finish the first part fully before optimizing.
- Talk through the data model first, then code; interviewers value readable code and tests.
- Expect a problem framed around Reddit concepts such as posts, comments and communities.
8 ML-role onsite reports include one or two coding rounds; most call them practical rather than puzzle-style, and a 2026 report had two standard algorithm problems.
04Onsite: ML fundamentals
About 60 min open Q&A, sometimes with a small dataset or plot to interpret
A breadth round on classical ML and practical modeling. Recent reports describe framing a problem from raw x and y, reading a plot of two distributions, cold-start questions, and a deep dive into position bias in click-trained rankers asked of a candidate who had never worked on ranking.
What it tests
- Model trade-offs, for example logistic regression vs random forest
- Framing a modeling problem and picking baselines and metrics
- Reading distribution shift or class separation from a plot
- Ranking-specific issues: position bias, cold start, feedback loops
How to prepare
- Review ranking and recommendation basics even if your target team is elsewhere; pooled candidates were asked about them.
- Answer concept questions with a concrete example and a way to measure the effect.
- Keep any opening small talk short so the technical part gets the time.
Free reported questions for this stage
- Position Bias in a Click-Trained Feed RankerML System DesignHardSolve
6 ML-role reports from 2024-2026 list an ML knowledge or fundamentals round; two 2026 reports show it focused on ranking topics such as position bias and cold start.
05Onsite: ML system design
About 60 min discussion; occasionally a generic system design round as well
Design a feed or recommendation model end to end. Recent prompts include comment-likelihood prediction, comment ranking and a video recommender, with interviewers pushing hard on infrastructure: feature and model serving, logging, latency and experimentation.
What it tests
- Problem framing, labels and training data from engagement logs
- Feature pipelines and online feature serving
- Model serving, latency budgets and logging for training
- Offline and online evaluation, A/B rollout
How to prepare
- Prepare one ranking design in depth and be ready to spend most of the time on serving and logging rather than model choice.
- Explain how every feature is computed, stored and fetched at request time.
- Senior candidates should expect depth on infrastructure; one senior candidate was down-leveled after this loop.
Free reported questions for this stage
- Comment-Likelihood Model: Feature and Model ServingML System DesignHardSolve
7 ML-role onsite reports include an ML or system design round; all three 2026 reports with prompts were feed or recommendation designs probing serving and logging.
06Hiring manager & behavioral
About 60 min with the hiring manager; some loops add a separate behavioral or team-manager chat
A deep dive into your most recent project and how it maps to the team, plus standard questions on failures, successes and collaboration. Data science loops often have several behavioral conversations with product and engineering partners.
What it tests
- Depth and personal ownership in a recent project
- Learning from a failure and describing a success with impact
- Leadership, initiative and cross-functional work
How to prepare
- Prepare a project walkthrough with your decisions, metrics and what you would change.
- Have one failure story and one success story ready with measurable outcomes.
A hiring manager or behavioral round appears in 8 ML-role and 5 data-science reports; behavioral rounds are shared across tracks, so both are counted.
07Data science track: SQL and Python screen
About 60 min shared editor, sometimes with no way to run code
Data scientist candidates face a technical screen of SQL on a Reddit-like schema plus light Python data manipulation, sometimes with a short statistics or algorithm question. Two reports say the editor could not execute code.
What it tests
- SQL with CTEs, subqueries and window functions
- Python data manipulation without running the code
- Basic statistics, such as testing whether a difference is significant
- Occasional short algorithm questions
How to prepare
- Practise writing SQL that is correct on the first try, since you may not be able to run it.
- Know window functions and how to compute a significance test by hand.
Free reported questions for this stage
- K-th Smallest Element in a Sorted MatrixCoding & AlgorithmsMediumSolve
8 data-science reports from 2018-2026 describe a SQL and Python screen; SQL is the most consistent element and two mention a code editor that could not run code.
08Data science track: product and experiment case
Onsite case rounds, often with the hiring manager and product partners
Case studies on product metrics and experiments: interpret A/B test results and recommend a decision, define metrics for growth and retention, or improve onboarding. One 2026 ML engineer loop on an infrastructure team also included a product-sense round.
What it tests
- Reading A/B test results and making a recommendation
- Choosing success and guardrail metrics
- Experiment design and causal inference
- Product sense for growth, retention and onboarding
How to prepare
- Know Reddit's core engagement metrics (visits, votes, comments, subscriptions) and how they relate.
- Structure every case as goal, metric, hypothesis, experiment, decision.
Free reported questions for this stage
- Improving New-User Onboarding on a Community Discussion PlatformProduct & MetricsHardSolve
6 data-science reports describe case or A/B-test rounds and one 2026 ML engineer report had a product-sense round; formats vary by team.
Questions and themes reported most often
- Build and compare click or binary classifiers on a given dataset in a notebook (9 reports, technical screen: build a model from a dataset)
- Analyze A/B test results and recommend a decision (6 reports, data science track: product and experiment case)
- SQL with subqueries, CTEs and window functions on a product schema (6 reports, data science track: sql and python screen)
- Design a feed or recommendation model, with most time on serving and logging (4 reports, onsite: ml system design)
- Walk through your most recent project and how it fits the team (4 reports, hiring manager & behavioral)
- Why this model and not another: logistic regression vs tree ensembles (2 reports, technical screen: build a model from a dataset)
- Cold start for new items and high-cardinality features (2 reports, onsite: ml fundamentals)
- Practical data processing: JSON fields, log aggregation (2 reports, onsite: coding)
What Reddit asks about
- Notebook modeling (screen)24%
- General coding20%
- ML / ranking system design20%
- ML fundamentals14%
- SQL, stats & A/B tests (DS track)12%
- Behavioral & hiring manager10%
Reddit interview prep checklist
- Built and compared three classifiers on a JSON dataset in a notebook in under 45 minutes
- Can explain the trade-offs between logistic regression, random forests and boosting with metrics
- Can explain position bias and cold start in a feed ranker and how to correct for them
- Sketched a feed ranking design covering feature serving, model serving and logging
- Solved a multi-part tree-traversal problem on comment threads without AI help
- Prepared a recent-project deep dive plus one failure and one success story
- Data science track: wrote window-function SQL and read out an A/B test without running code
Tips
- Make the notebook modeling screen your first priority: it is the gate for ML engineers and the most consistently reported round.
- Drill a timed sklearn workflow on small tabular data, ending with a short spoken comparison of models and metrics.
- Study feed ranking deeply, including position bias, cold start and feature serving, even if you applied to a non-ranking team.
- For coding, practise practical multi-part problems on trees and structured data, written without AI help.
- In ML design, budget time for serving, logging and experimentation; interviewers push there.
- For data science roles, practise SQL you cannot run and A/B-test readouts with clear recommendations.
- Confirm with your recruiter whether you are in a team-specific or pooled process, and ask for the round list.
- Follow up politely but persistently after each stage; delayed responses are a common complaint.
See the rest of the Reddit loop
The later stages, the questions reported for them and how to prepare are in Pro.
Unlock with ProPractice the Reddit loop
Work the stages in order: every reported question for this company, grouped by round, with solutions in the app.
Reddit interview FAQ
How many interview rounds does Reddit have for ML roles?
Candidates report 8 stages: Recruiter call, Technical screen: build a model from a dataset, Onsite: coding, Onsite: ML fundamentals, Onsite: ML system design, Hiring manager & behavioral, Data science track: SQL and Python screen and Data science track: product and experiment case. A recruiter call, one technical screen of roughly 45-60 minutes (for ML engineers, building a model on a provided dataset), then a virtual onsite of about four one-hour rounds, often scheduled in a single block. Some 2026 candidates were moved from a specific team's opening into a general ML engineer pool before the onsite, so questions may cover ranking even if you applied to another area. Results tend to come within days, but several candidates report slow or missing follow-up, so keep your recruiter in the loop.
How long does the Reddit ML interview process take?
Reported timelines run 2-6 weeks.
What does Reddit ask in ML interviews?
By reported question mix: Notebook modeling (screen) 24%; General coding 20%; ML / ranking system design 20%; ML fundamentals 14%; SQL, stats & A/B tests (DS track) 12%; Behavioral & hiring manager 10%. The most repeated themes: Build and compare click or binary classifiers on a given dataset in a notebook; Analyze A/B test results and recommend a decision; SQL with subqueries, CTEs and window functions on a product schema.
How should I prepare for the Reddit ML interview?
Make the notebook modeling screen your first priority: it is the gate for ML engineers and the most consistently reported round. Drill a timed sklearn workflow on small tabular data, ending with a short spoken comparison of models and metrics. Study feed ranking deeply, including position bias, cold start and feature serving, even if you applied to a non-ranking team.
Are there free Reddit interview questions?
Yes. LeetML has 15 questions reported from Reddit interviews, and 5 of them are free to solve in the browser; they are listed by stage above.
Related interview guides
- PinterestRapid-fire ML fundamentals, edge-case-heavy coding and embedding-centric recommendation design.
- SnapClassic coding plus fast, broad ML fundamentals and recommendation-heavy ML design, with values questions in every round.
- MetaFast classic coding, an AI-assisted coding project and product ML design for recommendations and integrity.
- LinkedInProbability-flavoured coding, ML fundamentals and recommender design built around LinkedIn's own products.
- NextdoorTwo back-to-back technical screens: practical coding plus a hands-on tabular ML pipeline, then a final stage of varying length.
- QuoraTimed coding assessment up front, then recommender-style ML talk for engineers and heavy A/B testing and metrics for data scientists.