Sefism is free for learners. We are here to help you grow, one step at a time.Join for free
Sefism.
Product engineeringProduct company

Snap

Builds Snapchat, a camera and messaging app, along with augmented reality tools and Spectacles smart glasses.

Not known5 stage process documentedFounded 2011
Headquarters

Santa Monica, California, United States

Headcount

1,000 to 5,000

1,000 to 4,999 people
Work model

Not known

Hiring

Not known

Not enough signal to say. Check the careers page directly.
Where to apply
Careers pageWebsite

Ask for a referral to Snap

A referral only means something if the person giving it can actually speak to your work. I will refer you where I know someone on the inside and your profile genuinely fits the role, and I will tell you plainly when I cannot. Either way you get an answer, and a straight one.

  • I read every request. A reply takes a few days, sometimes longer.
  • I will not refer someone for a role their profile does not fit. It wastes your time and costs me the contact.
  • Where I cannot refer you, I will say why, and point you at the way in that does work.
  • Nothing you send here is shared with anyone without you agreeing to it first.

If you found the opening, paste it. It tells me which team you mean.

A Drive, Dropbox or personal-site link is fine. Make sure it opens without a request for access, or I cannot read it.

At least a short paragraph. This is what I would be putting my name behind, so specifics beat adjectives.

Comma separated, up to six. Things you would be happy to be tested on.

Open internships

How they hire

Snap uses competency-based interviewing across all roles. Interviews are sometimes grouped into one day and sometimes spread out, virtual interviews require cameras on, and external resources and AI tools are not allowed. Behavioural questions are woven into the technical rounds rather than held in a separate round, according to candidates.

  1. 1

    Recruiter call

    Reported +1
    Recruiter screenRemote

    Covers your background and interest in Snap, and may include questions about how well you know its products.

  2. 2

    Technical phone screen

    Reported +1
    Live coding1 hoursRemote

    A data structures and algorithms interview in a shared coding environment, sometimes with light behavioural questions.

  3. 3

    Onsite coding rounds

    Reported
    Technical interview

    Several algorithm and data structure rounds drawn from a shared question bank, typically medium to hard, where speed to a working solution matters.

    ArraysStringsHash tablesParsing
  4. 4

    System design

    Reported
    System design1 hours

    A high-level design question usually tied to a product like chat or photo sharing.

  5. 5

    Hiring manager Q&A

    Reported
    Hiring manager

    A conversation with a hiring manager that candidates describe as largely non-evaluative. Team matching happens after the offer.

What comes up

Recurring themes from candidate accounts, not a question bank. Nobody is served by leaked question lists, least of all you in the interview.

  • Values competencies

    Official

    Snap assesses nine competencies grouped under its values Kind, Smart and Creative, such as courage, decision quality and managing ambiguity.

  • Craft competencies

    Official

    Role skills are assessed through behavioural questions or through demonstrating the skill directly.

  • Behavioural answers in S.A.I.L. form

    Official

    Snap asks candidates to describe the Situation, their Action, the Impact and what they Learned.

  • Algorithms under time pressure

    Reported

    Candidates describe LeetCode-style medium to hard questions where finishing a running solution quickly is key.

Worth reading before you apply

From the Sefism resource library, matched to the rounds above.

Roadmap
Coding Interview Playbook

A structured learning path through coding interview preparation that brings together data structures and algorithms fundamentals, recursion and the pattern-based approach to coding questions in one order. It totals 77 chapters and 1,054 lessons, with quizzes, flashcards and a certificate. Use it when you have plenty of material but no clear plan for what to study first.

  • Job search
  • DSA
  • Career
Design Gurus · Interview Prep · 3 to 6 months
SubscriptionDetails
Roadmap
FAANG Coding Interview Roadmap

A bundle of five company-specific question courses covering the problems most often reported from Meta, Microsoft, Amazon, Google and Oracle coding rounds, each split into easy, medium and hard sets with worked solutions. It suits candidates who already know the core patterns and have a loop booked at one of these companies, and want to rehearse on the questions those interviewers are known to ask.

  • Job search
  • DSA
  • Career
Design Gurus · Interview Prep · 3 to 4 months · Advanced
SubscriptionDetails
Roadmap
System Design Interview Playbook

A learning path that bundles five courses into one sequence for system design preparation: System Design Fundamentals, Grokking the System Design Interview, Advanced System Design Interview Volume II, Grokking Microservices Design Patterns and Grokking Design Patterns for Engineers and Managers. Together they add up to 76 chapters and 666 lessons. It suits engineers who want a complete, ordered curriculum instead of assembling one from scattered posts.

  • System design
  • Job search
  • Career
Design Gurus · System Design · 2 to 4 months
SubscriptionDetails
Course
Grokking Tech Salary Negotiations

A practical course on negotiating compensation in tech, from preparing and building a strategy to specific tactics, the full package beyond base salary, handling multiple offers and asking for a raise. It has tailored sections for fresh graduates and experienced engineers. It suits anyone with an offer coming, and anyone who has ever accepted the first number out of discomfort.

  • Career
  • Job search
Design Gurus · Career Growth · 1 week
SubscriptionDetails
Cheat sheet
Sefism University to Job-Ready Cheat Sheet

The quick-revision companion to the University to job-ready roadmap: OOP, Git and engineering practice, data structures, DBMS, operating systems and networks, then projects, choosing a direction, getting experience and the hiring process. It has editions for first or second year, third year, and final year. Revise a chapter a week alongside your courses and before assessments.

  • Career
  • Job search
  • CS fundamentals
  • DSA
Sefism · Career Growth · Reference · Beginner
FreeDetails
Book
Fundamentals of Data Engineering

The best single book for understanding what data engineering is and how the pieces fit, organised around the data engineering lifecycle rather than any one tool. Read it alongside a hands-on course: it explains why things are built the way they are, the course teaches you to build them.

  • System design
  • Databases
  • Cloud
  • Career
O'Reilly Media (Joe Reis and Matt Housley) · System Design · About 450 pages · Beginner
PaidDetails
Browse the whole library

What it pays

Nothing collected for this company yet, and nothing worth guessing at. A made-up range is worse than no range because people negotiate against it.

Add to the Snap page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.

Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

Universities they recruit from

No sourced university links yet. A campus drive, a career fair appearance or an internship partnership is what puts a university here.

Add to the Snap page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.

Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

How to actually get seen

Prepare a handful of stories in Snap’s own Situation, Action, Impact, Learning format mapped to its Kind, Smart and Creative competencies, because they come up in every round.

Sources

Whole profile last checked 2026-09-22.

Interviewed at Snap? Fill in what changed.

Processes change, rounds get added, tests get replaced. If what you went through was different from what is on this page, tell me and I will update it.

Want me to refer you here?

Send me the role, your CV and a few honest paragraphs on why you fit it. Where I know someone inside and your profile matches, I will make the introduction. Where I cannot, I will tell you why and point you at the route that does work. You get an answer either way.

Ask for a referral to Snap

A referral only means something if the person giving it can actually speak to your work. I will refer you where I know someone on the inside and your profile genuinely fits the role, and I will tell you plainly when I cannot. Either way you get an answer, and a straight one.

  • I read every request. A reply takes a few days, sometimes longer.
  • I will not refer someone for a role their profile does not fit. It wastes your time and costs me the contact.
  • Where I cannot refer you, I will say why, and point you at the way in that does work.
  • Nothing you send here is shared with anyone without you agreeing to it first.

If you found the opening, paste it. It tells me which team you mean.

A Drive, Dropbox or personal-site link is fine. Make sure it opens without a request for access, or I cannot read it.

At least a short paragraph. This is what I would be putting my name behind, so specifics beat adjectives.

Comma separated, up to six. Things you would be happy to be tested on.

Add to the Snap page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.

Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

Work with me

Stuck on something specific?

Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.

Book a free sessionSee all services

Follow along

New writing, resources and project ideas land here first.