A relatively straightforward technical discussion on predominantly fix logs and general system architecture. Most of the questions were focused around how to troubleshoot a standard client/matching engine setup.
While the questions were straightforward, the interview process was not. Despite reading and watching videos on their blog about how inclusive their work culture and ethic is, this is utter crap.
Speaking to an interviewee from the UK and one from Hong Kong, if this is what it’s like to work in an SRE team, then good luck.
Everyone says how inclusive they are and friendly, but ask a simple question and you are met with an awkward silence like you’re interrupting them. Then you get an idea of teamwork.
The example trading system doesn’t even mirror state in any real-world scenario, as the concept of market position is lost in favor of a make-believe Windows logging system.
Anyway, the takeaway is that it’s a very turgid, awkward affair, and speaking to their engineers, they are 10 years behind any modern architecture despite how much they will pay you.
Honestly, look elsewhere unless you want to learn 10-year-old tech while taking home easy money.
Troubleshoot trading system latency.
The following metrics were computed from 1 interview experience for the Jane Street Production Engineer role in Hong Kong, Hong Kong.
Jane Street's interview process for their Production Engineer roles in Hong Kong, Hong Kong is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Jane Street's Production Engineer interview process in Hong Kong, Hong Kong.