> offload all the stress and frustration onto you Man! I can feel you. However, after these years, I've learned how to be a polite dick: You don't have to wait

> offload all the stress and frustration onto you Man! I can feel you. However, after these years, I've learned how to be a polite dick: You don't have to wait until they allow you to, job interview is a negotiation, not an interrogation. If you feel abused during an interview, give them an one star on Glass Door and try another company. My strategy go like this: Whenever there is a chance to insert, I will start by asking which version control (or other quality management tool) they are using, followed by the detail of their CI/TDD/release/deploy system and code-reviewing tool, and then the code-reviewing and QA process, and then how they distribute responsibility and reward and so on. In the real world, it sound like: "Oh, You guys using Git? Nice. So, do the team also use CI, such as Jenkins? ..... How you test your code? ..... So what's the code review tool the team is using?". Always sound positive, casual, cute and all while professional, like you just met the child of your middle school crush taking by his dad to your clinic for a flu shot. Control your emotion like an airplane lieutenant telling others "everything will be fine" while the airplane is crashing into the ground at supersonic speed. If they can't produce an appropriate answer, maybe there isn't one[0]. I personally take it as a red flag, and will raise my caution when answering their question from the point and on. Of course, you have to ask the question to the right person. Negotiation itself is a skill. [0] You know, even if they don't have one, the correct and professional answer should be like "Oh, we don't have that right now. We would like to build one if it is necessary for us. [Do you like to share more information about it?|Do you like to build one with us?]"