Earlier quoted context omitted.
I came here to say basically this. I've worked at enough companies to know that their ideas of what their values are may not be accurate. Instead of asking about values, ask about behavior. No one is going to say no to "Do you value code quality?" Aking what they've done (and sacrificed) to support code quality will give you a better idea of what their relative values are. Asking about their tech ladder will get you…
I listened to a podcast recently [1] that talked about "embodied knowledge", which is basically the idea that what we know is often very different from what we think we know. The idea being that you will learn much more about someone / something if you ask questions that are anchored to a time and place rather than generic "unembodied" questions. So the first question you list "Do you value code quality?" is an "unem…
Y/N questions are not very revealing and are likely to lead to dead-ends in the conversation.
WWWWH questions reveal a specific bit of information, but can also lead to dead-ends.
Open-ended questions ("Tell me about...", "What do you think of...", etc) will foster good conversations and uncover new threads to pull. In my experience, this is by far the best way to interact with other people, whether they are interviewing you or not.
Coming up with good/relevant questions on the spot is a skill that can be difficult to master, but is extremely valuable.