The STAR method and STAR interview questions for program, project and product managers
The short answer
The STAR method is a way to answer a behavioral interview question in four parts: situation, task, action and result. 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 record that a reader could check.
Practice your answers in Claude with Interview Coach, free
What each part of the STAR method needs
The STAR answer check and Interview Coach read a practice answer with the same fixed rules. The table shows what those rules look for in each part.
| Part of STAR | What the check looks for |
|---|---|
| Situation and task | An opening that sets the scene, such as a deadline, a problem or a project you took over. The two parts are read together. |
| Action | At least 2 actions said with I. We is not used more than twice as often as I. |
| Result | A result named near the end, such as a decision, a delivery or a change. |
| Proof | A figure before and after, or a named record, such as a status report, a dashboard or the steering minutes. |
| Learning, for a setback question | What you do differently since. It takes the place of proof. |
The check does not look for a separate sentence for the task. A good opening covers both: what was at stake and what you were asked to do. A figure with no starting point does not count as proof, because the reader cannot see what changed. You do not need a number in every answer: a named record, such as a status report, a dashboard or the steering minutes, also works.
Why the action and the result decide a manager answer
An interviewer hears many answers that describe a team. A manager answer has to show the manager's own part: the call you made, the risk you logged, the plan you changed. Say it with I, and give the team's work one sentence.
The result is the second test. A result that can be checked sits in a record, such as a status report, a RAID log or the steering minutes. A change request log or a dashboard also works. Name the record, and the interviewer can ask to see it.
The records differ by role:
- Project manager: the RAID log, the status report, the change request log.
- Program manager: the dependency log, the benefits register, the board minutes.
- Product manager: the roadmap review, the metric on the team dashboard, the support tickets.
How to build a STAR answer
Build a STAR answer from one real project, in the order of the four parts.
- Choose one project where you made a decision, not one where you only took part.
- Write the situation and the task in two sentences: what was at stake and what you were asked to do.
- List two or three actions in the order you took them, and start each with I.
- State the result in one sentence, and name the record where it shows.
- Add the figure before and after if you have it, then say the answer aloud and time it.
A spoken answer of about one to two minutes is long enough for all four parts. The check marks an answer under 60 words as short and one over 350 words as long.
Four STAR answers as written, and what the check finds
Each answer replies to the question "Tell me about a risk you saw early. What did you do before it became an issue?" and is one or two sentences, so the check also marks all four as short.
| Answer as written | What the check finds | What to add |
|---|---|---|
| When test data arrived late, the risk was logged and the go-live moved by a week, and the project went live on time, per the steering minutes. | No sentence says what you did yourself, with I. | Say which steps were yours, with I: who logged the risk and who told the sponsor. |
| When data came late, we logged it, we told them, we retested and we reported. I raised it and I replanned, and we went live, per the steering minutes. | Mostly we and the team. The interviewer cannot tell which part was yours. | Give the team one sentence, then say which calls were yours. |
| I logged the risk and I told the sponsor the date should move by a week, and the release shipped on the new date, per the steering minutes. | No context is set before the action. Add what was at stake. | Open with what was at stake before you acted. |
| When test data arrived late, I logged the risk and I told the sponsor the date should move by a week, per the steering minutes. | No result is named. Say what changed. | Say what changed in the end, and where it shows. |
Illustrative, not a real client.
The check never adds a fact for you. It marks the gap, and you fill it from your own project.
Three STAR answers from project, program and product managers
Each answer below gets every mark of its question's check. The employers and figures are invented.
Project manager. Question: "Tell me about a risk you saw early. What did you do before it became an issue?"
When the build phase was ending, the vendor's test data had not arrived and the go-live date was at risk. I wrote the risk in the RAID log with a trigger date and I asked the vendor lead for a firm delivery date. When the date slipped, I took two options to the sponsor and I asked her to choose. She approved a one-week move of the go-live. The project went live on the new date, and the RAID log shows the risk closed with her decision attached.
Illustrative, not a real client.
Program manager. Question: "Tell me about a dependency between two projects in your program that threatened a milestone."
When I took over a program of five projects, the data migration was three weeks late and the clinic rollout depended on it. I mapped the dependency with both project managers and I showed the sponsor that the rollout date could not hold. I proposed two options: move the rollout by a month, or add two engineers to the migration. The sponsor chose the engineers, and I tracked the migration weekly in the dependency log. The migration closed one week late and the rollout kept its date, per the steering minutes.
Illustrative, not a real client.
Product manager. Question: "Tell me about a feature you decided not to build. How did you decide, and who disagreed?"
When sales asked for a custom reporting screen, the team had room for one large feature and the goal that quarter was fewer report tickets. I read the 40 support tickets about reports and I found that most asked for a simple export. I told the sales lead I would not build the screen, and I showed her the tickets. I scoped the export instead, and she disagreed until the next roadmap review. Report tickets went from 40 a quarter to 9, per the support dashboard.
Illustrative, not a real client.
STAR interview questions and answers
STAR interview questions are behavioral questions: they ask about a time something happened, and STAR is the order of the answer. Four questions are a good place to start. Each one weights the four parts a little differently.
Tell me about a time you disagreed with a senior stakeholder. What did you do, and how did it end?
Name the stakeholder by role and say what each side wanted. Then say what you did to move the disagreement, and how it ended, including any part that did not go your way. How to answer the stakeholder conflict question
Tell me about a project or a decision that did not go to plan. What was your part in it?
The setback question asks for learning, not proof. Say what went wrong, your own part in it, what you did once you saw it, and what you do differently since. How to answer the failed project question
Tell me about a time you had to get people to act when they did not report to you.
Name who had to act and why they had no reason to. The actions are the steps you took, such as data, a trade or an escalation, and the result is what they did. How to answer the influence without authority question
Tell me about the hardest deadline you have worked to. What did you cut, and who agreed?
Name the date, what you cut and who agreed. The proof is the record of the decision, such as the change request or the steering minutes. How to answer the hardest deadline question
More STAR interview questions by competency
Role interviews add questions about the work itself. Each one below has its own guide with an answer as written and what the check finds.
| Competency | STAR interview question | How to answer it |
|---|---|---|
| Scope | Walk me through a scope change request you handled. How did you decide, and who approved it? | The scope change question |
| Risk | Tell me about a risk you saw early. What did you do before it became an issue? | The project risk question |
| Recovery | Tell me about a project that was off track when you took it over. How did you bring it back? | The project recovery question |
| Dependencies | Tell me about a dependency between two projects in your program that threatened a milestone. | The program dependency question |
| Metrics | Tell me about a product metric you moved. What was it before, and how do you know your work moved it? | The product metric question |
| Vendors | Tell me about a vendor decision that was yours. What were the options, and what happened? | The vendor decision question |
For thirty questions in one list, sorted by what each one tests, see 30 common behavioral interview questions for project managers.
Check one of your answers
When your answer has the four parts, check it against the same rules.
The same rules apply to a line on a resume, but the line is shorter. How to use the STAR method on a resume shows which parts fit in one bullet. For the full list of questions by role, see behavioral interview questions for PMs.
A STAR answer that reads well can still run long when spoken. To rehearse it aloud with a partner and a score sheet, use mock interview questions for project managers.
Practice with Interview Coach in Claude
A behavioral question can come up in any project, program or product manager interview. Write your answer the way you would say it and ask Interview Coach for a check.
- Paste your resume and the job posting. Interview Coach returns the lines a hiring manager is likely to ask about, each as a question that quotes your own line, with the points a strong answer covers.
- It matches the requirements of the posting to your resume and turns the gaps into questions to prepare.
- Write one answer at a time and ask for a check. It looks for a situation, your own action, a result and a before and after figure or a named record. It does not judge whether the story is true.
Your answers start from your resume. The free review quotes your own lines and flags the 5 to fix first, so you know which lines an interviewer may question.
Free in Claude, no account. We do not store the text you send through it.
Questions
What does STAR stand for in an interview?
STAR stands for situation, task, action and result. It is an order for telling a behavioral answer: what was at stake, what you were asked to do, what you did, and what changed. Interviewers use the order to follow your part in the story.
How long should a STAR answer be?
About one to two minutes when spoken. The answer check marks an answer under 60 words as short and one over 350 words as long. Most of the time goes to the action and the result, not to the situation.
What are STAR interview questions?
They are behavioral questions that ask about a time something happened, such as a conflict, a missed date or a risk. STAR is not a separate kind of question but the order of a good answer. Any question that starts with tell me about a time can be answered with it.
Keep going
- How to use the STAR method on a resume
- Behavioral interview questions for PMs
- How to answer the stakeholder conflict question
- Project manager interview questions
Last updated: October 25, 2026