The Questions to Ask the Interviewer (and the Ones to Skip)

The 'do you have any questions for me?' moment is not optional and not throwaway. Strong candidates use it to demonstrate research, calibrate fit, and surface objections before they become silent reasons for a no. Weak candidates ask 'what's the culture like?'

Match the question to the interviewer

• Hiring manager: scope, success metrics, how the role fits into the org's six-month plan.
• Peer engineer: code review culture, on-call burden, what they'd change if they could.
• Skip-level or director: strategy, hiring philosophy, how the team is measured.
• Recruiter: process timeline, comp band, who else is in the loop.

High-signal questions

• 'What does someone need to do in their first 90 days for you to consider this hire a clear win?'
• 'What's the part of this role that's hardest to do well?'
• 'When was the last time you changed your mind about how the team works, and why?'
• 'What's the team's relationship with the rest of the org — who do you depend on, who depends on you?'

Treat answers as data

The point isn't only to perform — it's to find out whether you actually want the job. Listen for hesitation, for misaligned answers between interviewers, for vague descriptions of what success looks like. The best candidates walk out with as much information about the company as the company has about them.