Snap Backend Engineer interview questions

5 Backend Engineers have shared notes from their Snap interviews, with the questions they were asked in each round. That is 2% of the 216 Snap interview notes on Screna AI.

5 Backend Engineer interview notes

Snap·Backend Engineer·Technical Phone Screen

Jul 2026
Phone screen for a backend role at Snapchat with two behavioral questions back to back. Pretty standard format but the pairing felt intentional, like they were stress-testing communication and composure at the same time.
  • Describe a time you had to explain a technical concept, decision, or trade-off to someone non-technical, like a PM, executive, or business partner. How did you adjust your message, confirm they understood, and use it to move a decision forward?
  • Tell me about a time something unexpected hit you mid-project or in production, like an incident, a sudden scope change, or a key teammate going missing. Walk through how you triaged, communicated, and got things back on track.

“The part that tripped me up was the 'drive a decision' bit.”

View Post

Snap·Backend Engineer·Technical Phone Screen

Jun 2026
Snapchat backend screen, one algorithmic problem the whole time. Pretty standard union-find territory but I fumbled the counting step at the end and had to backtrack.
  • Given n employees and a list of pairs indicating which employees belong to the same group (with transitivity), count the total number of unordered pairs of employees that come from different groups.

“I recognized the connected components angle pretty fast and went with union-find.”

View Post

Snap·Backend Engineer·Onsite - System Design / Architecture

Jun 2026
Snapchat backend design round, one big question about a file storage system with access control. Pretty deep dive, we spent most of the time on the data model and the authorization query logic. Felt okay but not great coming out of it.
  • Design a file storage system with access control, where users belong to groups, permissions can be assigned to users or groups at the file or folder level, and access inherits down through folder hierarchies.

“The data model part I felt decent about.”

View Post

Snap·Backend Engineer·Technical Phone Screen

May 2026
SQL-heavy technical screen for a backend role at Snapchat. The interviewer gave me a multi-table schema upfront and then fired off a few verbal requests one by one, expecting me to write queries on the spot and talk through the logic without actually running anything.
  • Given a schema with users, files, groups, and ACL tables from a file-access system, write a SQL query that joins two or more of these tables to answer a specific access-related question, and walk through your reasoning without executing it.
  • Write a GROUP BY query with aggregation across multiple tables from the same schema, and explain how you'd handle deduplication if a join produces duplicate rows.
  • For a given verbal data request, explain how your SQL query maps back to the underlying data model and why the join type you chose is correct for that specific access pattern.

“The part that tripped me up was deciding between INNER and LEFT JOIN before I fully understood what NULLs in the ACL table would mean for the result.”

View Post

Snap·Backend Engineer·Technical Phone Screen

Apr 2026
Snapchat backend interview with a graph problem that looks straightforward until you actually have to count the pairs correctly. Union Find was the expected approach and they weren't subtle about it.
  • Given a list of edges representing employee connections, group employees into connected components and return the total number of pairs you can form by picking one person from each of two different groups.

“The example they gave made it click pretty fast: edges like [0,1],[0,2],[3,4] give you groups of size 3 and 2, so 3x2=6 pairs.”

View Post