Most people are nice to work with and super helpful. However, it's a bit of a gamble, as your environment/WLB will largely depend on which team you land on.
Slightly better WLB than similar trading firms.
There is a healthy obsession with QoL features, such as build, which is nice for devs.
Don't over-hire.
Take more responsibility for failed projects.
Give better feedback.
Technical Interview - 30 minutes. Questions ask about: * Machine Learning, such as time series prediction. * Databases, including how to design them and how to improve existing designs. * Basic statistics knowledge. * Any random topics.
The first stage was a 2-hour HackerRank challenge, including a few multiple-choice questions and two coding questions. The second stage was Codepair, with a pretty simple task: implement some methods for a class. The final stage was a 2-hour interv
One OA, three round technical interviews, and one bq. The OA was easy, and the technical interviews were difficult. They asked many C++ details and about the implementation of templates and threads. This was not what is normally asked for a C++ devel
Technical Interview - 30 minutes. Questions ask about: * Machine Learning, such as time series prediction. * Databases, including how to design them and how to improve existing designs. * Basic statistics knowledge. * Any random topics.
The first stage was a 2-hour HackerRank challenge, including a few multiple-choice questions and two coding questions. The second stage was Codepair, with a pretty simple task: implement some methods for a class. The final stage was a 2-hour interv
One OA, three round technical interviews, and one bq. The OA was easy, and the technical interviews were difficult. They asked many C++ details and about the implementation of templates and threads. This was not what is normally asked for a C++ devel