Real, anonymous reports from people who interviewed for Software Engineer at Belvedere Trading, newest first and distilled into what to expect across the loop.
My process felt like it dragged a bit, but it was still fairly positive overall. HR was friendly, and the director ended up changing the flow—what started as a behavioral-style conversation turned into more technical discussion. The technical assessment itself was described as straightforward, and the real thread that stood out was multithreading: if I had a thorough grasp there, the whole thing felt much easier to navigate.
After finishing a take-home assessment, I moved straight into a long technical interview that was split into three parts. I did live coding first, then I got a system design discussion, and finally I had to go back to the take-home work and revise/extend the code based on new requirements. I felt like the interview was constructive—there was a real focus on how I thought through changes rather than just getting a single final answer.
The interview process typically begins with a friendly HR call focusing on the candidate's resume and general fit for the role, lasting around 30-45 minutes. This step sets expectations for the technical assessments to follow.
Candidates are required to complete an online coding assessment that includes multiple timed questions, often with a focus on C++ and financial scenarios. The prompts can be complex and require careful reading to understand the requirements.
The technical interviews typically involve a mix of live coding, system design discussions, and reviewing the candidate's previous coding work. Interviewers emphasize the thought process behind solutions and how candidates would adapt their code under changing requirements.
Many technical questions are framed within financial contexts, requiring candidates to apply coding skills to scenarios related to trading and finance. This domain-specific focus can significantly influence how candidates approach problem-solving.
Interviews can be lengthy, often lasting over two hours, and may include multiple rounds in a single day. Candidates should be prepared for a rigorous evaluation of both coding skills and reasoning under pressure.
Candidates often report a lack of detailed feedback after interviews, with many not receiving offers despite positive experiences. It's common for candidates to feel that the process was well-structured but ultimately did not lead to further opportunities.
