3 ms·

I think interviews are also a whole another can of worms for recruiting. Hiring a programmer isn't the same as hiring in many other professions; you're actually

I think interviews are also a whole another can of worms for recruiting. Hiring a programmer isn't the same as hiring in many other professions; you're actually quizzed (university style) on textbook algorithms. Granted, there needs to be a filter. However, how many algorithms does one need to memorize to be a good programmer? Is knowing how red-black trees work going to make one successful? Or is knowing how hash tables work Under the surface going to make one successful? Or is just being able to use the Hash data structure provided in Ruby good enough?

cmrdporcupine 11y ago
So has something changed or was I just 'lucky' before, because for the first 10 years of my career I almost never ran into these whiteboard/skillz-tester type of interviews. And never into a "we take your life for the day and drill you with multiple teams for hours on end, oh and also you have to point us to a very illustrious github and stackoverflow portfolio." It was usually just a phone screen, an in person, a few questions to see if you were full of shit, and then call references. Ta da!