Snap · Primly Community

Snap onsite / final round, how it really goes

backend_bekah · 5 replies

Did my Snap virtual onsite for a staff-level SWE role earlier this year. Five rounds over one day. Posting this because the information I found when prepping was scattered and mostly pre-2024.

Round 1: Coding (45 min). Two LeetCode-medium-ish problems. First one was array/hash-map, done in about 20 min. Second was trickier, graph-adjacent. Got through a working solution but it wasn't optimal. Interviewer was fine with that, wanted to see clean thinking.

Round 2: System design (60 min). I described this in a separate thread. High-level: distributed systems problem, scoped to a specific feature, not the whole product. Two interviewers. Lots of back-and-forth.

Round 3: Behavioral (45 min). Four or five STAR-format questions. Focused heavily on cross-functional influence, conflict resolution, and how I approach ambiguous projects. They used the phrase "in your best guess" a lot which I took to mean: we want your judgment, not a corporate answer.

Round 4: Coding (45 min). Another medium problem. More string manipulation. By this point I was a little fatigued so I made myself slow down and talk through the approach before coding. Helped.

Round 5: Hiring manager (45 min). Mostly conversation. Some light behavioral stuff but also genuine discussion about what I'd work on, how I think about technical leadership at scale, and what I want in the next role. The HM asked good questions, felt like a real conversation not an eval.

Lunch break was built in but only 30 min. Eat a real meal before you start.

Overall vibe: organized, not grueling. Less adversarial than Meta's onsite, more structured than Airbnb's. They told me the timeline to feedback was 5-7 business days. Mine came in 6.

5 replies

sre_sol

five rounds in one day sounds rough but snap's virtuals are actually pretty reasonable. better than when they were flying everyone to santa monica and you had to figure out parking in culver city.

ops_omar

the 'eat a real meal' advice is underrated. by round 4 of any all-day loop your blood sugar is doing things to your algorithm recall.

director_dee

the HM round at the end is the one candidates underinvest in. by that point you've been in eval mode for 4 hours and you relax too much. that round is still scored. have two or three smart questions ready about the team's roadmap.

alex_design

did they give you a practice problem or coding environment to test before the onsite? or did you just show up and figure it out?

sec_sasha

recruiter sent a link to the CoderPad environment a couple days before so i could test audio/video and try a scratch problem. definitely use it, don't skip that.