
Reddit software engineer candidates often report a recruiter conversation, a coding screen, a hiring manager discussion and a multi-interview virtual onsite mixing algorithms, system design and behavioral questions, though the mix varies by role.
$236K
Avg. Base Comp
$297K
Avg. Total Comp
4-6 rounds
Typical Rounds
Not reported
Process Length
Across these candidate reports, coding is the common thread at Reddit. Most describe LeetCode-style data structures and algorithms problems. A couple say interviewers wanted a brute-force or working solution first, followed by discussion of runtime, space and optimization. One intern candidate described follow-ups such as how the code could be more efficient. A senior Android candidate described a 2D array problem about detecting rectangular regions of zeros surrounded by ones, then extending it to multiple rectangles and checking whether points fall inside them. That candidate also noted that a basic SQL question may come up depending on the role.
The mix beyond coding appears to depend on level and team. One software engineer who received an offer described separate backend programming and system design rounds, with a financial management system as the design task. Another reported designing a TCP server that reads and writes data. A full stack candidate recalled an object-oriented design question about fetching data from another service and returning sorted results. Another candidate faced a stream-of-messages problem that required finding entries five messages before and after a point without using a Set.
Hiring manager conversations appear in several reports. One candidate described that round as conversational and closely tied to the job description and the team's work, so reread the posting before that call. Behavioral questions covered teamwork, past projects, career story, why Reddit, and disagreements with teammates.
Most of these reports ended without an offer, so treat the difficulty as real. One candidate also described an interviewer who interrupted with hints, so practice thinking aloud while someone is talking. Timelines varied. One candidate said scheduling took longer than ideal, and another described the process stretching over a few months.
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 percentage of comments, by ad, that occurs in the feed versus mentions sections of the app.
| Question | |
|---|---|
| Comment Upvotes | |
| Rain on Rainy Days | |
| Best Performing Advertisers | |
| Trending Sort | |
| Automated Labeling | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Top 3 Users | |
| Last Transaction | |
| Random SQL Sample | |
| Monthly Customer Report | |
| Find Bigrams | |
| Raining in Seattle | |
| Longest Streak Users | |
| Size of Joins | |
| Duplicate Rows | |
| Largest Salary by Department | |
| Find the Missing Number | |
| Scrambled Tickets | |
| Comments Histogram | |
| Get Top N Frequent Words | |
| Like Tracker | |
| String Shift | |
| Rolling Bank Transactions | |
| Weighted Keys |
Synthesized from candidate reports. Individual experiences may vary.
Candidates typically report applying online and hearing from a recruiter, who discusses background, interest in the role and logistics. One candidate said the recruiter moved things along quickly, while another said scheduling took longer than ideal, so timing may vary.
Candidates report a coding screen with LeetCode-style problems. One described a technical phone screen of about an hour on data structures and algorithms. Interviewers may ask how a solution could be made more efficient, so be ready to discuss runtime and space.
Several candidates describe a hiring manager conversation covering experience and fit. One said the questions tied closely to the job description and the team's work, and described the round as more conversational than the coding rounds.
Candidates report several back-to-back interviews, with one describing four and another three. Reported content includes more data structures problems, backend coding, and system design tasks such as a financial management system or a TCP server. The exact mix likely varies by level and team.
Behavioral content appears in a dedicated or final round for several candidates. Reported topics include teamwork, communication, past projects, career trajectory, why Reddit and handling disagreements. Prepare specific examples rather than generic answers.