Reddit · Primly Community

Reddit coding interview / online assessment, format and difficulty breakdown

staff_steph · 4 replies

doing this from a lunch break so keeping it tight.

Reddit's coding process as of early 2026, at least for the backend/SWE track:

OA first. it's a HackerRank-style timed assessment, 90 minutes, two problems. difficulty: one medium, one medium-hard. the medium was a string manipulation problem with some edge cases. the medium-hard was graph-adjacent, basically BFS/DFS over a 2D grid. nothing crazy if you've done 60+ leetcode problems in the past month, but you can't half-ass it.

then a live coding round in the loop. this is where it actually matters. 45 min, one problem, coderpad. your interviewer can see what you're typing in real time. they'll ask you to talk through your approach first, which i actually liked. you're not being judged purely on speed.

what they seem to care about: clarity of code, variable naming, handling edge cases before you're asked, and asking clarifying questions up front. one interviewer literally said 'i don't care if you use the optimal solution first, i want to see how you think.'

i got a tree problem in the live round. medium difficulty. the trick was handling the base case correctly, which i nearly botched. interviewer gave a small hint, i caught it, finished clean.

what i'd say to prep: do mediums until they feel boring. understand trees, graphs, and hashmaps cold. the OA is a filter, the live round is the real signal. and don't skip the 'talk through your approach' step, it genuinely helps them and helps you catch dumb mistakes.

4 replies

sec_sasha

thank you for this. i've been terrified of the OA because someone told me it was an hour with three hard problems. good to know it's more reasonable. did you get results pretty quickly after the OA?

pivot_pat

for the live coding round, did they ask you to optimize after you had a working solution, or were they satisfied with a clear, correct O(n^2) if the problem didn't need better?

quietquit_quincy

depends on the problem. for mine they asked 'can we do better' after i had a working solution. i had to explain why O(n log n) was achievable. they didn't require the implementation, just wanted to know i understood the space. so: have a rough sense of what optimal looks like even if you don't code it.

qa_quinn

is there a separate testing or QA track at Reddit or do they funnel everyone through the same SWE loop? asking as someone who is SDET and it's often unclear.