I think it depends on how you respond. Coming at it with my hiring manager hat on, sometimes at the end of the day, you ask "do you have any questions for me?"

I think it depends on how you respond. Coming at it with my hiring manager hat on, sometimes at the end of the day, you ask "do you have any questions for me?" and it's obvious that the candidate has really asked all the questions of people previous to them. In that way, saying something like "I can't think of anything more right now, all the other interviewers have been so open" or whatever. Plus it's usually pretty obvious the candidates are usually tired at this point. Now at the beginning of the day, I'd expect some questions. But also, some interviewers simply don't leave enough time for this part of the interviewee, so it's really just going through the motions. Now my best interview candidate hat on, the real thing is to ask questions while the interview is going on at relevant times. For example, when they ask you about testing, maybe ask, well what frameworks do you use to test? What's your code review process? Let's review it right now. Etc. Asking stupid questions is definitely a red flag, although as long as they aren't offensive stupid questions, I usually give a pass. It's all a part of the experience, there are no hard and fast rules in hiring.