Snap

Updated July 12, 2026 · techinterview.org

Snap Interview: Mobile and AR Focus

Did my Snap interview in 2024 for a backend role. Despite being backend, they still cared that I understood mobile challenges – Snapchat is mobile-first, and that shapes everything.

What’s Different About Snap

They’re fighting Instagram and TikTok for Gen Z attention. That means: speed matters (app opens to camera in < 1 second), AR features need to be smooth, and anything that delays user engagement is bad.

The technical bar is high but the culture is more relaxed than you’d expect. Less pressure than Meta, more focus on creative solutions.

The Process

Recruiter Screen (30 min): Standard intro. They asked if I use Snapchat (I didn’t regularly – I started using it before my tech screen). Honesty is fine but show interest.

Technical Screen (45 min): One coding problem plus system design discussion. Mine was: “Design an image filter system.” Not just the algorithm – think about mobile constraints, battery life, processing time.

Virtual Onsite (4 rounds):

• Coding (2 rounds): Medium difficulty, often with mobile context. Mine included: “Optimize image loading for slow networks” and a graph problem (friend suggestions).
• System Design: Design something at Snap scale. I got “Design Stories feature backend.” Consider: storage (images/videos), expiration (24 hours), and privacy.
• Behavioral: Questions about working fast, handling ambiguity, and creative problem-solving. They value speed of execution.

Technical Focus Areas

• Mobile Optimization: Battery life, network efficiency, offline support. Expect to reason about what drains the phone – background refresh, GPS polling, and radio wakeups all cost power – and why batching requests saves both battery and data. Show that a feature still works on a spotty subway connection and syncs once the signal returns.
• Computer Vision: Face filters, AR features, object detection. You won’t build a neural net on the whiteboard, but know the pipeline: detect a face, track landmarks, then render an overlay every frame. Explaining why inference runs on-device instead of a round trip to the server is the kind of tradeoff they probe.
• Real-Time Communication: Chat, video calls, live stories. Know how messages get delivered fast and in order – WebSockets versus long polling, delivery receipts, and presence. For video calls, be ready to talk through WebRTC and how you’d degrade gracefully when a connection drops.
• Media Processing: Image/video compression, filters, effects. Understand codec tradeoffs – H.264 versus newer formats, lossy versus lossless, and why you downscale before upload. A common probe is keeping a filter looking smooth while shrinking the file so it uploads fast on mobile data.
• Algorithms: Graphs (social network), trees, dynamic programming. Graph traversal shows up because the friend network is a graph, so practice BFS/DFS, shortest path, and connected components. Trees and DP fill out the rest – know the common patterns cold instead of memorizing one-off tricks.

My Preparation

1. Used Snapchat Daily: Not just posting – I played with every feature. Lenses, Spotlight, Stories, Snap Map. Discussed feature ideas in my interview.
2. Learned Mobile Basics: Even as backend, I studied mobile constraints. Battery consumption, network requests, cache strategies. This came up.
3. Studied Computer Vision: Basics of face detection, image processing. Didn’t need PhD-level knowledge, just understanding.
4. Did 100 LeetCode Mediums: Snap doesn’t grind you with hard problems. Clean, working solutions matter more.
5. Speed-Focused Practice: Time-boxed problem solving. Snap values shipping fast over perfect solutions.

What I Learned

Snap cares more about product sense than some companies. They asked “How would you improve our camera?” and wanted real ideas, not technical jargon. Think like a product person, not just an engineer.

Also, they’re lean. Smaller teams than FAANG means more ownership but also more context-switching.

The Stock Situation

Let’s be real: Snap stock has been rough. From $80+ in 2021 to under $10 in 2022, now back to $10-15 range. Your RSUs might not be worth much. People join for the product and team, not to get rich.

If stock comp matters to you, negotiate higher base or look elsewhere.

Culture Check

Young team, LA-based HQ (Venice Beach office is nice). More startup vibe than big tech. Work-life balance is decent – they know burnout kills creativity.

Comp: Base is competitive, but RSUs are risky given stock performance. Total comp is 20-30% below Meta/Google. Make sure you’re okay with that.

Last Updated: February 2026