Recently I've added some rather stupid ones, for reasons that should be obvious:
1. Describe your git branching strategy
2. Who releases software, how (is it packaged / deployed), and how often?
3. Do you have dev/test environments?
4. Do you keep configuration out of your code? How? Example: IaC.
5. Describe a typical incident. How do you find out about it, who gets the first alert, how does it get resolved and how (do?) you follow up afterwards?
6. What does the oncall rota look like? Follow the sun or (immediate end of discussion) 24h?
7. Do you have superheroes (people who have been around since forever, that everybody says "well I hope <superhero> doesn't get hit by a bus, because then we'd be really effed")?
8. What is the engineering staff turnover for the last 12 months? What about for the team I'm interviewing for?
9. What are the top challenges facing this team (and wider engineering team) right now? (Not only within their problem domain, but outside it, eg communication, coordination, outages, observability, direction)
1. Describe your git branching strategy
2. Who releases software, how (is it packaged / deployed), and how often?
3. Do you have dev/test environments?
4. Do you keep configuration out of your code? How? Example: IaC.
5. Describe a typical incident. How do you find out about it, who gets the first alert, how does it get resolved and how (do?) you follow up afterwards?
6. What does the oncall rota look like? Follow the sun or (immediate end of discussion) 24h?
7. Do you have superheroes (people who have been around since forever, that everybody says "well I hope <superhero> doesn't get hit by a bus, because then we'd be really effed")?
8. What is the engineering staff turnover for the last 12 months? What about for the team I'm interviewing for?
9. What are the top challenges facing this team (and wider engineering team) right now? (Not only within their problem domain, but outside it, eg communication, coordination, outages, observability, direction)