You past the gauntlet, having nailed every single question your interviewer threw at you, and now the interviewer asks if you have any questions for him or her. Still recovering from the ordeal, your mind draws a big blank. You blurt out something incoherent about benefits and their mission. Before you get yourself into this situation, just as with coding questions, it is helpful to be prepared to interview your interviewer. Though we never can be sure of the outcome of interview, organized interviewers will leave time for you to ask questions about the company, nature of the work, and their experience. It is important that you make the best of this opportunity to show your sincere interest and to learn more about the company and team to determine if it is a right fit and what to expect. Of course, given this is a team member or even the supervisor, you may have to take what they say with a grain of salt, but asking some well thought out questions can help tease out what the work and environment is really like.
Pace of WorkRelease schedules vary from company to company. With so much of software moving to a service model with delivery on the web, release cycles have shortened dramatically for some companies. On the one extreme, you have companies which release multiple times a day and you will want to learn if they expect you to release multiple times a day once you settle it. The pace of releasing multiple times a day is quite different from a traditional annual release schedule. Sometimes you can learn about a company's release schedule from their website, but sometimes you have to ask. The matter is complicated some more if there are internal team dependencies. For example, a software team may be expected to pass their work to a QA team every few weeks.
Some teams have daily standup meetings where everyone needs to show up and report progress. On the other extreme, some teams rarely loop in their developers into meetings. There are pros and cons for both. You'll learn what you are both comfortable with eventually, but do note the differences in team cultures in terms of pace.