Generate Interview Questions for a Role

This prompt builds a structured interview kit split into three buckets — skills, behavioral (STAR), and culture-fit — instead of a random list of questions. Reach for it the day before an interview when you want coverage of the role's actual must-haves rather than generic 'tell me about yourself' filler. Because each question comes with a note on what a strong answer looks like, it doubles as a scoring rubric for less-experienced interviewers on the panel.

What you can expect back

Technical / Skills
1. Walk me through how you'd design an idempotent payment-processing endpoint in Go. Strong answer: discusses idempotency keys, DB constraints, retries, and failure modes — not just happy path.
2. How do you debug a goroutine leak in production? Strong answer: pprof, runtime metrics, and a concrete past example.

Behavioral (STAR)
3. Tell me about a time you shipped something under a hard deadline with incomplete requirements. Strong answer: clear Situation/Task, owned the trade-off decision, names a measurable Result.

Culture Fit
4. Describe a time you disagreed with a peer's technical direction and how you handled it. Strong answer: shows direct but respectful conflict, comfort without heavy process, and a focus on outcome over ego.

Illustrative example — your results will vary by tool and inputs.

Get sharper results

• 01Paste the actual job description under the prompt — the model matches 'must-haves' far better from real bullet points than from the title alone.
• 02Ask it to flag which technical questions are 'screening' versus 'differentiating' so a phone screen and an onsite use different subsets.
• 03Request a follow-up probe for each question ('if the candidate gives a shallow answer, ask...') to keep weaker interviewers from accepting surface-level responses.
• 04For senior roles, tell it to bias behavioral questions toward influence and leadership rather than individual execution.
• 05Avoid culture-fit questions that just test sameness — ask the model to frame them around values and working style, not background, to reduce bias.

Adapt it for your case