Interview questions to ask candidates, by skill

Good interview questions to ask candidates are tied to the one or two skills the interview decides, and each has a note of what a strong answer shows. The questions here are grouped by skill and quoted from Hirezen’s interview plans, each with its signals: what a strong answer shows, marked Yes, Not sure or No as the candidate talks.

Updated . Written by Hirezen.

How to run one of these questions

Decide the skills before you choose a question.

Choose one or two skills.
A skill here is what an interview checks, such as system design or leadership; HR frameworks call it a competency. In Hirezen an interview can be given two skills, no more, so the rest go to other interviews.
Ask a few questions, at length.
Of the 64 hour-long plans in Hirezen’s library updated in 2026, 59 ask three to five questions across their skills. Keep the rest of the hour for follow-ups.
Mark each signal as you hear it.
Yes if the answer shows it, No if it does not, Not sure if you cannot tell yet. A Not sure is your cue for a follow-up while the candidate is still in the room.
Then recommend.
Strong No, No, Yes or Strong Yes, with no middle. Let the marks inform the recommendation rather than adding them up. If you are torn, pick the side you lean to and write down what would settle it.

Questions by skill

Three skills have a page each. Six more are on the interview rubric, with one question each.

  • Leadership

    Taking charge of a new engagement, setting a rule the team will follow, running an incident and writing the review after it.

  • Conflict resolution

    A decision people did not want, news a customer did not want to hear, a request turned down, an argument lost.

  • Decision making

    Ship, stop or wait on a losing test; a release on a partly spent error budget; a migration with one number missing.

Coding, Production judgment, Incident response, Troubleshooting from evidence, Ownership and Prioritization, on the interview rubric.

A question from each page

Leadership

The question

“Rewrite the draft's root cause, impact and action items. Which of the four items survive, what replaces the others, and what does the review say about the engineer who typed 3?”

The draft postmortem blames an engineer who typed 3 as a rate limit. A strong answer:

  • Keeps the engineer out of the root cause, and asks what made 3 look right to them and to their reviewer
  • Drops "be more careful" and "add more monitoring" as unverifiable, and replaces them with specific changes, each with an owner and a date
  • Turns "retrain the team" into a change to the tool or its output, and says what the training was standing in for

Conflict resolution

The question

“Tell me about a decision you wrote down that the people it affected did not want. What did you change because of them, and what did you refuse to change?”

A strong answer:

  • States the objections in the objectors' own terms, not as resistance to be overcome
  • Names something they changed because of an objection, and why the objection was right
  • Names something they refused to change, and how the person heard about it

Decision making

The question

“It is day nine. Ship v7, kill it, or extend the test — and tell me what decision rule you wish had been written down before the test started.”

A ranking model is losing a live test it was expected to win. A strong answer:

  • Names who owns the decision and what they agreed to before day one
  • Considers the cost of extending — users in the treatment arm are seeing a worse product — and weighs it rather than ignoring it
  • Says what they will write down for the next test, and it is a rule with numbers rather than a lesson

Behavioral and situational questions

A behavioral question asks about the candidate’s past: “Tell me about a decision you wrote down that the people it affected did not want.” A situational question hands them a problem and asks what they would do now, as each decision making question here does. The Cloud Architect design review uses both on one skill: it has the candidate answer objections to a decision in the plan’s materials, then tell a story of their own.

Questions

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.

Start from a plan

Each question links to the plan it comes from, with that plan’s other questions and their signals. In Hirezen you can use a plan for one of your roles, change its questions, and mark its signals during the interview. The free plan covers one open role and up to ten people.