Works for non-software engineers too. Filters out if they've done any research at all into our work and if they're curious.
Works for non-software engineers too. Filters out if they've done any research at all into our work and if they're curious.
A lot of time I ask hard questions like what is the company's revenue model or the company's growth strategy, where do you see the company in 5 years? That can scare a senior developer... then they get angry with me because I have turned the tables and made the person think in a non-binary way.
What if they prepared with specific questions but you answered them during the interview?
What if a previous interviewer answered their outstanding questions?
Is curiosity about the company the trait you want to optimize for? In other words, does that curiosity translate to job performance?
I also think this question being so open ended and vague will lead you to get a lot of bad/blank answers. What should I be asking questions about?
And, as you might expect, people do tend to put the answers to the common questions in the job description.
Ask questions that aren't easy to find out without asking current employees, and that don't put employees on the spot. I can do that for hours.
With execs, questions turn more to product roadmaps, marketplace fit, revenues and budgeting, but again, I bet I can come up with interesting and practical questions longer than any slot any interviewer has in their calendar.
It's possible that the recruiter was expecting questions like the above, and saw your reasonable confidence as either over-confidence, incuriosity, or both.