
Snapdocs Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 14 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Snapdocs.
Software Engineer
First, I had a call with the recruiter. Then, a 1-hour technical screen over video where I had to solve one coding problem like coin change, making sure the code compiled and ran, and writing tests for it. After that, it was an onsite (virtual) that lasted 3-4 hours. This included a coding problem, like number to word conversion, a design session, and a behavioral interview. Finally, I met the Team Manager.
- Given an array of coin denominations, a price, and the amount paid, can you solve the coin change problem?
- How would you convert a number into its word representation?
- Could you write the code for the coin change problem, ensuring it compiles and runs?
Software Engineer
I had an easy tech phone screen, then they invited me to a virtual onsite that lasted two days. I got a schedule beforehand, but they changed the order and the interviewers without telling me, so I prepared for the wrong interviews and used the wrong names with the interviewers. The actual interview questions weren't that hard and I felt good about my interviews then. They said I'd hear back in 2 days, but they didn't. It's been 2 weeks and I haven't heard anything, even after I emailed the recruiter myself. It was so unprofessional and I felt like I wasted two days interviewing with them.
- How would you convert an integer to a string?
- Can you walk me through the architecture of a challenging recent project?
- What would your manager say your biggest strength is?
Software Engineer
This company loves to waste candidate time with DP interview questions. I was given a DP problem to solve in 30 minutes, and even though I got about 90% of the way there, missing just one requirement, I still got rejected. Big tech companies advise against DP questions, yet SnapDocs uses them to test candidates on obscure algorithms. I doubt their actual codebase uses DP, and I bet the interviewer couldn't solve a different DP question in an hour. My advice to the company and its SWE interviewers: ask about algorithms with real-world business applications, not theoretical ones, and stop trying to be like FAANG.
- How would you approach a dynamic programming problem like the coin change problem?
Snapdocs Software Engineer Interview Questions
Quoted word for word from Snapdocs interview reports.
“How would you convert a number to its string representation, like 0 to zero?”
Read reports →“How would you convert an integer to a string?”
Read reports →“Given an array of coin denominations, a price, and the amount paid, can you solve the coin change problem?”
Read reports →“Can you write a function to convert a number into its text form, like turning 1 into 'one' or 1,203 into 'one thousand two hundred three'?”
Read reports →“How to calculate change at a cash register without knowing the product price?”
Read report →“How would you convert a number into its word representation?”
Read report →“For the number to word conversion problem, can you provide the solution?”
Read report →“What are the APIs for a given workbench?”
Read report →“How would you approach a dynamic programming problem like the coin change problem?”
Read report →Formats, difficulty and experience
Across all 14 Snapdocs interview reports.