Last time I was on the interviewing side I used to ask engineers something like "If you weren't interviewing me today, what would you be doing instead?" to try and get a better idea of this person's day-to-day. Or sometimes phrased as what they were doing earlier in the day / planned to do later in the day. Got some good details of the actual work being done from it, e.g. once it was just lots of bug fixing / test writing / test fixing and no new features.
On the interviewer side, I usually left 5-10 mins for such questions for them to ask me. (I always think it'd be funny if more time was scheduled for candidates to hit interviewers with their favorite "can you actually code" style questions, like is the team they're expecting to join even any good...) It's a bit disappointing when the candidate has nothing to ask, asking something is better than nothing... A type of useful question I got and used to ask as well was simply why I myself had joined the company/how long I'd been there. Sometimes you get a sort of cookie-cutter HR style answer, but sometimes you get something more revealing (in a good or bad way). Engineers tend to be (often too) honest.
On the interviewer side, I usually left 5-10 mins for such questions for them to ask me. (I always think it'd be funny if more time was scheduled for candidates to hit interviewers with their favorite "can you actually code" style questions, like is the team they're expecting to join even any good...) It's a bit disappointing when the candidate has nothing to ask, asking something is better than nothing... A type of useful question I got and used to ask as well was simply why I myself had joined the company/how long I'd been there. Sometimes you get a sort of cookie-cutter HR style answer, but sometimes you get something more revealing (in a good or bad way). Engineers tend to be (often too) honest.