Search code, repositories, users, issues, pull requests...
This is a big collection of questions I've gathered over the years that have proven to be useful when interviewing, including why you might want to ask the question. Remember, in any interview you're trying to get to know the company and the people you might be working with as much as they're trying to get to know you. Maybe more.
There are a lot of questions here. Some are just simple nuts-and-bolts questions. Some are only appropriate for certain types of companies. Some might help after you've already got a whiff of an org smell. You'll never ask all of these -- there's no time! But usually, after you've read the role description and had a phone screen, you should have a pretty good idea of which questions you want to highlight and ask.
What is the onboarding process like? Do they have one? How well-defined is it? Do they have a "buddy system" or some other mechanisms to help you get ramped up, or do they just let you sink or swim?
In the first 60 to 90 days of employment, what would be my most urgent priorities? This is helpful for getting past the position description to the real expectations of the work. Plus the first 90 days are critical.
