I've been at the same job for over four years and haven't really moved around. A while back a recruiter reached out and said HRT was hiring, so I figured I'd test the waters and scheduled the phone screen. It was two rounds.
In the first round I was given a list of events, each with a timestamp, an order ID, and a batch ID. There was already an existing function that reads two files, one for open and one for close, and I was asked to change it so you can look things up by either order ID or batch ID. For a batch, it returns the earliest start and the latest end among its events. If an order has no close, its end returns 0. The problem was given entirely verbally by the interviewer, and just getting the problem statement straight took a lot of back and forth. I was a bit panicked.
The second round started with a chat about my projects. They asked whether I had run into IO, memory, or CPU constraints and how I solved them, then asked about the difference between multi-threading and multi-processing and when to use which. I run into this stuff all the time at work, so I answered it fairly smoothly.
The coding question was a variant of itoa: add a comma after every three digits, so 1234 outputs "1,234", and negative numbers have to be handled too.
A few days later I got a rejection. Honestly it was a bit unexpected. The second round felt like it went well, so I'm guessing I just spent too long on the first round.
Does anyone who has interviewed with them know how long you usually have to wait before you can apply again after failing a phone screen?
Discussion
Loading comments…