The "what did you have for lunch" question strikes me as a bad idea.
If I am interviewing someone and that is their only question, it is an immediate "weirdo-flag" if it gets to the stage where we are making our minds up and aren't sure - I can imagine the feedback now: "asked a weird, pointless and irrelevant question during an important situation" is a negative thing and could be a decider. Would this person do something equally odd and inappropriate in an important client meeting for example?
If you've had a really fun, jovial and friendly conversation with the interviewer then 100% sure go for it, but I find most interviews are a bit from stilted and fraught and it does not feel that this sort of thing would be appropriate.
My favourite sort of question for this when you have no other questions is something like "What is a typically day like for you?" or "What is a day-in-the-life of this role like?" It is useful for understanding if the role really is what you think it is, and from there you can branch out to get a bit more into the details ("ah - what SCM do you use?" "oh right - how are code reviews done?" "interesting - how do you track work to be done?" "I see - is there dedicated UX people?" etc etc)
Won't always work since the person interviewing you might not be in the team/role you are applying for, but I think it shows interest in what you will actually be doing if you got the role, re-inforces that you have relevant experience (if you ask appropriate follow-up questions), and that you are curious.
If I am interviewing someone and that is their only question, it is an immediate "weirdo-flag" if it gets to the stage where we are making our minds up and aren't sure - I can imagine the feedback now: "asked a weird, pointless and irrelevant question during an important situation" is a negative thing and could be a decider. Would this person do something equally odd and inappropriate in an important client meeting for example?
If you've had a really fun, jovial and friendly conversation with the interviewer then 100% sure go for it, but I find most interviews are a bit from stilted and fraught and it does not feel that this sort of thing would be appropriate.
My favourite sort of question for this when you have no other questions is something like "What is a typically day like for you?" or "What is a day-in-the-life of this role like?" It is useful for understanding if the role really is what you think it is, and from there you can branch out to get a bit more into the details ("ah - what SCM do you use?" "oh right - how are code reviews done?" "interesting - how do you track work to be done?" "I see - is there dedicated UX people?" etc etc)
Won't always work since the person interviewing you might not be in the team/role you are applying for, but I think it shows interest in what you will actually be doing if you got the role, re-inforces that you have relevant experience (if you ask appropriate follow-up questions), and that you are curious.