> Interviews should be consistent with what day to day work actually looks like I'm not hiring at the level of day to day work, I'm hiring at the level of when

> Interviews should be consistent with what day to day work actually looks like I'm not hiring at the level of day to day work, I'm hiring at the level of when things go complex or bad. To give an example, I'm not going to test a coders ability to write some CRUD application. I'm testing the ability when a junior developers comes with a crazy problem, that they can find the cause and solve it. If I only test day to day work, you get these kind of developers that keep changing faulty code until it magically works. I don't want those in my team. I want developers that can figure out what is going wrong, understand it, and provide a solution. Do such things happen day to day? No. And a person that can reason his way out of things instead of trying random stuff, sure as hell can do the same day to day tasks just as well or even better.