Verified against ChatGPT · 2026-08-09
Check your behavioral interview answers for the specific things that quietly read as red flags
Reviews your drafted behavioral answers for specific, well-documented red-flag patterns — blame-shifting, vague ownership, unverifiable claims — rather than generic tone feedback.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Review my behavioral interview answers for specific red-flag patterns that experienced interviewers are trained to notice, not generic feedback about tone or confidence. MY DRAFTED ANSWERS When the project fell behind schedule, we decided to cut some features to hit the deadline. We ended up shipping on time and the client was happy with the result... QUESTIONS THEY'RE ANSWERING Tell me about a time a project you were on fell behind schedule. ROLE I'M INTERVIEWING FOR Technical Project Manager role that specifically emphasizes stakeholder communication under pressure. Check each answer against these specific patterns, and only flag ones that genuinely appear rather than forcing every pattern onto every answer: 1. BLAME WITHOUT OWNERSHIP. Does the answer describe a problem as something that happened to me or was caused by someone else, without naming what I specifically did or could have done differently — even in a story about someone else's failure, a strong answer usually still contains a piece of my own agency or reflection. 2. VAGUE PRONOUNS HIDING UNCLEAR CONTRIBUTION. Does the answer use "we" throughout a section where the interviewer is specifically trying to learn what I personally did, in a way that could be covering for a smaller individual contribution than the story implies. 3. UNVERIFIABLE OR SUSPICIOUSLY ROUND CLAIMS. Any metric or outcome stated with a precision or magnitude that reads as invented or rounded up rather than remembered — a real number is often oddly specific or hedged, not a clean round figure. 4. UNRESOLVED TENSION LEFT HANGING. Does the story raise a conflict or difficulty and then jump straight to a resolved outcome without explaining the actual mechanism that got from one to the other, which reads as either an incomplete story or one where the real answer is being avoided. 5. MISMATCH WITH ROLE PRIORITIES. Does the answer emphasize a quality or skill that isn't actually what this specific role cares about, suggesting the story was recycled from a different application without adapting the emphasis. For each flag you raise, quote the specific sentence that triggers it and give me one concrete rewrite direction, not just "add more ownership" in the abstract. WHAT NOT TO DO Do not flag something as a red flag just to have something to say about every answer — if an answer is genuinely clean, say so plainly rather than manufacturing a minor nitpick. End with which single answer, if any, has the most serious flag and should be fixed first given limited prep time.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Generic feedback like "sound more confident" or "be more specific" is nearly unusable because it doesn't tell the candidate which sentence to change or how — this prompt instead names five specific, well-documented patterns experienced interviewers are actually trained to notice, which gives the model a checkable framework to apply to the actual text rather than an open-ended impression to form. The "we" pattern specifically matters because it's one of the most common and most subtle red flags in behavioral interviewing — a candidate describing team accomplishments in first-person-plural throughout an answer to a question explicitly asking what they personally did is a pattern interviewers are specifically trained to probe with a direct follow-up ("what did you specifically do"), and catching it before the interview is far cheaper than being caught by that follow-up live. The instruction to flag suspiciously round or precise numbers addresses a specific tell that experienced interviewers watch for: real remembered metrics tend to be oddly specific ("we cut it from 14 days to 9") or explicitly hedged ("roughly a third faster, I'd have to check the exact number"), while a fabricated-sounding number defaults to a clean round figure the brain reaches for when inventing rather than recalling, and a model reviewing a draft can be instructed to notice that same tell a skeptical human interviewer would notice. The explicit instruction against manufacturing a flag on every answer matters because a model asked to "find problems" will tend to find something in every input regardless of actual quality, which erodes the signal value of the flags that are genuinely serious — telling it plainly that a clean answer should be reported as clean keeps the flagged issues meaningful rather than diluted by forced nitpicks.
What you get back
Flag (pattern 2, vague pronouns): "We decided to cut some features" — for a question specifically about your role in a project falling behind, this hides whether the decision was yours to make or you were following someone else's call. Rewrite direction: name your specific role in that decision — did you propose the cut, push back on it, or execute someone else's call — since the interviewer is trying to learn your individual judgment under pressure, not the team's collective outcome.
Verified against
ChatGPT GPT-5.1 · 2026-08-09
Changelog
- 2026-08-09 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.
EXPLORE WHAT SCULT BUILDS
