Sprig Software Engineer Interview Questions
& Process

The take-home assignment wasn't that helpful and didn't really connect with our interview discussions. They didn't really use it or bring it up, so I regret spending so much time on it instead of prepping more for the actual interview.

The interview process included a hiring manager screen, followed by separate backend and frontend interviews. Overall, the interviewers were pleasant and supportive. The interview questions were of moderate difficulty, and I believe I could have managed them if I had prepared better. My main criticism is that while deviating from standard SWE questions is acceptable, the nature of these questions should be communicated more clearly. The preparation materials provided were vague and unhelpful. A pre-interview call with recruiting, common in many processes, would have been beneficial to clarify the exercises and focus areas, but this would only work if recruiting understood the interview questions themselves. As it was, recruiting primarily acted as a communication channel between the engineering team and me. A tip for fullstack engineers with a backend focus: become highly proficient in React, CSS, and JavaScript to the point where you can code pages from scratch without relying on documentation or syntax checks, similar to how you'd approach backend interviews.

It was a really well-organized interview process. I got to speak with 4 different engineers and the hiring manager. It started with a chat with the hiring manager, then a coding exercise, and finished with a longer "virtual" on-site. The on-site included another coding interview, one focused on systems/infra, and finally an architecture discussion. A lot of the interview questions were based on real issues the team has dealt with. The whole thing wrapped up in about a week or two. They were quick to let me know about the next steps and followed up fast after the last interview.