5 ms·

I interview plenty and I've moved away from technical questions and puzzles. We have a conversion, and talk about programming. I ask scenario based questions

I interview plenty and I've moved away from technical questions and puzzles. We have a conversion, and talk about programming. I ask scenario based questions and just see how they think and will solve it. i.e You have a program, it's running slow, how do you debug it. You find that the slow part has a query, how do you debug it? So you check the table, it has indexes, as a matter of fact, it has index on all 10 columns and the insert is slow as hell, what now? What's your opinion on OOP vs procedural? or OOP vs functional? Two developers come to you with various idea, idea A and B, which will you pick why? What do you think is the pros and cons of A and B? This is very revealing.

GreatPowers 10y ago
Those type of interviews have been the most enjoyable. Having to code a function to do a very specific thing while also having to come up with the algorithm with strict requirements in a half hour while the interviewer watches over your shoulder are the worst. And then having to repeat that for 4+ more interviewers just isn't worth it to me anymore. I did an interview at Fitbit where I did a phone interview with the manager who asked me algorithmic questions, then I had to write a program and make it optimized and pretty which took about a day to write, then I had to do about a 4-5 hour interview on site where I was drilled by about 8-10 different people 2 at a time to write code on a whiteboard. After all that and taking off work to do it I didn't get an offer saying my experience doesn't match up with what they are looking for. It was after that I realized I'm not going to go through all that bullshit anymore.