Why would it be challenging anyone's judgement? Just because it includes the word "why"?
If the mere fact of asking an open-ended question, in an interview setting, offends the interviewer, or makes them uncomfortable, to the point that they don't want to hire you, I think that's a good outcome.
Yes, sure, unless your objective is to be hired at absolutely all cost, anywhere, no matter how terrible. I know how that feels and I've been through that. But if that's the case, and you really don't care where you work, there are companies out there that will hire anyone who's even been in the same room with a computer for more than five minutes. You don't need to ask clever questions in those interviews.
And if, thank God, you're not in that situation, do you really want to work in a place where people make hiring decisions over things like these? Suppose they hire you -- sooner or later you're going to let a "why?" slip. If it's okay to do that when you're colleagues, why wouldn't it be okay to do it in an interview?
I definitely don't disagree that you should be able to come up with something more specific than "why", if only because it's likely to be more useful. But being empathetic towards someone who will otherwise feel they're being challenged because you asked them "Why are you using Yocto?" instead of "What are the constraints that made you choose Yocto, and in what context?" is unlikely to be useful IMHO.
If the mere fact of asking an open-ended question, in an interview setting, offends the interviewer, or makes them uncomfortable, to the point that they don't want to hire you, I think that's a good outcome.
Yes, sure, unless your objective is to be hired at absolutely all cost, anywhere, no matter how terrible. I know how that feels and I've been through that. But if that's the case, and you really don't care where you work, there are companies out there that will hire anyone who's even been in the same room with a computer for more than five minutes. You don't need to ask clever questions in those interviews.
And if, thank God, you're not in that situation, do you really want to work in a place where people make hiring decisions over things like these? Suppose they hire you -- sooner or later you're going to let a "why?" slip. If it's okay to do that when you're colleagues, why wouldn't it be okay to do it in an interview?
I definitely don't disagree that you should be able to come up with something more specific than "why", if only because it's likely to be more useful. But being empathetic towards someone who will otherwise feel they're being challenged because you asked them "Why are you using Yocto?" instead of "What are the constraints that made you choose Yocto, and in what context?" is unlikely to be useful IMHO.