- What are good interview questions to ask candidates?
- Ones written for the skill the interview decides, with the signals of a strong answer listed under them before anyone is interviewed. “Tell me about a decision you wrote down that the people it affected did not want” is one. Its plan lists what to listen for, such as the objection in the objector’s own words and one thing the candidate refused to change.
- How many questions should you ask in an hour-long interview?
- Three to five, across one or two skills. Of the 64 hour-long plans in Hirezen’s library updated in 2026, 59 ask three to five questions, and four is the most common count. The rest of the hour goes to follow-ups on what the candidate did themselves, until each signal under a question can be marked.
- Should every candidate get the same questions?
- Yes, the same questions with the same signals, so you can compare one candidate’s answer with another’s. Follow-ups differ, because each one chases what that candidate said. If a question needs changing, change it for every candidate still to come.
- What is a signal in an interview?
- One thing a strong answer shows, written under the question before anyone is interviewed, such as “Names something they refused to change, and how the person heard about it.” The interviewer marks it Yes, No or Not sure while the candidate talks. A signal names something you can hear in an answer, which a phrase like “good communicator” does not.
- Where do these questions come from?
- Each question and signal is quoted word for word from an interview plan published on hirezen.io, and links to it. The grouping by skill is Hirezen’s; each plan lists the skills it was written for on its own page. Some questions mention a system or a number from their plan’s materials, and a line above those explains the setup. The Yes, Not sure and No examples are written for these pages.