Real, anonymous reports from people who interviewed for Software Engineer at Balyasny Asset Management, newest first and distilled into what to expect across the loop.
Get your personalized Balyasny Asset Management Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
I started with a recruiter call and then moved quickly into a technical conversation with the hiring manager. After that, the process ramped up fast: I ended up with a total of seven interviews, where the second stage alone was five back-to-back sessions with different members of the team. That stretch covered a lot of C# and .NET depth, plus coding and architecture-style questions. I also had to talk through projects I’d worked on and show how I understood the business/industry side of what the team does.
The interviews were genuinely tough at points, even though most of the people I spoke with were friendly and helped keep the tone productive. What really stuck with me wasn’t the difficulty—it was how the process ended. After I didn’t get an offer, they refused to share any feedback at all, blaming the high volume of candidates. I’d already invested a huge amount of time, and it felt disrespectful to go from asking for that commitment straight to silence afterward.
7 months ago
Difficult Negative New York, NY
My process moved through three 45-minute interviews. The first one was behavioral, then I went into a combined system design plus coding round. The last interview was the one that hit the hardest: it focused on difficult computer science topics and covered areas like Java/Python compiler concepts and garbage collection, along with networking and database design.
By the time I reached that third round, I felt clearly less prepared than I had been earlier. The pace and breadth of what they expected made it difficult to settle into a rhythm. I managed to answer some parts, but overall it didn’t feel like a problem I could easily recover from once I realized how far along they were going.
> 1 year
Average Positive New York, NY
My interview journey was built around multiple team-member conversations that felt deliberately “team based.” I had rounds that went beyond just the i…
> 1 year
Easy Negative London, England
My first step was an offline HackerRank REST API task with a one-hour time limit. The work itself was achievable, so I felt like I could show how I ap…
> 1 year
Average Neutral London, England
I ended up doing what felt like a virtual super day: three back-to-back, 45-minute interviews. The first two were technical, and the last one was beha…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process typically starts with a recruiter call, followed by a series of technical and behavioral interviews, often culminating in a final round that can be intensive and lengthy. Candidates reported experiences ranging from compact, multi-round sessions to extensive processes with numerous interviewers.
Recruiter callMulti-roundBehavioral
Technical Assessments
Candidates faced a variety of technical challenges, including HackerRank coding tasks, system design discussions, and questions on specific programming languages like C# and Python. The technical rounds often included both coding problems and theoretical questions, with some candidates feeling the difficulty varied significantly between rounds.
HackerRankSystem designCoding problems
Behavioral & Cultural Fit
Behavioral interviews were a significant component, focusing on candidates' motivations, past experiences, and how they align with the company's culture. Interviewers emphasized understanding candidates' personal fit within the team, which some found to be a central theme throughout the process.
Cultural fitMotivationsTeam alignment
Communication & Feedback
Candidates expressed frustration over the lack of communication and feedback post-interview, with many reporting no follow-up or vague responses after their interviews. This left some feeling disrespected and uncertain about their performance and the outcome.
FeedbackCommunicationPost-interview silence
Interview Environment & Professionalism
The professionalism of interviewers varied, with some candidates experiencing disorganized sessions or unprofessional behavior, such as interviewers being unprepared or distracted. This impacted the overall impression of the interview process and the company's culture.
Candidates noted that the difficulty of questions could be inconsistent, with some rounds feeling significantly harder than others. This discrepancy sometimes led to feelings of being unprepared or overwhelmed, particularly in later stages of the interview process.