In the group between "don't qualify" and "can't afford", we have a hard time with candidates who are unable (or maybe lack the communication skills) to effectively talk about how their experience+potential are a good match for even a generic job opening.
We don't do any algorithmic/challenge screening during interviews.
A common interview fail for us is to have a candidate that can't generalize from or build on something from his/her resume. This usually comes out during "tell us about project X that you worked on" and comments from our side like "oh, that sounds like project Y here. But Y is different this way - what are your thoughts about how to handle <insert small-scoped, specific difference>?"
In the group between "don't qualify" and "can't afford", we have a hard time with candidates who are unable (or maybe lack the communication skills) to effectively talk about how their experience+potential are a good match for even a generic job opening.
We don't do any algorithmic/challenge screening during interviews.
A common interview fail for us is to have a candidate that can't generalize from or build on something from his/her resume. This usually comes out during "tell us about project X that you worked on" and comments from our side like "oh, that sounds like project Y here. But Y is different this way - what are your thoughts about how to handle <insert small-scoped, specific difference>?"