2 ms·
Love how he goes, he does not like tricky questions and first thing he describes is a trick hidden in the question designed specifically to fool candidates. Ye
by ozim 3y ago
Love how he goes, he does not like tricky questions and first thing he describes is a trick hidden in the question designed specifically to fool candidates.
Yet he still thinks it is not a tricky question.
But great article and I learned something from it.
- twelve40 3y agobut this "trick" tests for something very real: many times i've seen people around me mindlessly jump to coding a PM-written ticket without clarifying important details or even doing a basic sanity check on the feature. The end result is often a disaster for both parties, and should be avoided with a bit of thought upfront. It's not like anyone is lying or misleading here, such details get omitted all the time in real life but you need to collect them for a proper implementation.
- ozim 3y agoI don't think solution for that is dropping perfectly capable people on the interview. There should be process for clarifying tickets with the team because you don't just drop tickets on developers "out of nowhere" and expect them to ask questions especially if company culture is "drop the ticket on dev let him figure this out". Someone has to either make ticket written in detail so you can drop it on dev without dev needing to ask questions OR make refinement where you get team to ask questions to have input from multiple people because single person is not able to understand all the details of the system.