Real, anonymous reports from people who interviewed for Software Engineer at Voleon, newest first and distilled into what to expect across the loop.
I started with a recruiter screen, and then about a week later I moved into a technical screen. After that it turned into a four-part virtual onsite, and the whole thing felt very fast-paced for how heavy it was. The most intense round was a two-hour coding session made up of multiple parts, framed like real-world problems rather than a single neat exercise. I kept feeling the pressure to maintain momentum across segments.
I went through what felt like an exhausting, high-friction process rather than a smoothly designed interview loop. Early on there were technical rounds that focused on algorithmic-style problem solving, plus a system-design-style interview and behavioral elements spread through a month-long timeline. What stood out was how many moving pieces there were and how little enthusiasm the interviewers seemed to show about the company while I was trying to engage.
The interview process typically starts with a recruiter screen followed by a technical screen, leading into a multi-part onsite that can feel fast-paced and disjointed. Candidates often experience a lengthy timeline with multiple rounds, including reference checks that can extend the overall duration significantly.
Candidates report a heavy emphasis on algorithmic problem-solving, primarily through LeetCode-style coding questions, often under tight time constraints. Many found the technical rounds to be challenging, with a focus on performance rather than collaboration or discussion.
Behavioral questions are present but often feel secondary to technical assessments, with some candidates noting a lack of engagement or enthusiasm from interviewers. This can lead to a perception that the interviewers are more focused on evaluating technical skills than assessing cultural fit.
The interview environment is frequently described as tense and mechanical, with candidates feeling that interviewers are not fully engaged or supportive during coding tasks. This lack of interaction can create a high-pressure atmosphere that detracts from the collaborative nature of coding.
Candidates often leave the process without clear feedback or understanding of why they were not selected, despite feeling they performed well. The feedback provided can be vague or inconsistent, leading to frustration and confusion about the decision-making process.
Reference checks are a significant part of the later stages, with some candidates experiencing confrontational or lengthy evaluations that feel more like interrogations. This stage can add to the overall stress and uncertainty of the hiring process.