
Reddit software engineer candidates report a recruiter call, a coding screen, and a virtual onsite mixing algorithms, system design and behavioral rounds. Most shared experiences ended without an offer.
$195K
Avg. Base Comp
$290K
Avg. Total Comp
4-6 rounds
Typical Rounds
Not reported
Process Length
Candidates describing Reddit software engineer loops mostly report a recruiter conversation, a LeetCode-style coding screen, and then a virtual onsite. One candidate reported an offer, and several others reported no offer, so treat the coding bar as the main hurdle.
The coding rounds appear to reward process as much as the answer. One candidate reports being asked to show a brute-force solution first and then optimize it, with interviewers probing runtime and space complexity. Another described onsite data structures problems that built on multiple concepts. A third reported a 2D array problem about detecting rectangular regions of zeros surrounded by ones, extended to multiple rectangles and point checks. Another candidate reported a text-stream problem that barred a Set and relied on an unintuitive trick. Practice constraint-based problems while talking through your reasoning. One candidate also suggests brushing up on basic SQL queries and aggregations.
System design is reported as its own round in some loops. Examples include a financial management system with multiple constraints, a TCP server that reads and writes data, and a feature that pulls sorted data from another service. One candidate also described object-oriented design questions. Be ready to discuss practical trade-offs.
Behavioral conversations are reported with the hiring manager and again late in some loops. Topics include teamwork, communication, career trajectory, why Reddit, and disagreements with teammates. Prepare concrete stories. Reports vary by level and team, so expect some differences in format.
Synthesized from 8 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Reddit, Inc. process.
The Reddit interview process is structured and follows a predictable flow across four distinct rounds. It opens with a conversation focused on background, experience, and general fit questions — nothing surprising there. The second round is where the technical weight lands: you'll solve LeetCode-style coding problems, and from what I encountered, these ranged in difficulty. I was given a 2D array problem involving detecting rectangular regions of zeros surrounded by ones, then extending it to handle multiple rectangles and checking whether points fall inside them. The logic required careful coordinate tracking and pattern recognition, but it wasn't particularly exotic — the kind of thing you'd see in a medium-difficulty LeetCode problem.
The third round shifts tone entirely. This is with the hiring manager and is much more conversational. They ask topic-specific questions that tie directly to the job description and the team's actual work, so reading the role carefully beforehand really matters here. They're assessing both your technical depth on areas relevant to the team and your communication style. The fourth and final round is with the broader team. It's a chance to see how you'd work with actual colleagues and whether there's genuine fit. It feels less like an interrogation and more like a real conversation about how you'd approach problems together and integrate with their way of working.
One thing I didn't anticipate was the SQL component. Depending on the role, you might get a straightforward SQL question alongside the algorithmic work — nothing overly complex, but it's worth brushing up on basic queries and aggregations just in case. The whole process felt standard for a tech company of Reddit's size: organized, thorough, and designed to test both problem-solving ability and cultural alignment. I didn't advance past the technical stages, so I can't speak to later rounds with confidence, but the structure itself is solid and fair.
Prep tip from this candidate
Focus on 2D array and rectangular region detection problems — that was the core technical ask. Also, review your SQL fundamentals (basic queries, window functions) since the coding round may include SQL alongside DSA, and don't overlook the hiring manager round: they drill deep on domain-specific topics from the job description, so know the technical context of the role before you interview.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Reddit, Inc.
Write a query to get the top three users with the most upvotes on their 2020 comments
| Question | |
|---|---|
| Rain on Rainy Days | |
| Ad Comments | |
| Best Performing Advertisers | |
| Trending Sort | |
| Automated Labeling | |
| 2nd Highest Salary | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Employee Salaries | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Raining in Seattle | |
| Top 3 Users | |
| Comments Histogram | |
| Job Recommendation | |
| Like Tracker | |
| Random SQL Sample | |
| String Shift | |
| Rolling Bank Transactions | |
| Weighted Keys | |
| Flight Records | |
| Largest Salary by Department | |
| Size of Joins | |
| Liked Pages | |
| Last Transaction | |
| Find the First Non-Repeating Character in a String | |
| The Brackets Problem | |
| Delivery Estimate Model |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report applying online or through the careers page and hearing from a recruiter, typically for a call about background and the role. One candidate's first screen was a roughly 30-minute call with a hiring manager. Timing varied, and one candidate said scheduling was slower than ideal.
Candidates report a coding screen with LeetCode-style data structures and algorithm problems, in one case about an hour on backend fundamentals. One candidate called it the main filter. You may be asked to give a brute-force solution first and then optimize it and discuss complexity.
Some candidates report a hiring manager round covering experience and fit. It is typically conversational. One candidate for a more specialized role reports that questions tied directly to the job description, so read the posting carefully before this conversation.
Candidates describe an onsite of roughly three to four back-to-back interviews, with mostly algorithm or backend coding. Problems reportedly built on multiple concepts, and interviewers asked follow-ups on efficiency and trade-offs. One candidate was given a text-stream problem with a no-Set constraint and said hints interrupted their thinking time.
Several candidates report a dedicated system design round, such as a financial management system, a TCP server, or a feature returning sorted data from another service. A behavioral round may follow, covering teamwork, communication, project history, your career story and why you chose Reddit. Prepare specific examples of disagreements and how you resolved them.