
Snapsheet Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 86 interview experiences · FREE TO READ
Which role are you interviewing for?
19 roles · 86 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Snapsheet.
Software Engineer
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.
- Basic programming, basic SQL, and basic API calls were asked.
- For behavioral questions, brush up on projects you completed or coordinated, as a Sr engineer is expected to delegate and make a higher impact.
- In the last round, spend time showcasing your thought process and effectiveness.
Account Manager
I went through their whole interview thing. They set up interviews pretty fast, but the actual process was a mess. When I asked about standard account management stuff like retention metrics, churn drivers, and keeping revenue stable, they kept saying it was irrelevant. This was weird because then they said retention, cross-sell, and up-sell were the main KPIs. That kind of contradiction is a big red flag if you've actually worked in revenue-focused jobs. The leadership didn't seem to get basic sales or customer success. Neither interviewer had a sales or revenue background, and you could tell because they got defensive when I asked strategic questions. If leadership can't explain how to hit quota or how success is tracked, it's hard to trust the department's direction. After all the interviews, when they said they were making a decision, they just stopped responding. Then, while they were ghosting me, they reposted the same job but for way less money. Changing compensation mid-process without telling candidates is shady and makes you wonder about the company's stability. Their whole business model is also questionable. They act like a tech company, but they're really a managed service provider that relies a lot on unpredictable claim volume, which is a risky setup if you know insurance operations. When even basic questions about revenue resilience, forecasting, and customer adoption get vague answers, it's tough to see how a new hire would succeed. It felt like a company with no clear direction, bad communication, and leadership not on the same page. Candidates need clear answers, consistent info, and quick follow-up, none of which happened here. I wouldn't recommend applying until they get their operational stuff and leadership sorted out.
- Can you share an instance where you managed a dissatisfied customer and what steps you took to resolve the issue?
Employee Experience Associate
My interview experience started with an initial screen with Kyrsa from the People team. She was really nice and gave me a good overview of the role and company. After that, I had a few more interviews, including a take-home assignment which was surprisingly enjoyable and let me show my thinking process. I talked to people from the People team and other departments, and all the conversations were meaningful and they asked good questions. It felt like they really wanted to know me and for me to know what it's like to work at Snapsheet. The last interview was with a senior leader and felt like a genuine discussion. Kyrsa did a great job making the whole process feel smooth, transparent, and well-paced.
No confirmed questions were included in this interview report.
Account Executive
I invested weeks in their interview process, going through four separate rounds. Each person I spoke with gave me different answers about what the role actually entailed, but I stayed hopeful, trusting the process. I was told things like “you’d be a great fit” and “you know how to do the job,” which made me believe I was on the right track. I sent follow-up thank-you notes after every round, and despite my efforts to show genuine interest and gratitude, not one person responded—not a word. After the final interview with the CRO, I was told the company had “changed what they’re looking for” and that I “didn’t align with their needs.” Fair enough—roles evolve. But when I checked LinkedIn shortly after, I saw the exact same job reposted with the same description. I even reached out to the team on LinkedIn for clarity and received nothing but silence. At that point, I felt lied to. If I wasn’t the right fit, why not just say so instead of making me feel like I wasted my time? Job hunting is already stressful, but this experience was demoralizing. Companies forget that candidates are people—people who rearrange schedules, prepare intensely, and invest energy into opportunities that seem promising. I expected more respect and transparency from a company like Snapsheet. If Snapsheet does read this, my hope is that they reconsider how they treat candidates in the future. Silence is the worst kind of rejection, and dragging someone through a process only to leave them confused and ignored isn’t fair.
- Tell me about your experience with long sales cycles, and if you’ve had a similar role before.
- Are you experienced in sales?
- Are you a good fit for this role?
Snapsheet Interview Questions
Quoted word for word from Snapsheet interview reports.
“Given a string of parentheses, determine if it is valid by checking for matching pairs.”
Read reports →“What is the most common character in a given string?”
Read reports →“What are three potential suspension issues following a collision?”
Read reports →“Is there a way to optimize the time complexity further?”
Read reports →“What steps are involved in replacing a Quarter panel with an LKQ assembly?”
Read report →“How would you design a database schema for students and enrollments?”
Read report →“Could you implement a solution for a moving average, ensuring it's rounded up to four decimal places?”
Read report →“How would you approach validating parentheses, perhaps using a Stack?”
Read report →“Could you solve Leetcode easy problems using a Hashmap?”
Read report →Formats, difficulty and experience
Across all 86 Snapsheet interview reports.