Earlier quoted context omitted.
“As a SWE, I seek to understand important context first, before jumping to build or code. First, I’d like to ask if you’ll guess randomly and fairly, or adversarially?” “Secondly, when significant money is involved, I make sure to verify any inputs. I’m considering the situation, not you personally, untrusted. How can I verify it, or do you want me to proceed assuming that’s verified?” Those are great questions, but…
"as you, my interviewer, are a capable SWE I assume you gave me all the context needed to solve the problem". The interviewing game of asking clarification questions is silly and should stop. In the system design portion I can understand it, but not when asked a direct technical question. It's perfectly fine to ask followup questions with added constraints or just directly say that the specification is fuzzy and need…
This is anything but a direct technical question though.
> It's perfectly fine to ask followup questions with added constraints, but having the guessing game to figure out those constraints is nonsense.
You say that. I say people being able to ask the right question is one of the most important skills to be a productive developer. So of course as an interviewer I want to know if they can do it.
I don't know how it works where you are, but we don't have a big book of perfectly defined specifications for our work. I guess if we could get one of those that would improve our productivity. But until we obtain one we will keep testing candidates on their ability to ask questions.