Wolverine Trading Software Engineer Interview Questions
& Process

The interview process involved a coding challenge with three questions first, followed by a phone interview. Then there was a virtual superday that included two coding interviews. Finally, I received an offer during a call with the recruiter. The whole process wrapped up in three weeks, and they were quite efficient and kept me informed.

The interview process was pretty standard but dragged on a bit. It kicked off with a 60-minute online assessment that was mostly behavioral questions along with one simple coding problem. Next, there was a 45-minute phone screen that involved some initial behavioral questions and a LeetCode medium difficulty problem. The final stage was a 3-hour virtual onsite, split into three 1-hour blocks: one for behavioral questions, one for LeetCode medium problems, and one for system design implementation. Everyone I talked to was nice but hard to read. I felt good about my answers, but they passed on me a few days after the onsite. When I asked for feedback, they mentioned my technical answers weren't strong enough.

I got a code challenge, which was pretty tough, needing an O(n) solution. After that, I had an hour-long phone interview that I felt went well. It covered data structures (like hash maps), multi-threading, behavioral questions, and C++. For the challenge part, it's good to practice hard algorithm questions on HackerRank. For the data structures, brush up on hash tables and collision handling. For multi-threading, know the basics and how to implement lock-free hash-maps. Also, make sure to research the company and don't hesitate to ask questions.