List of questions to ask in job interviews

gistfile1.txt

Note that it should be clear who my team leader would be, and lots of these questions should be directed to them.
Also preface that lots of these seem obvious and possibly insulting. For example I wouldn't think to ask a software company whether they have a bug tracker-- Until I started working for a company and discovered they don't have a bug tracker.
Code-wise: (Need to add lots more to this!)
 - Take any from Joel's list.
 - Take any from https://github.com/viraptor/reverse-interview and https://news.ycombinator.com/item?id=20916749
 - One-step build.
 - There's a bug tracker I can open a ticket for everyone.
 - When people get tagged or assigned on tickets, they get notified and actually see it without me having to manually notify them.
 - Email doesn't get spammed too much, can live without filters.
 - Recent versions of Python and any packages.
 - Ask about assignments I'll get.
 - Project is hopefully starting with me.
 - Programmers write their own tests.
 - Are there errors in the log that we ignore?
 - Is the company currently in crunch time / emergency mode? How long has it been in crunch time?
 - When a user accesses the site and has a 500 error, what happens? (Do people get notified? Is a ticket created, manually or automatically? Do we see the stack with local variables?)
 Third-party packages:
   - Is adding packages easy?
   - Will I be allowed to add python_toolbox?
 Repos:
    - Git.
    - Mono-repo? (Differentiate the case of separate repos for non-server stuff)
    - Did you ever need to get two or more PRs merged that were part of the same change? Did you have to merge them at the same time? 
 CI:
    - Maintained by what team?
    - When fails, do I need to search the log or do I get just the error?
    - How long does it take to run?
    - Let's say a developer runs the CI on his PR and it fails. Would they sometimes try to just run it again and it works? Is this done often, at all?
    - If a CI run is successful, and I'll look at the full log, will I see any exceptions / errors / tracebacks? 2-3 or more?
 Security:
    - Is there a security contact email, easily available on the site and reaching straight to the security team?
    - Is there a process for handling security problems? i.e., when a vulnerability is found, is it fixed, or is there an investigation into the chain of mistakes that caused it? 
  
General:
    Startup / small company
    Fun office
    Ask to see the office I'll be in, hopefully not open space
    Document saying open-source projects done outside of company time and without company equipment are mine
    Need to be on call?