Phone conversation with HR: General position preferences and expectations.
Online coding test: A few simple algorithm/coding questions that can be implemented in C++, Python, or Java.
Technical phone interview: Programming and probability/statistics questions.
Onsite interviews: Multiple coding questions were asked in front of a computer, with the interviewer sitting nearby. Significant weight was placed on creating unit tests. The interviews were mixed; I had a particularly bad experience in one where the interviewer left the room for a while, returned, and without attempting to understand my solution, declared it suboptimal and ignored all explanations. (I later researched this, and it's a known problem for which I had provided the best known solution).
When I tried to follow up with HR, my email was ignored.
Q: Tell about previous work.
Q: Multiple algorithmic/coding questions in Java/Python. I am not disclosing this information due to the company's privacy policy. However, generally, the questions are in the fields of data structures, dynamic programming, state machines, and graphs.
The following metrics were computed from 2 interview experiences for the Two Sigma Quantitative Software Engineer role in New York, New York.
Two Sigma's interview process for their Quantitative Software Engineer roles in New York, New York is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Two Sigma's Quantitative Software Engineer interview process in New York, New York.