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.
A recruiter reached out and said they wanted to schedule me for an interview the following week, but it turned into a mess. I had to follow up three separate times because the scheduling kept getting delayed with excuses about being too busy, and I never received an actual invite. The lack of follow-through and the repeated runaround made the process feel completely unprofessional from the start, and I never got to the point of interviewing.
I went through a fairly structured path that started only after my profile was shortlisted. Once that happened, I had a screening call followed by a coding round, and then an additional interview aligned with an L1 level. The sequence felt organized enough to know what was coming next, but it also meant the process didn’t just stop at general fit checks—it moved toward an actual coding-focused step pretty early once I cleared the first barrier.
The interview process generally follows a structured path starting with a recruiter call, followed by technical interviews that include both coding and behavioral questions. Candidates noted that the flow was usually clear, allowing them to anticipate the next steps.
Technical interviews often emphasize OOP fundamentals and may include coding challenges related to basic concepts, data structures, and problem-solving. Candidates reported that while the questions were generally approachable, the final technical round could significantly impact the outcome.
Behavioral interviews are consistent across candidates, with a strong emphasis on using the STAR method to articulate past experiences, collaboration, and adaptability. Candidates were expected to discuss their projects in detail and demonstrate ownership of their work.
Candidates experienced a generally friendly and conversational atmosphere during interviews, which helped ease stress. However, some reported instances of poor communication, particularly regarding scheduling and interviewer engagement, which detracted from the overall experience.
Some interviews involved technical challenges related to remote setups, such as audio issues or disorganization during virtual interviews. Candidates noted that these factors could affect their performance and perception of the interview process.
While many candidates felt prepared and that the bar was manageable, the overall experience varied significantly, with some reporting long delays in feedback and a lack of clarity on expectations. The outcome often hinged on performance in the final technical round.