I was given access to a virtual machine that had a simplified copy of Balyasny's work environment with various things broken. I was asked to fix things and add some implementations. This is a good approach in theory, but there were a few things that made it terrible.
So, the problem with the interview was not that it was difficult per se, but that it was trying to test too many things at once over a very short period of time, without even the theoretical possibility to finish them all.
Fix a broken Docker container. It did not get enough stuff copied, and it included main program executed during the build step instead of entry point. This is not trivial in its own right, since to know that this is wrong, you need to be familiar with the project setup.
There were 15 or 17 failing unit tests that I was required to fix. However, when I randomly picked one, the interviewer advised me not to go there, since fixing that test is not trivial at all, and suggested an easier one.
Implement two functional endpoints using their web framework (they guide you through some details, but still it's not something one was expected to be familiar with out of the box, and it was not a position requirement)
The following metrics were computed from 2 interview experiences for the Balyasny Asset Management Senior Software Engineer role in New York, New York.
Balyasny Asset Management's interview process for their Senior Software Engineer roles in New York, New York is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having mixed feelings for Balyasny Asset Management's Senior Software Engineer interview process in New York, New York.