I think most of these questions are basically asking the same thing: how bureaucratic is this organisation? Which is not something you can ask directly, so thes

I think most of these questions are basically asking the same thing: how bureaucratic is this organisation? Which is not something you can ask directly, so these proxy questions are a good idea. For example, I laugh at the crap my SO has to go through at their (larger) employer for simple things. The "fixing a typo in a log file" question is especially apt: it's essentially impossible for my SO because they're only supposed to work with the software as provided, despite being programmers themselves (they do scripting to add functionality to the software using a custom language, to adapt to customer's needs). My SO would have to answer something involving navigating multiple levels of management in another country. For my own employer, I would answer "the process is git clone, git commit, git push. You can ask someone for feedback on your typo fix if you want I guess?" I'd never think of asking such a simple but effective question. But then there is "Does this team or any of the related teams have a person who actively rejects proposals to improve the code base?" Huh? What do you expect anyone to answer to this, "oh yes we have Steve, he's a real asshole and continuously rejects the best of ideas for no apparent reason"? The author even lists it as "Out of all the questions in this list, this one is the most crucial." I can understand that the author had a bad experience having to work with someone like that, but the odds of getting a real answer here are negligible, especially compared to the odds of the interviewer thinking worse of you for asking to throw someone under the bus before you're even hired. Would not recommend asking this 'most crucial' of questions.