"They eat large sprawling problems for breakfast, but they balk at 45-min algorithm challenges." Care to guess what we're looking for in screens and interviews

"They eat large sprawling problems for breakfast, but they balk at 45-min algorithm challenges." Care to guess what we're looking for in screens and interviews? Some of our best performers were poor interviewers. Likewise, we've had interview aces not pan out. Rather than expecting the world to become interview clones (and make our hiring decisions even more difficult), we're learning how to be better interpreters of people to get to the answer of our real question -- is this person an engineer we'd like to have on our team? It's still a work-in-progress and we're nowhere near perfect, but we're simply not going to outsource our decision-making to the status quo of technical interviewing in 2016.