Real, anonymous reports from people who interviewed for Software Engineer at St. Charles Trading, newest first and distilled into what to expect across the loop.
After a recruiter screen, I moved into a manager and team interview that felt organized and focused on fundamentals plus fit. The very first HR-style call covered my background, why I was interested, relocation flexibility, and general behavioral topics. It wasn’t robotic—more conversational than canned—and it set expectations clearly about how the rounds would run.
My interview started with a manager discussion that sounded routine at first, and then it turned into something that felt chaotic. The plan was for an in-person technical troubleshooting plus design and architecture discussion using a whiteboard, but when I got to the site I ended up joining a Teams setup where the interviewers joined remotely as well. Only one interviewer turned their camera on for about five minutes of questioning, and the rest of the time it was like talking to faceless blocks—plus the audio was rough enough that I had to ask people to repeat themselves multiple times.
The process typically begins with a recruiter call that covers basic background, motivation, and some behavioral questions, setting a conversational tone for the subsequent rounds.
Candidates can expect a strong emphasis on technical fundamentals, particularly around SQL, OOP concepts, and data structures, with some interviews including coding challenges or conceptual discussions.
Behavioral questions are prevalent throughout the interviews, often requiring candidates to use the STAR method to articulate their experiences and teamwork, emphasizing clarity and ownership.
Candidates reported mixed experiences with interview formats, including some chaotic setups with remote elements, which affected communication and clarity during technical discussions.
The interview process is described as relatively fast-paced but can vary in communication consistency, with some candidates experiencing long waits for feedback and closure after interviews.
While the technical questions are grounded in fundamentals, candidates noted the importance of being prepared to explain their past projects and technical concepts clearly, rather than just solving problems.
