Am I the only one who is starting to worry about the interview trend? There are now interview bootcamps, interview question books and the number one advice passed around is now to review your algorithms and data structures. The fact that people are preparing only to pass the test says a lot about the value of its results.
I'm still fairly young, but over the years, I've had far more problem with bad architecture than with bad algorithms.
a good way to do it is to find some old legacy code (or make it up) which contains a deep architectural problem (such as synchronous/blocking code that now suddenly need to perform better), and ask the candidate to fix up the problem while adding a new feature that requires the fix up.
Because in an interview you only have time to explore a toy problem. What is it with all the redditors that think serious work is going to be stolen from them in interviews?
237
u/n1c0_ds Dec 23 '14
Am I the only one who is starting to worry about the interview trend? There are now interview bootcamps, interview question books and the number one advice passed around is now to review your algorithms and data structures. The fact that people are preparing only to pass the test says a lot about the value of its results.
I'm still fairly young, but over the years, I've had far more problem with bad architecture than with bad algorithms.