I joined a company that claimed to be awesome only to be laid off within the year. It's weird to think this, but the layoff was not a surprise and it was kind

I joined a company that claimed to be awesome only to be laid off within the year. It's weird to think this, but the layoff was not a surprise and it was kind of emotionally gratifying. There were a great many warning signs of impending doom screaming at me from the background suggesting either team/product failure or eventual job termination. My learnings from that last job that I will carry forward to my next interviews are: * How do you conduct test automation? * What is the standard process to manage risks for a refactor? * How would you describe the central architecture of your primary application? (I expect to hear about a few deliberate decisions, not something about a framework or obscure business logic isolation) * When a defect arises is the solution or code location expected to come from memory, as in will I be expected to memorize a significant majority of the code base? * How do you monitor for regression? * Will I be expected to regularly manually copy code from one environment to another? * How do you make determinations about performance? (I don't want to hear some nonsense about doing it one way because JavaScript, or whatever, is slow when you have measured neither approach and especially when you have no idea how one or both approaches actually work) If the employer cannot answer most of these questions there are only two options: 1) Empower you to address these concerns 2) Don't work there. I would rather change careers than be hired as a senior, treated like child, and then get punished for the result.