Real, anonymous reports from people who interviewed for Software Engineer at Smartsheet, newest first and distilled into what to expect across the loop.
Recruiter outreach turned into a pretty drawn-out process. I ended up with three interviews spread across about a month and a half. The overall vibe stayed relaxed, which helped, because the format was still pretty involved.
My process felt comprehensive from the start, but also a little hard to predict. After the initial step with the recruiting team, the technical assessment leaned heavily toward LeetCode-style algorithms. From there, the rounds broadened out into deeper territory: a MySQL-focused deep dive on database management, then a system design evaluation, and finally a behavioral interview.
The process typically begins with a recruiter outreach and a short HR screening call focused on the candidate's background and fit for the role. This initial step is generally non-technical and aims to gauge alignment with the company's expectations.
Candidates can expect one or more technical interviews, often involving live coding sessions that may include LeetCode-style problems or system design questions. The technical rounds are crucial for demonstrating coding skills and problem-solving abilities.
Behavioral interviews are a key component of the process, focusing on past experiences and how they align with the company's values. Candidates should prepare to discuss their work history and approach to challenges.
The interview process can vary in structure, with some candidates experiencing a clear sequence of rounds while others report confusion regarding the format and expectations. It's important to clarify the nature of each round beforehand.
Candidates often report issues with communication and feedback throughout the process, with some experiencing long delays or a lack of updates after interviews. Clear communication from the recruiter can help alleviate some of this frustration.
Many candidates leave the process without an offer, often feeling uncertain about their performance or the reasons for rejection. Reflecting on the experience can provide insights into areas for improvement and expectations for future interviews.