Real, anonymous reports from people who interviewed for Software Engineer at FlexTrade Systems Inc., newest first and distilled into what to expect across the loop.
My screening involved a HackerRank exam that turned out to be very hard. What caught me off guard was that the platform didn’t allow me to use any outside resources, and I realized I couldn’t reliably recall the syntax for functional programming—something that was listed as a small requirement in the application.
After a straightforward intro call, I walked through my background from start to finish, focusing on my most recent role and the architecture, day-to-day work, and core language uses that mattered to it. Since I was a junior developer, the call felt pretty “storytelling”-oriented rather than deep grilling, and it set the tone for what came next.
Candidates typically start with a recruiter call followed by an online coding assessment, often using platforms like HackerRank or LeetCode. The difficulty can vary, but many found the assessments to be challenging, with some candidates struggling due to specific language requirements or hidden test cases.
The technical interviews often involve multiple rounds focusing on coding problems, language-specific questions, and sometimes system design or OOP concepts. Candidates noted a shift from general coding to specific language details, which could catch them off guard if they weren't well-versed in the required language.
Behavioral interviews are included but tend to be less emphasized compared to technical discussions, with some candidates feeling that they lacked the opportunity for in-depth conversations about their experiences. The tone of these interviews can vary significantly, impacting the overall candidate experience.
The interview process is generally well-structured, moving from initial screening to technical assessments and then to behavioral interviews. However, candidates reported inconsistencies in scheduling and communication, with some experiencing ghosting or lack of feedback after interviews.
The overall difficulty of interviews is perceived as moderate to hard, with candidates expressing frustration over specific technical questions or the lack of clarity in problem requirements. Positive interactions with interviewers can enhance the experience, while negative interactions can leave candidates feeling discouraged.
Candidates often report a lack of closure after interviews, with some not receiving any feedback or follow-up communication. This can lead to feelings of unprofessionalism and uncertainty regarding their performance and fit for the role.