Real, anonymous reports from people who interviewed for Software Engineer at St Engineering, newest first and distilled into what to expect across the loop.
I started with a Teams meeting where the interviewers didn’t have their cameras on because they were working from a secure area where cameras weren’t allowed. The process kicked off in a pretty standard way: I introduced myself, then they outlined the role and its key responsibilities before moving into questions. The whole vibe felt easy and manageable, more conversational than intense.
My interview felt pretty professional and straightforward. It started with a quick introduction about myself—background and previous projects—and then the interviewers drilled into my software development fundamentals. I got questions that covered C++ and debugging, and they repeatedly tried to connect the technical side to my actual project experience.
The interview process typically involves multiple stages, starting with an HR screen, followed by technical assessments and interviews with hiring managers or team leads. Candidates noted that the flow can vary from quick and straightforward to more drawn-out with several rounds, often taking weeks to finalize.
Candidates experienced a mix of technical assessments, including coding challenges on platforms like HackerRank, with questions often centered around data structures, algorithms, and specific programming languages like C++ and Java. The technical interviews emphasized not just knowledge but also the ability to articulate thought processes and problem-solving approaches.
Interviews often included behavioral questions aimed at understanding candidates' past experiences, teamwork, and problem-solving strategies. The tone was generally conversational, with a focus on fit for the role rather than solely technical prowess, allowing candidates to discuss their projects and motivations.
The atmosphere during interviews varied significantly; while many candidates reported a friendly and low-pressure environment, others experienced a more intense and stressful dynamic, with some interviewers being perceived as rude or dismissive. This inconsistency affected candidates' comfort and performance.
Candidates frequently noted issues with communication and follow-up after interviews, with many experiencing delays in receiving feedback or updates on their application status. This lack of timely communication contributed to feelings of uncertainty and frustration throughout the process.
The overall difficulty of the interview process was described as variable, with some candidates finding it manageable and others feeling challenged by the technical depth and interpersonal dynamics. Many emphasized the importance of being prepared for both technical and behavioral aspects to navigate the experience successfully.