Interviews: competencies, behavioral questions and the panel

Priya Sandhu has an oral board interview booked with the Ohio State Highway Patrol for early December. She has read that the panel will ask about past experiences and how she would handle situations, and that the scores are added to the rest of her file. She has written out twenty examples from her life and work and practiced them aloud until she could recite them. In a mock interview with Boyce, she answers the first question in three minutes, fluently, with a clear situation, task, action and result. Boyce stops her. 'That was a good answer,' she says, 'to a different question.'

The question had been about a time Priya disagreed with a supervisor's decision and what she did about it. Her answer was about a time she found a fraud pattern her team had missed. It had a disagreement in it, but the disagreement was a sentence; the answer was really about her analytical skill. 'Interviewers score what you say against the competency they are asking about,' Boyce says. 'If the answer does not show that competency, it does not matter how good the story is.' This lesson is about how police interviews work and how to prepare for them without turning into a recording.

What police interviews assess

Police services have studied what makes officers successful and identified the competencies that matter most. The lists differ in wording but overlap heavily: communication, problem-solving and judgment, self-control and composure under pressure, teamwork, respect for diversity and inclusion, integrity, adaptability, service orientation and the courage to act on one's values. Ohio departments commonly use an oral board of two to five panel members, often a mix of officers, supervisors and sometimes civilians or community members, who ask the same questions of every candidate and score the answers on a rating scale. Some departments add a final interview with the chief or sheriff.

Most questions are behavioral: they ask what you did in a real past situation, on the principle that past behavior is the best predictor of future behavior. Typical openings are 'Tell us about a time when...' or 'Describe a situation in which...'. Some questions are situational, asking what you would do in a hypothetical situation, and a few are general, about your motivation, your knowledge of the service, or your understanding of the job.

The STAR structure

STAR is a simple structure for behavioral answers. Situation: briefly describe the context, including when, where and who. Task: say what you were responsible for or what needed to be done. Action: describe what you did, step by step, using 'I' rather than 'we'. Result: say how it turned out and, if relevant, what you learned. The action section should be the longest, because that is where the competency shows. A common fault is a long situation, a short action and no result.

Boyce suggests a rough timing guide for a two- to three-minute answer: about twenty seconds for the situation, ten for the task, a minute and a half for the action, and twenty seconds for the result. She also suggests choosing examples where the stakes were real, the applicant's own actions made a difference, and the outcome can be described honestly, even if it was not perfect. 'A story where it went wrong and you learned something is often better than a story where you were the hero,' she says. 'Panels have heard a lot of heroes.'

The action's share is the action time divided by the total: 55 ÷ 180 ≈ 0.31 the first time and 95 ÷ 155 ≈ 0.61 the second. The second answer was also shorter, which matters in a panel interview with a fixed number of questions. Boyce suggests a simple practice routine: record an answer on a phone, time each part, and rebuild it until the action is at least half of the answer and the whole thing fits in about two and a half minutes.

In Priya's first answer, the action was less than a third of the time. In her second, rebuilt around the question she was actually asked, it was about two thirds. The second answer described how she raised her disagreement privately with her supervisor, explained her reasoning with data, accepted the decision when it went the other way, and later saw the decision revised when new evidence emerged. It showed communication, self-control and courage of convictions, which was what the question was about.

Preparing examples

Preparation is essential, but memorizing scripts is not the goal. Boyce recommends that applicants build a bank of ten to fifteen real experiences, each written out briefly in STAR form, and then map each one to the competencies it could show. One good experience can often answer several questions, depending on which part you emphasize. During the interview, the applicant chooses the example that best fits the question asked and tells it naturally, emphasizing the competency being assessed.

Each student builds a bank. Marco's has examples from the army, including a night he talked a drunk and armed soldier into handing over a rifle, and from his job managing a warehouse shift. Jesse's comes from coaching, the summer land-based program and a time he helped search for a missing teenager at Nimkii Bay. Linh's comes almost entirely from call-taking. Amara worries that hers, from retail and volunteering, are too ordinary. Boyce disagrees. 'Dealing with an angry customer who is shouting at a sixteen-year-old cashier is exactly what we want to hear about,' she says. 'What matters is what you did, not where you were.'

Situational and motivational questions

Situational questions ask what you would do: for example, 'You see a senior officer take a wallet from a prisoner's property and put it in his pocket. What do you do?' The panel is looking for sound values and a sensible process: identify the issue, act within your role, ensure safety, follow policy, report through the proper channel and document what you saw. Panels distrust answers that are either passive ('I would mind my own business') or wildly heroic ('I would arrest him on the spot'). It is fine to think for a moment before answering.

Motivational questions, such as 'Why do you want to be a police officer?' and 'Why this service?', are asked in almost every interview, and most applicants answer them badly. Generic answers about wanting to help people or make a difference do not distinguish anyone. Strong answers are specific: what in your own experience led you here, what you know about this service and this community, and what you have already done to test the decision, such as ride-alongs and volunteer work. 'Tell us something only you could say,' Boyce advises.

Practicing without scripting

Boyce runs mock interviews for each student twice during the term. She asks questions they have not seen, scores the answers on the service's scale, and gives feedback. The students also practice with each other, with one asking questions, one answering and one timing and taking notes. Recording a practice answer on a phone and watching it back is uncomfortable but useful: most people discover that they talk faster than they thought, say 'um' more often, or never actually state the result.

She warns against over-rehearsal. Panels hear many applicants who have memorized answers from books or online forums, and those answers sound alike and rarely fit the question exactly. 'Know your stories so well that you can tell them in any order, starting from any part,' she says. 'Then listen to the question and tell the one that fits.' If no example fits perfectly, it is acceptable to say so briefly and choose the closest, or to describe what you would do and why. It is also acceptable to ask the panel to repeat a question, and to take a moment to think before answering.

On the day

Practical details make a difference. Dress as you would for any professional interview; most applicants wear a suit or equivalent. Arrive early, and be courteous to everyone you meet, including reception staff. Bring copies of anything you were asked to bring. Turn off your phone. Make eye contact with all panel members, not only the one who asked the question. Panel members will usually take notes while you speak; that is normal and not a sign that something is wrong. At the end, you will usually be asked if you have any questions. A thoughtful question about training, the community or the service's priorities shows interest; questions about pay and holidays are better saved for later.

Nerves are normal and panels expect them. Slow breathing before you go in, a glass of water, and a deliberate pause before each answer help. Marco, who has faced armed soldiers more calmly than he faced his first mock panel, finds that the tactical breathing he learned in the army works here too. 'It is the same body,' Grant tells him when he mentions it. 'It does not know the difference between a panel and a threat. You have to tell it.'

After the interview

After an interview, write down the questions you were asked and how you answered, while they are fresh. If you are unsuccessful, ask for feedback; many services will provide it, and it is the best guide to preparing for the next attempt. If you are successful, the information may help in later interviews within the same process. Either way, a brief thank-you note or email is courteous, though it will rarely change a score.

Linh asks how to talk about weaknesses, a question that comes up in many interviews. Boyce suggests choosing a real weakness that is not central to the job, explaining briefly how it has affected you, and describing specifically what you are doing about it. Linh's honest answer is that she undersells herself and tends to wait to be asked; she is working on it by volunteering to lead the shift debrief at the communications center once a week. 'That is believable,' Boyce says, 'and it shows you know yourself.'