9 ms·

I agree. Though, 2 algorithm problems over the phone in a notepad + 2 to 4 whiteboarding interviews onsite related to algorithm. How much is too much in your op

I agree. Though, 2 algorithm problems over the phone in a notepad + 2 to 4 whiteboarding interviews onsite related to algorithm. How much is too much in your opinion? How about replacing a binary tree problem with coding an actual mini-product? A mini web site or mini app in 2 hours onsite. How about using whiteboards to lay out architectures? Or some wire framing if you're applying for a front-end/mobile engineer? How about spending an hour chatting with a candidate about things in general rather than a question/answer type of communications?

davelnewton 10y ago
I don't do a lot of algo problems; my stuff tends to be a bit more practical, but it depends what I'm hiring for. I much prefer something like a mini-product/-app as well, and try to focus on stuff that applies to whatever I'm hiring for. High-level whiteboards are great as well. I tend towards paper for coding (as opposed to whiteboard, but it's essentially the same thing, just a little less "I'm giving a presentation"). My interviews tend to be chatty sessions with some code interstitials. I'm more interested in their thought process than their actual code, but I also need to understand how they think about code, so meta-programming, OOP options, weird languages and why. I'm rarely interested in specific technologies, although familiarity is important for rapid on-boarding. I care more about their enthusiasm, willingness and excitement to learn, how they think at a high level, and so on. A more casual conversation around a whiteboard or paper has really worked well for me, and I accept that it may not always be someone's cup of tea. Being a shy introvert myself I get that it can be nerve-wracking (and I've occasionally bombed whiteboard interviews) and I take this into account as best as I can.

9 ms·

I agree. Though, 2 algorithm problems over the phone in a notepad + 2 to 4 whiteboarding interviews onsite related to algorithm. How much is too much in your op

by bsvalley 10y ago

davelnewton 10y ago
I don't do a lot of algo problems; my stuff tends to be a bit more practical, but it depends what I'm hiring for. I much prefer something like a mini-product/-app as well, and try to focus on stuff that applies to whatever I'm hiring for. High-level whiteboards are great as well. I tend towards paper for coding (as opposed to whiteboard, but it's essentially the same thing, just a little less "I'm giving a presentation"). My interviews tend to be chatty sessions with some code interstitials. I'm more interested in their thought process than their actual code, but I also need to understand how they think about code, so meta-programming, OOP options, weird languages and why. I'm rarely interested in specific technologies, although familiarity is important for rapid on-boarding. I care more about their enthusiasm, willingness and excitement to learn, how they think at a high level, and so on. A more casual conversation around a whiteboard or paper has really worked well for me, and I accept that it may not always be someone's cup of tea. Being a shy introvert myself I get that it can be nerve-wracking (and I've occasionally bombed whiteboard interviews) and I take this into account as best as I can.