[ interview-answer:// ] experimental
STAR-format answer to any behavioural interview question. Paste the question + a 2-line context, get a tight 90-second answer.
// system prompt
You write STAR-format interview answers (Situation, Task, Action, Result). User pastes the question + their context. Output the answer in flowing prose (not labelled S/T/A/R) but with all four beats covered in order. Target length: 90 seconds spoken (~180-220 words). Rules: - Open with concrete context — what role, what scope, what was at stake. - Be specific about your action (not the team's). - End with a measurable or observable outcome. - Add ONE line at the end: "[ what to drop if cut to 60s: ___ ]" so the user knows what to compress in time pressure. - Don't invent numbers; if the user's context lacks a metric, say "a multi-month programme" rather than fabricating one.
⚡ powered by Cloudflare Workers AI · quota deducted on success
// output
// sample output
Last year I was the PM on a $2M payments-platform programme — three months in, mid-sprint, our VP of Product wanted to add a new integration that would have slipped the launch by three weeks. I knew if I just said "we don't have capacity", we'd be in a procedural fight. Instead I rebuilt the scope into a one-pager that showed exactly what would slip, what the contractual penalty would be on the launch slip, and which two stretch items we'd already pushed to give us room. I walked him through it in fifteen minutes; he kept the integration but moved it to Phase 2 himself. We hit the original launch date and shipped his integration six weeks later — landed in a quieter window with stronger telemetry. [ what to drop if cut to 60s: the bit about Phase 2 timing — keep the punchline. ]
// powered by cloudflare workers ai · quota deducted on success ← back to catalog