Intervu is in beta — feedback welcome at support@intervu.io

Snap Software Engineer Interview Questions

30 real practice questions for the mid-level Software Engineer role at Snap (Social / AR / Technology), spanning behavioral, technical, system design, leadership, and problem solving. Design, develop, and maintain software applications. The first 3 questions below include what Snap interviewers actually listen for, plus likely follow-ups.

Practice these questions with AI feedback
Questions
30
Categories
Behavioral (6), Technical (6), System Design (6), Leadership (6), Problem Solving (6)
Difficulty mix
10 easy · 10 medium · 10 hard
Avg. answer time
~4 min

Behavioral Questions (6)

  1. 1.Tell me about a time you built or shipped a feature involving real-time media — video, audio, or camera. What was the hardest part of making it work reliably?

    easy~3 min

    What interviewers look for

    • Candidate can clearly describe the real-time media pipeline they worked with — capture, encode, transmit, decode, or render — and shows genuine fluency in the domain, not just surface-level awareness.
    • Candidate identifies a concrete technical challenge (latency spikes, frame drops, synchronization issues, codec tradeoffs) and explains the specific fix or design decision they drove.
    • Candidate reflects on how the media constraint shaped product decisions — e.g., graceful degradation on poor networks — demonstrating camera-first product thinking aligned with Snap's identity.

    Likely follow-ups

    • What was the worst bug or regression you hit in that pipeline, and how did you diagnose it?
    • If you had to ship that same feature on a low-end Android device with half the RAM, what would you change?

    Company context

    Snap's camera is the homepage — literally the first thing users see when they open Snapchat. Engineers across many teams at Snap work with real-time media pipelines: camera capture, AR lens rendering, video messaging, Stories playback. Snap looks for mid-level engineers who have genuine hands-on exposure to at least one layer of a real-time media or graphics stack, not just theoretical knowledge. This question probes for the Camera-First Engineering principle and is an easy baseline check for whether the candidate has the foundational fluency Snap's culture expects.

  2. 2.Describe a time you shipped a mobile feature and then had to go back and fix it for battery or memory. What did you discover, and what did you change?

    easy~3 min

    What interviewers look for

    • Candidate describes a specific measurable regression — e.g., X% battery drain increase, Y MB memory spike, thermal throttling — caught via profiling tools like Android Profiler, Instruments, or Firebase Performance, not just user complaints.
    • Candidate explains the root cause (background wake locks, excessive allocations, unbounded caches, redundant network calls) and the targeted fix they shipped, demonstrating genuine mobile systems understanding.
    • Candidate reflects on the process change — adding a battery or memory budget to the definition of done, automating regression tests — showing they built a preventive system, not just patched one bug.

    Likely follow-ups

    • How did you reproduce the issue — was it consistent across devices, or did it only show up on specific hardware?
    • What would you do differently in the original design to have caught this before shipping?

    Company context

    Snap's Move Fast at Mobile Scale principle is non-negotiable — Snapchat ships to devices ranging from flagship iPhones to budget Android handsets across emerging markets. Battery and memory aren't nice-to-haves; they are product quality bars. Snap interviewers use this question to check whether mid-level candidates treat mobile constraints as first-class engineering concerns. Candidates who have only worked on web or server-side systems often lack the intuition for how camera-on, always-rendering apps like Snapchat stress device resources.

  3. 3.Tell me about a time you had to design or build something where minimizing stored user data was a hard requirement, not a suggestion. How did you think through what to keep and what to throw away?

    medium~4 min

    What interviewers look for

    • Candidate demonstrates that privacy and data minimization were treated as first-class design constraints from the start — not bolted on at the end — and can articulate the specific data lifecycle decisions they made (retention windows, anonymization, ephemeral storage).
    • Candidate describes concrete tensions they navigated — e.g., debugging vs. privacy, analytics fidelity vs. data minimization — and how they resolved them, showing the nuanced tradeoff reasoning Snap expects at mid-level.
    • Candidate references specific privacy-by-design patterns or standards they applied (differential privacy, k-anonymity, on-device processing, TTL-based deletion) rather than describing only procedural compliance like 'we followed GDPR'.

    Likely follow-ups

    • How did you handle the debugging and observability tradeoff — how do you diagnose production issues when you're intentionally not logging data?
    • If a product manager asked you to retain that data longer for analytics, how would you respond and what alternatives would you propose?

    Company context

    Ephemerality is Snap's founding product principle — messages disappear, location sharing on Snap Map is opt-in, and data minimization is culturally foundational. Snap engineers are expected to internalize privacy as a design constraint, not a legal checkbox. This question probes whether a mid-level candidate has ever built something with genuine privacy-by-design thinking, which is especially relevant for teams working on Snap Map, messaging infrastructure, and user content pipelines. Snap's Privacy and Ephemerality principle requires engineers to proactively push back on over-retention, not just comply when asked.

  4. 4.Walk me through the last time you found a serious performance hotspot in a system you owned. How did you find it, what was the root cause, and what did the fix actually look like in the code?

    medium~4 min

  5. 5.Tell me about a time you worked on a computer vision or AR problem — something where the input was pixels, depth data, or sensor streams. What made it technically hard, and how did you get it to work well enough to ship?

    hard~5 min

  6. 6.Tell me about the most complex ML or computer vision system you've personally contributed to. Where did the model or algorithm fall short in production, and what did you do about it?

    hard~5 min

Technical Questions (6)

  1. 7.You're building a Snap Map feature that shows nearby public Stories on a map tile. How would you decide what to cache client-side versus always fetch fresh from the server?

    easy~3 min

  2. 8.Snap's backend services communicate over gRPC. What's the difference between unary and server-streaming RPCs, and when would you actually use streaming for a Snapchat feature?

    easy~3 min

  3. 9.Snapchat's Spotlight feed uses a recommendation model to rank short videos for each user. If the team wants to add a new real-time signal — say, how many friends viewed a given Snap in the last 5 minutes — how would you get that signal into the ranking pipeline without blowing up latency?

    medium~4 min

  4. 10.You're on the Lens Studio platform team. AR Lens creators upload assets — 3D meshes, textures, scripts — that get processed and served to Snapchat clients. How would you design the asset processing pipeline to handle a sudden 10x spike in uploads during a major creator launch event?

    medium~5 min

  5. 11.You're given a stream of Snapchat Chat events — each event is a tuple of (sender_id, recipient_id, timestamp_ms). Write a function that, at any point in time, returns the top-K most active chat pairs by message count over a sliding 5-minute window.

    hard~5 min

  6. 12.Snapchat delivers ephemeral messages — once read, they're supposed to be gone. But building 'delete on read' reliably across a distributed system is harder than it sounds. Walk me through the failure modes and how you'd handle them.

    hard~5 min

System Design Questions (6)

  1. 13.Snapchat sends push notifications for new Snaps, Chat messages, and Story replies. How would you design the notification delivery service to make sure notifications arrive quickly and don't get lost?

    easy~3 min

  2. 14.Snap Map shows your friends' Bitmoji avatars moving around a live map. How would you design the location ingestion and serving layer that powers this?

    easy~4 min

  3. 15.Snapchat Stories are watched by hundreds of millions of users daily. How would you design the view counter system so that creators can see their Story reach in near-real-time without it falling over under load?

    medium~4 min

  4. 16.Snap Ads delivers video and AR ads at scale across Snapchat. How would you design the ad auction and selection service that picks which ad to show a user when they open a Story or Spotlight?

    medium~5 min

  5. 17.Snapchat's Chat feature needs to support disappearing voice notes — sent, played once, and gone. How would you design the storage and delivery system for ephemeral audio messages at Snapchat scale?

    hard~5 min

  6. 18.Lens Studio lets creators publish AR Lenses that run on 800 million Snapchat users' devices. How would you design the Lens distribution and update system so that a newly published Lens reaches users quickly, but a broken Lens can be killed or rolled back just as fast?

    hard~5 min

Leadership Questions (6)

  1. 19.Tell me about a time you caught a bug or quality issue in a teammate's code during review. How did you handle the feedback, and what happened next?

    easy~3 min

  2. 20.Tell me about a time you had to get up to speed on an unfamiliar technical domain quickly — something outside your comfort zone. How did you approach it, and how long before you were actually contributing?

    easy~4 min

  3. 21.Describe a time you pushed back on a product or design decision you thought was wrong. What was your argument, and what actually happened?

    medium~4 min

  4. 22.Tell me about a time you spotted a privacy or data risk in something your team was building — before it shipped. How did you raise it and what changed?

    medium~4 min

  5. 23.Tell me about a time you led the technical direction on a project where the scope or requirements kept shifting mid-build. How did you keep the team aligned and the codebase from becoming a mess?

    hard~5 min

  6. 24.Describe a time you came up with a creative technical or product solution that wasn't the obvious approach. What made you think of it, and was anyone skeptical at first?

    hard~5 min

Problem Solving Questions (6)

  1. 25.Snapchat has around 800 million monthly active users. Roughly how many Snaps — photos and videos — do you think are sent per day, and how did you get there?

    easy~3 min

  2. 26.Snap's daily active user count dropped 3% in a single day, and no code shipped and no incidents fired. How would you figure out what happened?

    easy~4 min

  3. 27.Snap is deciding whether to add a 'view receipt' feature to Snapchat Chat — senders can see exactly when their message was read. Walk me through how you'd estimate the impact of that feature on user engagement and retention before building it.

    medium~5 min

  4. 28.Estimate how much storage Snap needs to retain unread Snaps — just the ones sitting in inboxes waiting to be opened — at any given moment. Walk me through your approach.

    medium~5 min

  5. 29.Snap Map's 'Heat Map' view shows areas of high public Story activity. If you were designing a system to detect and rank trending geographic locations in real time — not just by raw volume but by velocity of activity — how would you approach it?

    hard~5 min

  6. 30.Snap's Spotlight feed is competing with TikTok and Reels for creator attention. If creator posting volume on Spotlight dropped 20% quarter-over-quarter, how would you diagnose whether this is a distribution problem, a monetization problem, or a creation-friction problem — and what data would you look at first?

    hard~5 min

More Snap interview questions