Process
I submitted my resume online, then received an email 3-4 weeks later inviting me to a phone interview. They did not specify that the interview would be technical, but I was expecting it to be.
The interview was poorly conducted. The questions were theoretical and focused more on running code than actually writing code. It concluded with a probability brainteaser, which was fun, though I did not solve it. I was not invited for the second round.
My advice: study core concepts such as runtime versus compilation, data structures, and so on.
Questions
What are some things that work in C++ that don't work in C?
Was this helpful?
Interview Statistics
The following metrics were computed from 13 interview experiences for the D. E. Shaw Software Developer role in United States.
Success Rate
D. E. Shaw's interview process for their Software Developer roles in the United States is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having good feelings for D. E. Shaw's Software Developer interview process in United States.
D. E. Shaw Work Experiences
- 4.0Bunch of smart folksSoftware Developer • Former EmployeeApril 12, 2014Pros: This place has a bunch of really smart folks. They take really good care of their employees. Honest, sincere effort are rewarded quite well.Cons: By taking really good care of employees, they make it difficult for employees to quit. This makes it challenging when we want folks to move on. They keep clinging on, which is neither good for them nor the company.
- 4.0Good but hardSoftware Engineer • Current EmployeeJanuary 19, 2023Pros: LeetCode easy, but I didn't have a lot of LeetCode experience back then.Cons: System design focus. Rescheduled multiple times.
- 4.0Nice place to be inSoftware Engineer • Current EmployeeNovember 1, 2009Pros: Freedom to make decisions Direct exposure to the clients Challenging problems to solveCons: Stressful, deadlines every now and then. Not your cup of tea if you don't like finance.
D. E. Shaw Interview Questions
