Real, anonymous reports from people who interviewed for Software Engineer at Smarsh, newest first and distilled into what to expect across the loop.
The process kicked off with a projects overview, and then I had to go deeper into one open-source contribution. That part was hands-on: I walked through the work essentially line by line, explaining my thinking as I followed the structure of what they wanted to understand. After that, there were some more straightforward development questions.
My start was an easygoing recruiter conversation where most of the discussion was straightforward—general questions and whether I was available for weekend shifts. It didn’t feel intense, and the people I spoke with were genuinely pleasant.
The interview process typically begins with a casual recruiter conversation focused on fit, availability, and general expectations, creating a low-pressure environment for candidates to gauge the process.
Candidates can expect multiple technical rounds that include coding challenges, often focusing on data structures and algorithms, with a practical rather than theoretical approach to problem-solving.
There are usually segments dedicated to system design and problem-solving questions, where candidates are assessed on their approach and reasoning rather than just correct answers.
While some candidates experienced timely feedback and clear communication, others reported significant delays and a lack of follow-through, leading to frustration and uncertainty about their status.
The interview process often emphasizes cultural fit and alignment in values, with interviewers seeking to understand candidates' working styles and thought processes in a conversational manner.
Candidates noted logistical challenges during in-person interviews, including disorganization and poor coordination, which detracted from the overall experience and professionalism of the process.