1p3a Experience · May 2026

reddit software engineer onsite interview experience with ml case study

SWE Onsite newgrad
2 upvotes 3 replies

Interview Experience

First Round, ML Case Study 参考 但是有 missing data, 并且 class imbalance, 20% positive label 最后还有时间做了一点 feature engineering, normalize time spend per person 最后最出来的 F1 score > 0.97 Final Rounds 第一轮 ML Fundamental, 讲怎么build cvr model 第二轮 ML SD, 非常偏重 inference 和 feature serving 第三轮 Coding,Billing Status 第四轮 HM 常规BQ

Full Details

🔒

Unlock all Reddit questions

Full insider details, leaked discussions, and candidate experiences.

Get full access — from $50/mo

About Reddit Interview Reports

This question was reported by a candidate who interviewed at Reddit. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.

Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Reddit are the higher-signal extractions to take from this report.

For broader preparation context, the Reddit interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.

How To Practice This Type of Question

Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.

Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Reddit reports consistently are the ones worth investing in; one-off niche problems are not.

During Your Reddit Round

Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.

The single most predictive failure mode in Reddit reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.