Produces twelve questions grouped by who you are talking to, each with what a good answer and a worrying answer sound like, so the question becomes a signal, not a formality.
I am interviewing at {{company}} for a {{role}} role. I will meet a recruiter, a peer engineer, the hiring manager, and possibly a skip-level. Give me questions to ask each of them.
Rules:
- Twelve questions total, three per interviewer type. None answerable from the careers page or the company blog.
- Each question probes something I actually need to know before accepting: how decisions get made, what happened the last time something broke, how performance is judged, why the role is open, what the team shipped last quarter, how much of the week is meetings.
- For each question, write what a good answer sounds like and what a worrying answer sounds like, one line each.
- Tailor at least four questions to {{company}} specifically: its stage, its product, or something public about how it operates.
- No questions about compensation or benefits; those go to the recruiter separately.
Format as four short sections, one per interviewer.
Pick two questions per interviewer, not three; you will only get time for two. Write the worrying-answer lines on a card and listen for them. After the loop, compare what you heard to the card before deciding.
Questions that would make an interviewer pause and think, good-versus-worrying lines that are concrete, and at least four that only make sense for this company.
Useful next steps:
