If I may opine, and while I agree with some of the highlights of the article, here's a few things that I've observed from my years in the field, and of multiple interviews that I went through and conducted:

1. Know who your audience is - some of the professionals conducting the interview may not be Designers. Understanding who's asking the questions also allows for the candidate to pose questions that better align with the people they're talking to (be it Product Owners, Development Leads, Go To Market Professionals).

2. Asking about the Design Process itself - this allows to uncover the type of approach, structuring of the teams, KPIs establishment, deliverability/implementation, to name but a few aspects of how that Organization and group works. Asking granularly about Research is important, but can be part of the conversation about how Designers and Researchers are organized and collaborate with each other.

3. The ratio question - that can go either way, since at times teams have contractors and vendors to help them out in dispersing the workload. The question should focus more on how Design/Product and Development collaborate, and how Agile the process actually is.

4. Feature Release - while that is an interesting question, every organization has a unique process. I've worked for companies with continuous delivery and others who took time to get to market. They both had their challenges, much like any other. The point is: this can be a barometer to better understand how an Organization works, and not necessarily a "red flag" to something that is wrongly being implemented.

Ultimately, I'd say preparing for the interview, demonstrating interest in the organization and in the interviewers themselves makes all the difference.