Reddit SWE Interview: Onsite Coding Guide

Estimated read time: 8-10 minutes

Summary: Reddit SWE onsite or final-loop coding rounds deepen the signal from the first screen. The evidence supports additional coding and technical interviews, with meaningful variance by backend, infrastructure, mobile, ML, ads, feed/ranking, moderation, and safety roles.

TL;DR + FAQ

At-a-glance takeaways

• Final-loop coding is candidate-report backed, but exact round count is unclear.
• Expect stronger scrutiny across multiple engineers than in a single screen.
• Backend, mobile, ML, ads, safety, infra, and ranking paths may diverge.
• Senior candidates may be evaluated for systems thinking and ownership even during technical rounds.
• Role-specific fluency matters alongside working code.

Quick FAQ

Is onsite coding different from the screen?
It can be deeper, more consistent across interviewers, and more role-specific.

Will all final interviews be coding?
No. Final loops may include system design and behavioral or manager rounds too.

Are exact tasks known?
No. Public evidence is mostly themes.

Should I prepare domain follow-ups?
Yes, especially for mobile, ML, ads, safety, ranking, infra, and backend roles.

---

1) How final coding rounds work

Final-loop coding rounds give Reddit multiple technical data points. The source supports 45-60 minute interviews with engineers, but does not prove a universal round count.

Expect less tolerance for shallow reasoning than in an initial screen. You should clarify constraints, write maintainable code, test tricky cases, and show that you can connect implementation choices to Reddit-scale product or infrastructure realities.

---

2) Final-loop coding tasks you may face

These tasks reflect source-supported themes and role context. They are phrased to include realistic final-loop follow-ups.

• Build a service-side function that assembles a feed page from candidate posts, blocked communities, duplicate content, and ranking scores.
• Given comments, votes, and moderation states, return what a viewer should see. Now support edits and deleted comments.
• Implement a notification batching function. Avoid duplicate notifications and preserve priority for urgent events.
• Given a stream of safety events, count rule violations per user within a rolling window and expire old events correctly.
• For an ads or ranking path, merge candidate lists with scoring, budget, or diversity constraints.
• For an infrastructure path, implement retry or backoff logic for a failing downstream service.
• For a mobile path, reconcile local cached state with a newer paginated server response.
• After the implementation works, explain what would break first at larger scale and what you would monitor.

---

3) What interviewers may probe

Final rounds often probe whether your code still works when the data becomes messy. Reddit-style systems can involve deleted content, blocked users, duplicate votes, ranking changes, moderation actions, stale mobile cache, or large event streams.

For senior candidates, expect questions about tradeoffs, monitoring, ownership, and when an implementation should become a service design discussion.

---

4) Common failure modes

Assuming all Reddit SWE loops are backend-only. Team variance is high.

Writing brittle code. Final-loop code should handle bad or changing input.

Ignoring domain constraints. Moderation, ranking, ads, mobile, and infrastructure all change what correctness means.

Not communicating tradeoffs. Multiple interviewers need to see how you reason.

No testing story. Explain what you would test before shipping.

---

5) How to prepare

• Practice coding tasks around feeds, comments, votes, moderation states, notifications, caching, and event streams.
• Prepare role-specific variants for mobile, ML, ads, safety, infra, or ranking.
• For senior roles, connect implementation choices to reliability and ownership.
• Use tests that cover deleted content, duplicates, out-of-order events, and scale.
• Ask the recruiter what final technical rounds are expected for your team.

---