
Snapp (Iran) Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 11 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Snapp (Iran).
Software Engineer
Interview had 4 steps: 1. Tech interview with a team member disscused about my previous experience and some technical scenarios and how I would solve them, for instance how would I distinguish if an endpoint is slow and how can I fix it. 2. Another tech interview more focused on algorithms and DS. 3. Talk to hiring manager 4. Culture fit
- How to implement a rate limiter?
- What are interfaces in Golang used for?
- Different functions of redis and when to use them?
Software Engineer
So the interview started late, and the interviewer asked me some algorithm questions. There was a sorting question and then a big data question, which made sense because the position was for a map team. This question was about saving map tiles. They also asked some Golang questions, like about Goroutines and how to handle graceful shutdown using signals.
- How do you find a missing number in a sequence of sorted numbers, given that the sequence can start and end at any point?
- If the Earth is tessellated with 1km triangles, each belonging to a larger 2km triangle with a unique ID, describe how you'd locate a triangle based on its ID.
- Could you explain what goroutines are and contrast them with operating system threads?
Software Engineer
This whole thing usually takes over 4 weeks. You have 3 interview rounds that normally happen over 2-3 days. First up is a quick chat with HR, just some basic stuff. They asked about my past jobs, problems I'd solved, if I'd served in the military, what salary I was looking for, and what I expected from this role. Then there was supposed to be a technical chat with the team lead, I even got an email with their name. But they didn't show. They rescheduled, and again, no-show. So, two developers from the team, who looked like they might still be students, ended up giving me the interview. It was just a whiteboard session. They threw out two algorithm questions and one system design question. Honestly, they seemed a bit off for the job, I was kinda hoping for more backend-specific stuff like API design, software principles, tech I've used, and my ideas for the team. They didn't seem too keen on my past work either, like they hadn't even looked at my resume. Got a rejection email a couple of weeks later saying they found someone better.
- Can you generate all permutations of a given string?
- How would you design a URL shortening service?
- Given an array, how would you shuffle it and then slice it into chunks of a fixed size?
Snapp (Iran) Software Engineer Interview Questions
Quoted word for word from Snapp (Iran) interview reports.
“Can you generate all permutations of a given string?”
Read reports →“Given an array, how would you shuffle it and then slice it into chunks of a fixed size?”
Read reports →“What are OS signals and what is their purpose?”
Read reports →“How do you find a missing number in a sequence of sorted numbers, given that the sequence can start and end at any point?”
Read reports →“What are interfaces in Golang used for?”
Read report →“How to implement a rate limiter?”
Read report →“How is the reactive pattern implemented within the Spring Reactive framework?”
Read report →“Different functions of redis and when to use them?”
Read report →“Could you explain what goroutines are and contrast them with operating system threads?”
Read report →Formats, difficulty and experience
Across all 11 Snapp (Iran) interview reports.