AIO APEX
Claude Opus 5 (also works well with GPT-5.4 and Gemini 3 Pro)You have a final-round interview in three days for a senior product manager role, and you know behavioral questions are coming, but your work history spans five different projects and you're not sure which stories map to which likely questions — or where your prep has gaps.Career

Le Constructeur de Réponses d'Entretien STAR : Transformez Votre Parcours Professionnel en Réponses Comportementales Percutantes

Partager:
Le Constructeur de Réponses d'Entretien STAR : Transformez Votre Parcours Professionnel en Réponses Comportementales Percutantes

Pourquoi ce prompt est important

Rambling, unstructured answers to behavioral questions are one of the most common reasons qualified candidates lose offers — not because they lack the experience, but because they can't retrieve and structure a specific story fast enough under interview pressure. Candidates who walk in with pre-mapped stories answer more concisely, sound more confident, and are far less likely to freeze on a question they technically could have answered well.

À quoi nous l'utilisons

You have a final-round interview in three days for a senior product manager role, and you know behavioral questions are coming, but your work history spans five different projects and you're not sure which stories map to which likely questions — or where your prep has gaps.

Prompt

Act as a former hiring manager and interview coach who has conducted hundreds of behavioral interviews and coached candidates through offers at competitive companies.

Context — here is what I'm working with:
- Job description: [PASTE THE FULL JOB DESCRIPTION]
- My relevant work history / resume bullet points: [PASTE YOUR RESUME BULLETS OR A LIST OF YOUR KEY PROJECTS AND ACCOMPLISHMENTS]
- Role level: [E.G., ENTRY-LEVEL, MID-LEVEL, SENIOR, MANAGER]
- Interview type: [E.G., PHONE SCREEN, ONSITE PANEL, FINAL ROUND WITH VP]

Task: Do this in three passes.
Pass 1 — Predict: Based on the job description, list the 8-10 behavioral questions this role is most likely to ask, grouped by the competency each question is testing (e.g., leadership, conflict resolution, ambiguity, technical judgment).
Pass 2 — Match: For each predicted question, identify which specific story from my work history best answers it. If no story in my background is a strong match for a predicted question, say so explicitly instead of forcing a weak fit — flag it as a "Gap" so I know to prepare a new example or reframe an existing one.
Pass 3 — Build: For every question with a matched story, write a full STAR-format answer (Situation, Task, Action, Result) using only details drawn from what I actually provided — do not invent outcomes, metrics, or details not present in my input.

Constraints:
- Every Result must include a specific outcome — if I didn't provide a measurable result, prompt me for one instead of inventing a percentage or dollar figure.
- Keep each STAR answer under 200 words — long enough to be substantive, short enough to say out loud in under 90 seconds.
- Flag any answer that leans too heavily on "we" instead of "I" — interviewers are evaluating individual contribution.
- Do not use generic corporate language ("synergy", "leverage", "move the needle") in the answers.

Output format:
1. Predicted Questions by Competency (grouped list)
2. Question-to-Story Map (table: question, matched story, or "Gap — no strong match")
3. Full STAR Answers (one per matched question)
4. Gaps to Prepare (bullet list of predicted questions with no current story, so I know what new example to think through before the interview)

Résultat

Predicted Questions by Competency

  • Cross-functional leadership: "Tell me about a time you had to influence a team without direct authority."
  • Handling ambiguity: "Describe a project where the requirements changed midway through."
  • Conflict resolution: "Tell me about a disagreement with a stakeholder and how you resolved it."
  • Prioritization under pressure: "Walk me through a time you had to cut scope to hit a deadline."

Question-to-Story Map

QuestionMatched Story
Influence without authorityQ3 checkout redesign — aligning eng, design, and support leads
Requirements changed midwayQ3 checkout redesign — pivot after usability testing
Disagreement with stakeholderGap — no strong match provided
Cut scope to hit deadlineMobile app v2 launch — deferred two features to hit App Store deadline

Full STAR Answer — Influence Without Authority

Situation: Our checkout redesign was stalling because engineering wanted to ship fast with the existing flow, while design was pushing for a bigger structural change based on usability testing.
Task: As the PM, I needed to get both teams aligned on a single direction within two weeks, without either team reporting to me.
Action: I set up a working session where I had design walk engineering through the actual usability test recordings instead of just the findings summary — seeing users struggle in real time changed the conversation. I then proposed a phased approach: ship the structural change to the highest-traffic flow first, validate it, then extend it.
Result: Both teams signed off on the phased plan within the two-week window, and the first phase shipped on the original engineering timeline while still incorporating the design team's core recommendation.

Gaps to Prepare

  • Disagreement with a stakeholder and how it was resolved — no current story provided. Worth preparing a specific example before the interview rather than answering this one cold.

Un prompt en trois passes qui prédit les questions comportementales qu'un poste posera, les associe à votre véritable parcours professionnel, et rédige des réponses au format STAR — tout en signalant les lacunes où vous n'avez pas encore d'histoire solide.

Cas d'Usage

Vous avez un entretien de dernier tour dans trois jours pour un poste de chef de produit senior, et vous savez que des questions comportementales arrivent, mais votre parcours professionnel couvre cinq projets différents et vous n'êtes pas sûr de quelles histoires correspondent à quelles questions probables — ni où votre préparation présente des lacunes.

Pourquoi C'est Important

Les réponses décousues et non structurées aux questions comportementales sont l'une des raisons les plus courantes pour lesquelles des candidats qualifiés perdent des offres d'emploi — non pas parce qu'ils manquent d'expérience, mais parce qu'ils ne peuvent pas récupérer et structurer une histoire spécifique assez rapidement sous la pression de l'entretien. Les candidats qui arrivent avec des histoires pré-cartographiées répondent plus succinctement, paraissent plus confiants, et sont bien moins susceptibles de se figer sur une question à laquelle ils auraient techniquement pu bien répondre.

prompt-engineeringCareerinterview-prepstar-methodjob-interview
Partager: