Real, anonymous reports from people who interviewed for Software Engineer at Smartsheet, newest first and distilled into what to expect across the loop.
I went through a fairly complete sequence that felt like it covered the full stack of what they needed. After the recruiter contact, I had a technical assessment that was geared toward LeetCode-style algorithms. That was followed by a deeper technical dive focused on MySQL—how I thought about database management and how I’d approach real-world issues with it.
My process started with an HR screening call that lasted about 15 minutes. It came through a referral, and the conversation was pretty direct: they wanted to understand what I was doing in my current project, what parts of the tech stack I’d actually used, and how I handled situations involving scale and high-traffic.
The interview process typically begins with a recruiter screening, followed by a technical assessment that includes coding and system design interviews, and concludes with behavioral interviews. The structure is generally consistent, with a focus on both technical skills and real-world problem-solving.
Candidates can expect a mix of coding challenges, often LeetCode-style, and system design questions that assess their practical understanding of software engineering concepts. The technical rounds are designed to evaluate both implementation skills and system architecture reasoning.
Behavioral interviews aim to connect candidates' past experiences to the role, focusing on real-world scenarios rather than abstract storytelling. Candidates are encouraged to provide concrete examples of their work under pressure and in high-traffic situations.
Candidates reported varying experiences with communication throughout the process, with some feeling supported and informed while others experienced delays and a lack of feedback. Clear communication is crucial for maintaining candidate engagement and trust.
The timeline for receiving decisions can vary significantly, with some candidates experiencing quick feedback while others faced prolonged uncertainty. This inconsistency can affect candidates' perceptions of the process and their overall experience.
Candidates expressed the importance of preparing for both technical and behavioral aspects of the interviews, with some wishing they had better clarity on what to expect in terms of question types and interview structure. Aligning preparation with actual interview content is key.
