Snapsheet Software Engineer Interview Questions
& Process

The interview process started with a recruiter call, followed by a basic programming test. Then, there was a 60-minute session with the hiring manager focused on behavioral aspects. The final stage involved 3-4 hour panels with potential colleagues. It's a pretty standard process. I personally don't like wasting time, so remember to interview them back about the role, projects, and expectations.

First, I had a call with a recruiter. Then, I was given a take-home HackerRank test with three questions: an easy algo, a SQL query, and an easy frontend API implementation. After that, I met with the engineering manager to go over my resume and answer some backend questions. Finally, there were 3 interviews, each an hour long, with 30 minutes for behavioral questions and 30 minutes for HackerRank. These covered database design for a rental car app, database/API design for TinyURL, and frontend app pseudocode for a Google Maps-like implementation.

This was a great interview experience, with good communication and really engaged interviewers. It started with a 90-minute take-home coding test that had three parts: an easy algorithm, a database query, and an API request involving JSON parsing. Then, there were three 1-hour interviews. The first was with the Engineering Manager, covering behavioral questions and a live coding challenge with easy/medium LeetCode problems. The second was with a Lead Engineer. About half of this was a coding challenge to build a binary search tree, which was tough without a CS background or much LeetCode practice, but the interviewer was very helpful and made it feel more collaborative. The other half involved system design, specifically designing something like Craigslist. The final interview was with the Director of Engineering, focusing on behavioral questions, along with database and architectural topics, including questions about AWS S3.