To make it clear, these are questions for the interviewee to ask the interviewer.

They are also designed for an candidate in a job working with many other developers, and deploying primarily web-based software in an IT-heavy environment.

If you are hired as the sole software developer for a non-programming group, then most of the questions make no sense. For example, I mostly work with chemical research groups, where there is no mandatory code review as I am the only developer, and where the deployment is to install to /usr/local/bin .

Also, '100% test coverage' is a meaningless goal. It's trivial to force 100% coverage, and does that mean line or branch coverage? Coverage testing is a way to find where you need more test, but it mustn't be the end goal.