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 went through an early, mostly conversational interview flow with light technical screening on a short timeline.
I had an interview journey that started with motivation/fit and role expectations, with limited indication of heavy coding.
The interview process typically includes an initial HR screen followed by a technical discussion and a final interview with management, often conducted virtually. Candidates should expect a mix of casual conversation and structured technical questions throughout the process.
Candidates may encounter a variety of technical assessments, ranging from straightforward coding tests to discussions about engineering fundamentals, with a notable emphasis on practical skills rather than algorithm-heavy problems. Familiarity with tools and languages like C++ is often assessed.
Behavioral questions focusing on teamwork, problem-solving, and personal motivation are common, with interviewers looking for cultural fit and alignment with the company's values. Candidates should prepare to discuss their past experiences and how they handle challenges.
The interview environment can vary significantly, with some candidates reporting a friendly, low-pressure atmosphere while others describe high-pressure or even hostile experiences. Being prepared for varying interview styles is essential.
The efficiency of logistics and communication can fluctuate, with some candidates experiencing quick coordination and feedback while others face delays or lack of follow-up. Candidates should be proactive in seeking clarity and updates throughout the process.
Most candidates report not receiving offers, often reflecting on the importance of preparation for both technical and behavioral aspects. Understanding the role's expectations and aligning personal experiences with those expectations can be crucial.
