I had a bug hunt as part of an interview once (or, I should say, once that I remember). It was different from that proposal in that the code was not part of the company's actual codebase - it was entirely fabricated for the test. It was fun, though; I enjoyed that more than livecoding and live-whiteboarding.

I had one that wasn't fabricated when I worked at Strip. There was an old bug in the requests library for Python where it was sending wrong data when posting a stream and the response had to be retried. The bug had already been fixed upstream.

We cloned a repo, ran they tests, it failed, and the task was to identify why it failed.

It was a tough process for me, since I've never really used Python debugging tools, so I actually had to learn during the interview, but I was able to reason well and picked things up quickly enough that I found the cause, and we had time to discuss ways it could have been fixed.

It was different. I do well during Leetcode questions, so stepping out of that framework was uncomfortable and stressful. I got an offer, but I felt like it was closer than it should have been.

Thanks for relating your experience. I'm sorry to hear that it was uncomfortable and stressful, but it sounds like you must have reacted pretty well in those circumstances to get an offer. Do you feel like the skills assessed by the interview were reflective of what you ended up doing on the job (assuming you accepted) ?

There are always going to be parts of life that are uncomfortable and stressful. This one wasn't terrible, and I appreciated a new outlook on how to assess skills. The interviewer was very understanding and we meshed well, so I don't think it came off as negative.

Were they indicative? shruggie. I mis-typed, I interviewed there, didn't work there. And I haven't used the python debugger since, but I also haven't worked on much python code.