First-round on-campus interview:
Mainly, I was asked how I would approach a couple of algorithmic problems that the interviewer described as simplifications of stuff he works on. We discussed the solutions at a pretty high level, and I didn't have to write much code. The problems were interesting but not killer, involving dynamic programming and some combinatorial and probability calculations, and happened to draw on my strengths. I got an invitation to NYC the same day.
On-site interview day:
They put me in a nice hotel a block from their office. I had a long day of interviews from 10 am to 5 pm, with about 1-hour one-on-one sessions. There was also a laid-back one-on-one lunch at a restaurant midday. The interviewers included both programmers and quants, with corresponding questioning styles. I was posed challenging questions on software engineering, algorithms, statistics, and quantitative reasoning. There were no fit or behavioral questions beyond the introductory chit-chat. The people were all really smart, and personalities ranged between pleasant/relaxed and nerdy/quirky (nothing adversarial).
I left feeling it went OK, but I did need a lot of help on some of the problems. I got a rejection email one week later.
Three of my 150 friends have phone numbers ending in a permutation of the digits 0, 1, 4, and 9. Is this surprising?
The following metrics were computed from 6 interview experiences for the D. E. Shaw Software Developer role in New York, New York.
D. E. Shaw's interview process for their Software Developer roles in New York, New York is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for D. E. Shaw's Software Developer interview process in New York, New York.