In this article
Before you start
For the wider picture, see the interview process: stages, rounds and who scores what.
Why interviewers ask this
A conversation that wanders gives a hiring team little to compare, so many employers replace it with fixed questions and fixed scoring. The U.S. Office of Personnel Management (OPM) reports in its 2008 guide that unstructured interviews show low reliability (consistency between interviewers) and low-to-moderate validity (how well the method measures job performance). Structured interviews, it says, show a high degree of both, plus legal defensibility. A 2023 review of selection research revisits the validity evidence for widely used hiring methods, so the OPM figures are a starting point, not the last word.
So the interviewer is collecting comparable evidence, not judging charm. A weak answer states a trait: "I am a good communicator." A strong answer tells one episode in which you did something, with a result. The OPM guide is old, so check how your own employer runs its rounds.
Interview skills from first principles
- Competency
- A competency is a job-related skill or behavior, such as oral communication or interpersonal skills, that an interviewer chooses in advance and scores your answers against, instead of forming a general impression of you. A hiring team picks a short list of them for each role, and each question is written to draw out evidence of one.
In plain words
Think of a driving test. The examiner does not ask whether you are a good driver. She has a checklist and watches you park, merge and brake. An interview works the same way: a short list of skills, each judged on what you show.
The analogy breaks in one place. The examiner sees you drive. An interviewer only hears you describe the past. So the detail in your story is your evidence. Specific details such as names, dates and numbers let the interviewer check that the episode really happened.
In one precise sentence: interview skills are the behaviors in your spoken account that give the interviewer evidence of the few competencies the employer chose for the job.
The interview skills interviewers notice
The core interview skills are preparing, listening, structuring, speaking concisely, asking questions and following up, and each shows up in a visible way. Preparing shows when your examples connect to the role and the employer's work. Listening shows when you answer the question that was asked and, if it is unclear, ask a short clarifying question first. Structuring shows when your answer has an order, such as the STAR method.
Speaking concisely shows when you reach your action quickly and stop after the result. Asking questions shows when you ask about the work, the team or how success is measured, rather than something a web search answers. Following up shows in a prompt, specific thank-you message and in how you handle a probing question in the room. These skills are the means; the competencies in the next step are what the interviewer scores through them.
Step 1: The question points to a competency
Every question is a probe for a competency. OPM says a structured interview typically assesses between four and six competencies, and names Oral Communication and Interpersonal Skills as well suited to an interview.
A behavioral question is a question about something you did in the past, such as "tell me about a time you disagreed with a teammate." OPM's premise is that past behavior in similar circumstances is the best predictor of future behavior. A situational question is a question that describes a hypothetical scenario and asks what you would do. Its premise is that stated intentions track real behavior.
Input: the question. Output: the competency to evidence. Before answering, name that competency to yourself. A leadership question and a conflict question are both competency questions. You now know what the interviewer listens for; the next step is the evidence.
Step 2: Your answer supplies evidence
Your answer is the evidence for that competency. Use the STAR method to keep it short and ordered. Give the situation and task in two sentences, the action in the longest part, and the result last. As a common guideline, not a rule from the OPM guide, aim for an answer you can say in one to two minutes.
Input: the competency. Output: one spoken episode with a visible action and outcome. The action is the part the interviewer can score. Say "I" for what you did and "we" only for what the team did. Name a real result and, where you can, what you would change.
OPM tells interviewers that taking regular, detailed notes of observable behaviors and verbal responses during each interview is crucial. Your answer should therefore contain things worth writing down: a decision, a message you sent, a trade-off you weighed. Two video-round questions have their own pages: are video interviews assessed by AI and looking at notes in a video interview.
Step 3: The interviewer scores your answer on a common scale
The interviewer turns the notes into a score on a rating scale shared by every candidate. OPM says all candidates are evaluated with a common scale, and interviewers are trained on rating biases, for example giving higher ratings to candidates who seem similar to them.
This is where the hook pays off. The notes record what you said you did. A sentence such as "we decided to roll back" leaves the scorer nothing to attribute to you, so the rating drops even when the story is good. "I proposed the rollback, wrote the message to the customers and checked the metrics the next morning" gives three observable actions.
Rating scales vary by employer. The scale used below is illustrative, not OPM's. You now have the full mechanism, shown in the figure.
Step-by-step description
- The question points to a competency.
- Your answer supplies evidence.
- The interviewer scores it on a common scale.
- A question points to a competency.
- Your answer supplies evidence of that competency.
- The interviewer scores the evidence on a common scale.
Knowing it is half the job. Saying it is the other half.
Interview Clozo is an AI interview copilot for real interview rounds: it hears the question and puts a strong answer on your screen, and you say it in your own words. See the features or how it works.
Start Free Trial →The Staff-level answer
The sample answer below is illustrative and answers a common prompt: "Tell me about a time you explained a hard technical problem to someone who was not technical." It is a composite, not a real person's story.
Tell me about a time you explained a hard technical problem to a non-technical colleague.
Our checkout page kept timing out, and the product manager needed to decide whether to delay a launch. I skipped the architecture and drew one picture: a queue of customers and one slow cashier. I said what was certain, that the database was the bottleneck, and what was not, how long a fix would take. I gave two options with their costs. She chose to delay by a week, and I sent a short written summary the same day. Afterwards I added a one-line status to our incident template so the next explanation starts from that picture.
What makes it Staff-level is the last two moves: it states uncertainty and a trade-off, and it changes how the team works afterwards. Staff is the most senior level in this page's third column, a term from engineering career ladders; in other fields, read it as the answer a very senior person would give.
The rubric
| Dimension | Weak answer | Strong answer | Staff answer |
|---|---|---|---|
| Specificity | A general trait or opinion | One real episode with context | The episode plus why it was hard |
| Own contribution | "We did it" | "I did" with named actions | Actions plus how you led others |
| Result | None, or vague | A stated outcome | Outcome, cost and what you changed |
| Communication | Rambling, no order | Clear order, one to two minutes | Plain words, uncertainty named |
| Follow-up readiness | Stalls on a probe | Answers one level deeper | Names alternatives you rejected |
To see the effect of that difference, the script scores two answers on four criteria (situation, own action, result and reflection), a simplified cut of the five rubric dimensions, on an illustrative 5-point scale. The weak answer scores 3, 2, 2 and 1; the strong answer scores 4, 4, 5 and 4.1 The weak answer averages 2.0 and the strong answer averages 4.25 on the illustrative scale. The strong answer leads most on the result, because weak answers often stop before saying what happened.
Text description of the diagram
- The weak answer averages 2.0 and the strong answer averages 4.25 on the illustrative scale.
- The strong answer leads most on the result.
Three variants of this question
Leadership skills interview questions: tell me about a time you led
Leadership skills interview questions are competency questions: the interviewer wants a specific time you set direction, made a call or brought others along, with your own action in the middle. A title is not needed; leading a small fix counts. Four common prompts reported by candidates, in our own words, and what the interviewer listens for:
- Leading without authority: "Tell me about a time you got people to follow your plan when you were not their manager." The interviewer listens for how you built agreement and what you personally did.
- A disputed decision: "Describe a decision your team disagreed with." The interviewer listens for how you heard the objections, how you decided and how you kept the relationship.
- Developing someone: "Tell me about a time you helped a colleague grow." The interviewer listens for a specific need you noticed, the support you gave and a change you can point to.
- Owning a failure: "Tell me about a time something you led went wrong." The interviewer listens for plain ownership, the cause and what changed afterward.
An illustrative STAR outline for the first prompt (a composite, not a real person's story): the situation and task are a shared service that kept failing, with no owner, used by several teams I did not manage. My action was to write a one-page proposal listing the failures, ask each team for one objection, change the plan for two of them and run the first fix myself. The result was that the teams adopted the plan and the failures stopped recurring; next time I would involve the teams earlier. For the technical version of these questions, see the project deep dive.
What would you do if an angry client says a check never arrived?
The angry-client prompt is a situational question; OPM's guide uses a prompt of this kind, where a client says an overdue check, reportedly mailed five days earlier, has not arrived. A strong answer states steps in order: listen, check the facts, act, then follow up.
How do you explain your work to someone non-technical?
Engineers get this as a communication skills question. Pick one real episode, give the listener one concrete picture, say what is certain and what is not, and finish with the decision that followed.
Common mistakes
- "We shipped it and it went well." (wrong) The scorer cannot attribute anything to you. (right) "I wrote the migration plan and ran the rollout."
- "I would usually talk to the team first." (wrong) A hypothetical answer to a behavioral question gives no evidence. (right) "Last year I talked to the team first, and here is what happened."
- "I'm a natural leader." (wrong) A trait is a claim, not evidence. (right) Tell the episode and let the action show the trait.
- A long setup, then "it worked out." (wrong) The result is the cheapest thing to add. (right) State the outcome and one thing you would change.
Follow-up questions
Are behavioral and situational questions the same?
No. A behavioral question asks about the past and a situational question asks what you would do in a described scenario, and OPM gives them different premises. Answer the first with a real episode and the second with ordered steps.
How long should an interview answer be?
As a general guideline, a strong answer takes one to two minutes to say, with the action as the longest part. The interviewer can then ask a follow-up, and the staff follow-up shows how deep those go.
What do interviewers look for in leadership skills interview questions?
They look for four things: setting direction without relying on a title, handling disagreement, developing other people and taking responsibility when something fails. The interviewer scores the specific actions you describe, not the word "leader", so answer each with one episode, your own action and a result.
Are communication skills scored in a technical interview?
Yes, in many structured technical rounds, as reported by candidates, though no single published rule covers every employer. A clear structure and stated trade-offs are typically rewarded alongside correctness, and OPM names Oral Communication as a competency well suited to interviews. For how technical and spoken skills mix, see forward deployed and applied AI engineer rounds and AI engineer interview questions.
What are the most important interview skills?
The most important interview skills are listening to the question, structuring an answer around one real episode, speaking concisely and asking good questions about the role. Preparation underpins all four, because it tells you which episodes fit the job.
- Interview skills are how you give evidence in the room: preparing, listening, structuring, speaking concisely and asking questions.
- Interviewers score a few job-based competencies from that evidence.
- Name the competency a question tests before you answer.
- Tell one specific episode, with your own action in the middle and a result at the end.
- Behavioral questions ask about the past; situational questions ask what you would do.
- Notes record what you said you did, so "I" statements carry the score.
Sources
- Structured Interviews: A Practical Guide — U.S. Office of Personnel Management, 1 Sep 2008
- Revisiting the design of selection systems in light of new findings regarding the validity of widely used predictors — Industrial and Organizational Psychology (Cambridge University Press), 1 Apr 2023
