Snap·Software Engineer

Snap Software Engineer interview experience

Candidate report, summarized by Dataford

I ended up in a pretty typical Snap phone screen for an SWE role, and it moved fast from scheduling to actually sitting down for the hour.

The interview came as a timed technical segment plus the rest of the hour covered behavioral follow-ups and some general security-related questions, so it didn’t feel like a pure coding test.

What threw me off was that the coding part wasn’t gentle. It leaned hard enough that the question felt tougher than I expected, and I remember wrestling through it while trying to keep my explanations clear. Then the behavioral portion got quite intense, described as a tough behavioral question, and that combination made the whole call feel higher-pressure than I was used to.

I didn’t get past the

Create a free Dataford account to unlock the full round-by-round breakdown, the questions asked and the outcome.

Read the full report Read the full report

Preparing for this interview?

Snap Software Engineer interview guideThe full process, round by round, with the question bank Practice Software Engineer interview questionsReal questions from this role across companies All Snap interview guidesEvery role we cover at this company