3 ms·
I'm going to politely disagree on some points: Consider this scenario, your company will never need an algorithm designer. The jobs they need are to do basical
by bane 14y ago
I'm going to politely disagree on some points:
Consider this scenario, your company will never need an algorithm designer. The jobs they need are to do basically glorified component integration. You have a candidate who is awesome at gluing together various libraries and other odds and ends into a working product. The things he's worked on are well known and well regarded, and he has 15 years out of college doing these things. He's never even had to think about the complexity of a red-black tree in all that time let alone implement one. He's solid, a great team lead, personable without any difficult to handle "quirks". He's been the core to the success of several products. In other words, he's the perfect match.
So why filter him out by testing how much of an algorithm encyclopedia he is? It'd be like interviewing an algorithm guy by asking him how well he knows some web framework. At best it's non sequitur, at worst you won't get the employee you need.
>Notice that big tech companies have stopped with the "brainteaser" style questions like how many potholes in Manhattan
My understanding is that they did this due to a number of lawsuits. The courts felt that it presented a discriminating playfield, and most large companies have stopped this due to recommendations form their legal departments.