The PAR Method: How to Answer Behavioral Questions (+ Examples)

PAR stands for Problem, Action, Result. It's a way of organizing a true story from your working life so an interviewer can follow it in about a minute and write down something concrete afterward.

Use it whenever a question asks for a past event rather than an opinion. The signals are:

• "Tell me about a time when…"
• "Describe a situation where…"
• "Give me an example of…"
• "Walk me through a time you…"
• "When have you had to…"
• "How did you handle…"
• "What's the most difficult _____ you've dealt with?"

Anything in the past tense asking for one specific occasion is a behavioral question, and the interviewer wants a story, not a policy statement.

How formal this gets varies by employer and by place. Large companies, hospital systems, and public-sector hiring in many US states — and standard practice in Canada, the UK, and Australia — often use structured interviews where every candidate hears the same questions and answers are scored against a published competency list. A ten-person business may never use the word "behavioral" and still expect the same thing. Read the job posting for the competencies it names, and build your stories against those.

The single biggest fix most people need is pronouns. Interviewers hear "we rolled it back," "we decided," "we got it done" and have no way to score it, because a team result tells them nothing about you. Say "I" for the things you did and "we" only for genuinely shared work — "the team ran the migration; I wrote the rollback script and made the call to use it." You will not sound arrogant. You will sound specific.

End on something measurable wherever you can: a percentage, a count, a time saved, a renewal, an error rate. When the work genuinely doesn't produce numbers — much of care work, teaching, legal, and creative work doesn't, at least not quickly — use a proxy the interviewer can still picture: the complaint never recurred, the client renewed, the process you wrote is still in use, your manager asked you to train others on it. A vague ending ("so it worked out well") throws away the part of the answer that earns points.

The question: "Tell me about a time you fixed a process that wasn't working." The competency being tested is process improvement — can you find a root cause and change how the work is done, rather than just working harder around the problem? This answer belongs to a logistics coordinator at a regional food distributor with three warehouses.

Logistics coordinator, regional food distributor — process improvement

Problem: Last spring our afternoon outbound loads were leaving an average of 50 minutes late, which pushed deliveries past the receiving windows at two of our biggest grocery accounts. One of them had already sent a written warning about rejected deliveries. I owned the dispatch schedule for that shift.

Action: I spent four days timing the dock myself instead of asking people why they were late, because I wanted the sequence, not the excuses. The delay wasn't loading — it was that pick tickets for the afternoon run were printing after the morning run closed out, so pickers sat idle for about forty minutes. I took that to the warehouse manager with the timings written out, and proposed printing the afternoon tickets at 6 a.m. with the morning batch. He was worried about pickers grabbing the wrong tickets, so I color-coded the two batches and ran it as a two-week trial on one dock before we changed anything company-wide.

Result: Average departure moved from 50 minutes late to 8 minutes early. We had no rejected deliveries at either grocery account for the rest of the year, and the color-coded print batches are now standard at all three warehouses.

Notice the proportions. The problem takes three sentences and names a stake someone outside the company cared about. The action is the longest stretch and shows judgment — timing the dock rather than interviewing people, piloting before scaling, handling the manager's objection. The result lands one number and one thing that outlasted the project.

These are written the way you'd actually say them, without the labels spoken out loud. Read one aloud and time it — each lands between fifty and seventy seconds.

"Tell me about a time you escalated a concern about patient safety."

The competency is clinical judgment combined with willingness to escalate through hierarchy.

Charge nurse, night shift, 32-bed surgical unit

About six months into the role I had a post-op patient whose blood pressure was drifting down over two hours, and the on-call resident had already told me twice it was nothing. I rechecked the vitals myself, pulled the last two sets of labs, and wrote down exactly what had changed since my first call: pressure down, urine output down, dressing damp. I called him back with those three facts in that order and asked directly for a bedside assessment. When he hadn't come in fifteen minutes, I used the chain of command and paged the attending, and I told my manager I'd done it before I left that morning rather than letting her hear it secondhand. The patient went back to the OR that night for a bleed. My manager used the call in escalation training on the unit, and we added a "what has changed" line to the handoff sheet.

Why it works: the result outlasts the shift, and the action shows she escalated by protocol and documented it, rather than going around a colleague on instinct.

"Tell me about a time you shipped something that broke in production."

The competency is ownership under pressure — whether you surface your own errors fast or wait to be found out.

Backend engineer, 12-person product team, subscription software company

We pushed a billing change on a Thursday and by Friday morning support had forty tickets from customers charged twice. I'd written the migration, so I said that in the incident channel immediately instead of waiting for the post-mortem. I rolled the deploy back within twenty minutes, then wrote a query to pull every affected account rather than trusting the ticket count — that found 212 customers, about five times what support had seen. I drafted the refund list, got finance to approve it in one call, and gave support a plain-English line they could paste into replies. Over the weekend I added a dry-run step and an invoice-count assertion to the billing pipeline so this class of bug can't ship silently. We've run eleven billing migrations since and none has needed a rollback.

Why it works: he names his own mistake in the first fifteen seconds, and the result is a permanent guardrail, not just a cleanup.

"Describe a time you dealt with an underperforming team member."

The competency is performance management — can you give direct feedback without either avoiding it or blowing it up?

Store manager, 40-person big-box retail location

One of my department leads had been missing truck-unload targets for about two months and the team had quietly started working around him. I pulled the unload times before I said anything, then asked him to walk the back room with me on a Tuesday morning. He told me he'd been covering two departments since a resignation and was starting the unload an hour late on every delivery. I rebalanced the opening schedule so he had two extra people for the first hour, set a fifteen-minute weekly check-in with three specific targets, and wrote down what we'd agreed so neither of us had to remember it. I also told him plainly that unload time would be part of his review. Within six weeks he was inside target four weeks running, and I rolled the same check-in format out to the other two department leads.

Why it works: she separates the performance problem from its cause, still holds the line on expectations, and the result covers both the person and the practice.

"Give me an example of adapting instruction for a student who was struggling."

The competency is differentiation driven by evidence rather than guesswork.

Seventh-grade math teacher, public middle school

I had a student who'd passed sixth grade but was failing every unit test on fractions. Rather than re-teaching the whole unit, I sorted her last four quizzes by question type and found she could run the procedure fine and lost almost all her points on multi-step word problems with units. I gave her a two-week routine: five minutes at the start of class underlining what the question actually asked for, then one worked problem she explained back to me in her own words. I asked her English teacher what reading supports she was already using so we weren't pulling in different directions, and I called home once a week with one specific thing she'd done well. She went from a 48 to a 79 on the end-of-unit assessment and passed the state test in spring. I now run the underlining routine with the whole class on word-problem days.

Why it works: the action starts with diagnosis, not effort, and the result shows the fix scaled beyond one student.

"Walk me through a time you caught an error others had missed."

The competency is attention to detail paired with the nerve to raise it.

Staff accountant, 200-employee manufacturer

During month-end close I noticed freight expense running about 18% above the prior three months with no change in shipment volume. The easy move was to book it and flag it in the variance notes. Instead I pulled the carrier invoices for the month and matched them line by line against our contracted rate schedule, which took most of a Saturday. Two accessorial charges had been applied to every shipment out of one terminal since the contract renewal — a setup error on the carrier's side, not ours. I wrote it up with the invoice numbers attached and took it to the controller rather than calling the carrier myself, because the relationship sat with her. She used it in the quarterly carrier review. We recovered roughly $34,000 in credits, and a rate-schedule spot check is now a standing step on our close checklist.

Why it works: he names the shortcut he didn't take, respects who owned the relationship, and ends with both a number and a permanent control.

"Tell me about a time you improved safety or reduced downtime."

The competency is structured problem-solving on the floor, including getting operators on board.

Maintenance supervisor, two-line packaging plant

Our filler line was stopping four or five times a shift for short jams, and because each stop was under two minutes nobody was logging them — they didn't show up in the downtime report at all. I asked the operators to put a tally mark on a clipboard every time it stopped for one week, with no blame attached and no names on the sheet. The tally came back at 61 stops, and three-quarters traced to one infeed guide that shifted once the belt ran warm. I priced a shim-and-bracket fix at under a hundred dollars in parts, scheduled it into a planned shutdown so we lost no production, and had the operators sign off on the change before we ran it. Short stops dropped to about one a shift and line output went up roughly 6% with no extra labor. That clipboard tally is now how we open every downtime investigation on the line.

Why it works: the action shows him making an invisible problem visible first, and the cheapness of the fix makes the thinking the star of the answer.

"Tell me about a time you turned around an angry guest."

The competency is service recovery under pressure, including protecting your own staff.

Front office supervisor, 180-room airport hotel

A flight crew arrived at one in the morning to find we'd oversold and two of their rooms were gone — and they were back on duty at six. The captain was shouting at my night auditor in the middle of the lobby. I moved the conversation to the far end of the desk, told him plainly what we'd gotten wrong instead of blaming the system, and gave him the one thing I could actually promise: rooms at our sister property eight minutes away, a van within fifteen minutes, and both nights comped. I called the other hotel standing right there so he could hear it happen. Then I emailed the airline's account manager before I left at seven, so she heard it from us first rather than from her crew. The contract renewed that quarter, and we changed our overbooking rule so crew blocks are never walked.

Why it works: she gets her colleague out of the line of fire, over-communicates upward before being asked, and the result is a retained account plus a rule change.

Most interviews draw from the same small set of competencies. Write six to eight PAR stories and you'll cover the majority of what you get asked — each story can usually answer two or three different questions depending on which part you emphasize.

For each one, write three bullet points — not a script. One for the problem, three or four verbs for the action, one line for the result with the number in it. Keep the bank in a single document and reread it the morning of an interview. Then add the two or three questions that only your field asks, which you can usually pull straight out of the job posting's responsibilities section: a nurse gets asked about escalation and end-of-life conversations, an engineer about production incidents and code review disagreements, a teacher about parent conflict and differentiation, a salesperson about a deal that died.

• Spending ninety seconds on setup. You start with the company history, the org chart, and who reported to whom, and the interviewer's attention is gone before you've done anything. Fix: hold the problem to three sentences — when, what was going wrong, what was at stake — then move.

• Hiding behind "we." Every verb belongs to the team, so there's nothing on the page to score. Fix: go through your stories and change every action you personally took to "I," out loud, until it stops feeling strange.

• Trailing off instead of landing a result. The answer ends on "…and yeah, it ended up being fine," and the strongest fifteen seconds of the answer never happens. Fix: write the last sentence of each story in advance, with a number, a time frame, or something that's still in use today.

• Answering in general terms rather than about one occasion. "What I usually do in that situation is make sure everyone's aligned…" is a hypothetical, and structured interviewers are instructed to score it as a non-answer. Fix: anchor the first sentence to a specific time and place — "Last March, on the night shift…" — which forces the rest into past tense.

• Telling a well-rehearsed story that doesn't match the question asked. You hear a keyword, reach for your favorite story, and answer a conflict question with a time-management example. Fix: before you start talking, say the competency to yourself — "this is about conflict" — and pick accordingly; it's fine to take three seconds of silence to choose.