The STAR method, but live for behavioral interview questions

Let’s focus on one specific type of interview question you can count on hearing in almost any panel: the behavioral, “tell me about a time” question. Things like “tell me about a project that went well,” “tell me about a time you worked as part of a team,” or “tell me about a time you improved a process.” We’ll get into other common interview questions in future issues. This one is just about this category, because it’s close to guaranteed to come up.

Have your examples ready

The mistake most candidates make isn’t a lack of experience. It’s walking in without a mental bank of examples ready to pull from. When the question lands and you’re searching your memory for the first time in that moment, even a strong example comes out disorganized.

Before your next interview, think through three or four examples in advance: a project that went well, one that didn’t, a time you worked closely with a team, a time you identified or solved a problem on your own. Have them ready in your head, not written out word for word, so you’re not building an answer from scratch under pressure.

STAR, but live

If you’ve used our STAR method guide or been with us since the welcome series, you already know the tool for structuring these once you’ve picked them: STAR (Situation, Task, Action, Result). We introduced it for supplemental questions on the application itself. Same framework here, but live, across the table from a panel, with no chance to edit before it’s heard. A few things change when STAR moves from the page to the interview room:

Keep it to about 60-90 seconds. A written answer can run several sentences. A spoken one needs to stay tight enough that the panel doesn’t lose the thread.

Don’t memorize it word for word. Know your Situation, Task, Action, and Result, but say them in your own words. A memorized answer falls apart the moment a follow-up knocks you off script.

A pause is fine. Two seconds to organize your thoughts before you start talking reads as thoughtful, not unprepared.

What it sounds like

Here’s how that sounds for someone like Jordan Reyes, an MPA graduate student, answering “Tell me about a time you identified a problem and took initiative to fix it”:

“During my internship, I noticed our office was manually re-entering the same data into two separate systems every week. It wasn’t part of my assigned duties, but I was the one most familiar with both systems, so I built a simple template that let us update one system and pull the numbers into the other automatically. I walked my supervisor through it so the office could keep using it after I left, and it cut that weekly task from about two hours to fifteen minutes, and the office still uses it today.”

Notice it’s shorter than it would be on paper. The structure is just there, holding the answer together and providing clarity for the panel.

Insider tip: The same example can often answer more than one of these questions. A project that hit a snag halfway through can work for “went well,” “didn’t go well,” or “worked with a team,” depending on which part you emphasize. Have a few examples that can work for different questions and you will feel more prepared.

Want new issues first? Subscribe for free below.