[NTTP]

Interview Answer Helper

Paste an interview question and your experience. Get a strong, natural answer plus delivery tips.

The situation, what you did, and how it turned out. Rough notes are fine.

Free to try, no sign-up needed

Your text isn't stored. It's sent to Anthropic to generate your result, then discarded. Privacy

Prefer to write it yourself? Use the free prompt.

New to this? Read the guide.

What it produces

Real output from this tool, not a mock-up.

What went in

The interview question
Tell me about a time you had to give someone difficult feedback.
Your relevant experience
I manage a team of 5. One of my support agents, really well liked, was closing tickets fast but customers kept reopening them. I pulled twenty of his reopened tickets, sat down with him and went through five together rather than showing him the stat. He spotted the pattern himself. We agreed he would flag anything ambiguous to me for two weeks. Reopen rate went from about 30% to under 10% in six weeks.
Style
STAR

Your answer

I had a support agent on my team who was really well liked, and his dashboard looked great, fast resolution times, high ticket volume. But when I dug into the numbers I noticed his reopen rate was way higher than the rest of the team, around 30%. The stat alone wasn't going to land well with him, so instead of leading with it, I pulled twenty of his reopened tickets and sat down with him, and we went through five together. I wanted him to see the pattern himself rather than me telling him what was wrong. He noticed it pretty quickly, he was answering the literal question customers asked instead of digging into what they actually needed. From there we agreed he'd flag anything ambiguous to me for two weeks so I could sanity check his read on it. His reopen rate dropped from about 30% to under 10% within six weeks, and he kept that habit of flagging unclear tickets long after the two weeks were up.

Delivery tips

  • Slow down on the part where you describe going through tickets together, that's the core of the story and shows you didn't just lecture him.
  • Land the ending firmly on the reopen rate drop, don't rush past it or tack on extra explanation after.
  • Keep steady eye contact when you say he spotted the pattern himself, that detail is what makes this feedback story different from a generic one.

When to use it

Use this while preparing for an interview, not during one. Paste a question you expect and the experience you would draw on, and you get an answer in your own material plus notes on delivering it. It is most useful for the behavioural questions where people ramble, because it forces the story to land on a result.

Common questions

Should I memorise the answer it gives me?
No. Read it a couple of times, keep the structure and the numbers, then say it in your own words. A memorised answer sounds memorised, and interviewers ask follow-up questions that a script cannot survive. Treat the output as a well-organised version of your own story, not a line to recite.
What is the difference between the three styles?
STAR structures the answer as Situation, Task, Action, Result, which is what most large employers score against. Conversational is looser and suits a first-round chat or a startup. Concise strips it to the shortest version that still lands a result, useful when you know you talk too long.
What are the delivery tips for?
They cover the things that go wrong when the answer is spoken rather than read: where to slow down, which sentence to land firmly, and what to leave out. Most people lose a behavioural question on delivery rather than content, usually by rushing the result at the end.
Is it free?
You can run it three times a day with no account. Signing in gives you renewing monthly credits, and this tool costs one credit per run with the one-click refinements included.

Similar tools

All Job Hunting