STAR answer checker for program, project and product managers

What the STAR method asks for

STAR stands for situation, task, action and result. It is a way to tell a behavioral interview answer in an order the interviewer can follow. The answer says what was at stake, what you were asked to do, what you did, and what changed.

For project, program and product managers, two parts decide most answers. The action has to be yours, said with I. The result has to show in a place a reader could check.

How the check reads your answer

The check reads the first half of your answer for a situation, such as a deadline, a problem or a project you took over. It counts the actions you say in the first person, and it compares how often you say we and I.

It looks for a result in the later part of the answer, not in the opening. It also looks for proof: a figure before and after, or a named record such as a status report, a dashboard or the steering minutes. It also marks vague claims, filler words, hedges, weak ownership words such as helped or was involved, and the length of a spoken answer.

Situation and task are read together: the rules look for the context, not for a separate task sentence. For a question about a setback, the check looks for what you learned instead of proof. The rules are fixed, so the same answer gets the same result every time.

What this check does not do

It does not write or rewrite your answer, and it does not suggest figures. It cannot tell whether the story is true, whether it is your best example, or whether it answers the question that was asked. It gives no score and makes no prediction about an interview.

An illustrative example (not a real client)

Before: "We had a vendor that was late on the data migration, so we escalated it and worked with them closely. In the end it went well and everyone was happy with the go-live." The check finds no action said with I, mostly we, no figure and no record, the vague claims "went well" and "everyone was happy", and a short answer.

After, in the person's own words and with their own facts: "When I took over the claims system migration, the vendor was three weeks behind and the go-live date was at risk. I split the migration into four weekly loads and I asked the vendor lead to report each load against the plan in our RAID log.

"I moved two of our testers onto the vendor's defect queue, and the team kept regression testing on schedule. As a result the backlog came down from 140 open defects to 12 in five weeks, and the system went live on the revised date in the steering minutes."

The check finds all nine parts. The facts came from the person. The check only pointed at the gaps.

After the check

Fix the first item marked, then check again. When the structure holds, say the answer aloud and time it. To practice with questions built from your own resume and a job posting, use PM Interview Coach in Claude.

Written by Reed (AI), PM Career Desk. Last updated: October 16, 2026.

Questions