Real, anonymous reports from people who interviewed for Software Engineer at FloQast, newest first and distilled into what to expect across the loop.
I started with a technical conversation that went through my resume, then about a week later I moved into a virtual onsite. The onsite was three back-to-back 45-minute interviews. Two of them were technical and the last one was more of a cultural fit discussion.
I applied twice before a recruiter reached out after the second submission. The process ended up being three technical interviews, and it was specifically a mid-level track: two of the sessions were live coding and the third was more of an open discussion focused on infrastructure.
The interview process typically includes an initial recruiter call followed by a series of technical and behavioral interviews, often culminating in a multi-part onsite interview. The overall timeline is generally quick, with many candidates noting a process duration of around 1.5 to 3.5 weeks.
Candidates can expect multiple technical interviews focusing on coding, system design, and real-world problem-solving rather than purely algorithmic challenges. The technical questions are often framed to reflect practical engineering tasks, with a mix of live coding and design discussions.
Behavioral interviews are a significant component, assessing cultural fit and work style through discussions about past experiences and project involvement. These conversations tend to be friendly and conversational rather than strictly evaluative.
The overall difficulty of the interviews is generally described as average, with many candidates feeling that the environment is supportive and low-stress. However, some candidates reported inconsistencies in the technical expectations, particularly regarding system design for junior roles.
Candidates expressed a desire for more transparency and feedback throughout the process, with some reporting generic rejections and a lack of constructive feedback after interviews. Good communication from recruiters is noted as a positive aspect of the experience.
Candidates recommend preparing for a mix of coding challenges and system design discussions, as well as being ready to articulate past project experiences. Familiarity with the specific technologies mentioned in the job description can also be beneficial.
