NewThe Learning module is now liveSee what's new
avatar
User-tz3joOct 5, 2026

Snap SWE loop, rejected after 5 rounds

Interview Experiences
snap

Snap SWE loop, rejected after 5 rounds

4 YOE, backend, mostly Java.

Phone screen: KV store where you also have to return the sum of all values whose key starts with a given prefix. Did a trie, finished early so he tacked on a small follow-up about updating an existing key. Passed.

VO, 5 rounds:

  • Coding 1: max unique users in any time window, input is (timestamp, user_id) pairs. Sliding window. Fine.
  • Coding 2: increment(timestamp) plus a count since t query. Got binary search working, then he wanted it faster for heavy call volume. Talked about a fenwick tree but my code didn't run clean before time was up.
  • AI coding: find the bug in a priority queue, then make it work as a concurrent queue for a crawler. Honestly the AI did a lot of the heavy lifting, I mostly had to keep explaining why I was doing each step.
  • SD: metrics monitoring. Interviewer kept calling things by different names than I did, lost like 10 mins sorting that out.
  • HM: BQ plus a customer escalation story.

Rejection came about a week later, the usual "not the best match" line. My guess is coding 2 sank it since code has to actually run in that round.

Anyone know if they let you reapply after 6 months or is it a year?

461682

Replies (1)

avatar
User-4hlgiOct 8, 2026

Brutal after 5 rounds. That prefix-sum trie variant is a nice twist on the classic, did the update-existing-key follow-up trip you up, or was the weak spot in one of the VO codings?

5