“Tell me about a time you handled a difficult coworker” is not an invitation to describe your conflict-resolution philosophy. The interviewer wants one incident: what was difficult, what you did, and what happened next.
That’s why behavioral questions can feel harder than they sound. You have to choose a relevant memory, explain it to someone who wasn’t there, and make your own contribution clear—without spending three minutes on background. The STAR method gives that answer a shape. It stands for situation, task, action, and result. Think of it as a way to edit a true story, not a script to recite.
Pick the story before you build the answer
Behavioral questions ask for evidence from past experience. Prompts such as “Describe a time you changed your approach” or “Tell me about a goal you achieved” differ from hypothetical questions about what you would do. CareerOneStop distinguishes behavioral questions from hypothetical scenarios, and that distinction matters: an answer about your usual habits won’t replace a specific event.
Before an interview, read the job description and identify a few skills the role will require. For a project coordinator, those might include managing deadlines, communicating changes, and working across teams. Then look for moments when you demonstrated those skills. Work examples are useful, but school, extracurricular, and volunteer experiences can also provide specific evidence, especially if you’re early in your career or changing fields.
Choose a story using three tests:
- It answers the question. A successful launch may be your proudest achievement, but it’s a poor answer to “Tell me about a mistake” unless you can discuss an actual mistake within it.
- Your role is visible. You should be able to explain a decision you made or a step you took, even if the result belonged to a team.
- The outcome is clear. You know what happened, what you learned, or what changed afterward. A measurable result helps when it’s real, but it isn’t required.
A modest, well-explained example often works better than a dramatic one in which your contribution is hard to find. If you coordinated a handoff that kept a small project on track, you can show judgment, communication, and follow-through. You don’t need to have saved the entire company.
Give each part of STAR a job
The four parts aren’t meant to receive equal time. Situation and task help the interviewer understand the stakes. Action carries most of the evidence. Result closes the loop. The STAR framework is most useful when it keeps you focused on those essentials rather than making every answer sound identical.
Situation: Set the scene briefly
Say where you were, what was happening, and what made the moment challenging. One or two sentences are often enough.
Instead of walking through a department’s entire history, try: “During our monthly reporting cycle, two teams were using different definitions for the same customer metric. We discovered the mismatch the day before the report was due.”
That gives the interviewer what they need: a deadline, a problem, and a reason it mattered. Names, software tools, and side disputes can wait unless they’re essential to understanding your choice.
Task: Explain what you owned
Task is your responsibility or goal, not a second description of the problem. In the reporting example: “I was responsible for checking the figures and getting an accurate report to leadership by the deadline.”
If the task was shared, say so. You can describe your piece of a team effort without claiming you owned the whole project. Be precise about the difference between “I led the discussion,” “I proposed the fix,” and “I implemented the fix.” That precision makes the answer more credible.
Action: Show your judgment
Action is where many answers go vague. “I communicated with everyone” tells the interviewer little. What did you communicate, to whom, and why?
A stronger version might be: “I checked the definitions against the source data, called both team leads to agree on one measure, and updated the report notes so readers could see the change.” Those details show how you diagnosed the issue, brought people together, and prevented confusion later.
Use “I” when describing your contribution, while giving teammates credit for theirs. Spend the most time on the steps that reveal the skill the interviewer asked about. For a conflict question, that could be how you listened and reached an agreement; for a prioritization question, it could be how you decided what to delay.
Result: Say what happened—and what didn’t
Finish with the actual outcome. If the report went out accurately and on time, say that. If it was delayed, explain the delay and the decision behind it. If a new process came out of the experience, mention it if you can describe your part in the change.
Don’t invent a percentage to make the story sound impressive. A result can be a completed deliverable, a resolved disagreement, a decision made with better information, or a lesson you applied later. Penn’s guidance on behavioral answers includes both the outcome and what you learned as useful ways to close a response. Be careful, though, not to claim that your action caused a broader improvement you can’t substantiate.
Hear the difference in a complete answer
Suppose the question is, “Tell me about a time you had to manage competing priorities.” Here’s a sample answer based on an illustrative workplace scenario:
“At my last job, I was preparing materials for a client meeting when my manager asked for a separate report on the same afternoon. Both were due the next morning. I was responsible for getting the client materials ready, so I first checked which pieces required input from other people. I sent those requests immediately, then told my manager what I could finish that day and asked whether the report or the client materials should take priority if anything slipped. She confirmed the client deadline came first. I finished those materials that evening and sent her a draft of the report, with the remaining section flagged for the morning. Both were delivered when needed. Since then, I’ve raised deadline conflicts early instead of assuming I can absorb them.”
The answer doesn’t claim heroic productivity. Its strength is that you can follow the candidate’s choices: identify dependencies, clarify priorities, communicate a realistic plan, and follow through. It also answers the question directly. If the interviewer asks for more detail, the candidate has room to add it.
Now consider a question about failure. A convincing answer shouldn’t turn the mistake into a disguised triumph:
“I once sent a meeting agenda without confirming that the data owner could attend. The team couldn’t make the decision we’d scheduled the meeting for. I apologized, contacted the data owner that day, and circulated the missing information before rescheduling a shorter discussion. We made the decision at that follow-up meeting, but I had cost the group time. After that, I checked attendance with anyone essential to a decision before sending the agenda.”
This answer takes responsibility, describes the repair, and shows a change in behavior. It doesn’t pretend the first meeting was a success. For negatively framed interview questions, Harvard’s interview guidance emphasizes honesty, accountability, and improvement—a better approach than searching for a failure that wasn’t really yours.
Prepare a small set of stories, not a stack of scripts
You don’t need a separate memorized answer for every possible question. Build a short bank of experiences covering different strengths and challenges: a problem you solved, a time you worked with others, a change you handled, a mistake you corrected, and an accomplishment you can explain clearly. One story may fit more than one prompt, but adjust the emphasis to the question rather than repeating the same speech.
Make a few notes for each story:
- The question or skill it could address.
- The situation and your responsibility, in a sentence each.
- Two or three actions you took.
- The outcome and, if relevant, what you learned.
Then practice saying the story aloud without reading it. If the setup takes longer than the action, trim it. If you find yourself saying “we” throughout, identify where your own decision belongs. Ask a friend who doesn’t know the story whether they can tell what you did and why it mattered. That’s a more useful test than asking whether you sounded polished.
Memorizing sentences can make a good example harder to adapt when the interviewer phrases the question differently. Harvard advises preparing ideas rather than word-for-word scripts. The goal is to know your stories well enough to tell the right part of one naturally.
You can also use your application materials to spot stories worth preparing. If your resume summary highlights a particular strength, have an example ready that shows what that strength looked like in practice. An interview answer should add the decisions and context that a resume line can’t hold.
Stay flexible when the question surprises you
In the interview, listen for the precise behavior being tested. “Tell me about a disagreement” is different from “Tell me about a time you persuaded someone.” The same event might answer both, but you would focus on different actions.
It’s fine to pause briefly to choose an example. If you’re unsure what kind of experience the interviewer wants, ask a short clarifying question. Then begin with the situation rather than announcing each letter of STAR. You don’t need to say, “For the task portion of my answer…”
If you realize halfway through that your story is getting long, move to what you did and what happened: “The important part is how I handled the handoff.” If you don’t have an exact match, choose the closest genuine experience and explain its relevance. Don’t stretch a story until it describes work you never did.
The best STAR answers leave the interviewer with a clear picture of your behavior, not just a favorable impression of your result. Pick a true example, keep the setup lean, make your actions specific, and end where the story actually ended.