Questions to ask your interviewer

Role and team

What does success look like in this role after the first six months?

This surfaces whether the role has concrete expectations at all, and lets you compare the answer against the job description you were sold.

What is the biggest challenge someone in this role would face right now?

A vague or evasive answer is itself information; a specific, slightly uncomfortable answer usually means you are talking to someone honest.

Why is this position open — new, a backfill, or growth?

A high-turnover backfill answered vaguely is worth probing further before you accept an offer.

How is the team structured, and who would I work with day to day?

Clarifies whether you would be embedded in a team or working solo, which matters more for fit than the org chart title.

What does the on-call or incident process look like for this team?

For engineering roles this is one of the most concrete signals of day-to-day quality of life, and a hesitant answer is worth a follow-up.

Manager and growth

How do you approach one-on-ones and feedback with your reports?

Asked to the hiring manager, this tells you how much structure and attention you will actually get, versus a title on a calendar invite.

What is an example of feedback you have given someone on this team recently?

A specific example beats a general philosophy answer, and an inability to give one is itself a data point.

What does the promotion path look like from this level?

Useful mainly at companies with defined levels; a company with none is not necessarily bad, but the answer should be honest about that.

What is something you would change about working here if you could?

A personal, specific answer usually beats the rehearsed reply to "what do you like most about working here."

Company and strategy

How has the team’s roadmap changed over the last year?

Reveals whether priorities are set with any stability or whipsaw quarter to quarter, which affects how much of your work actually ships.

What metric does this team get measured on?

If nobody can answer this cleanly, the team’s success is likely judged informally, which can cut either way depending on your tolerance for ambiguity.

How did the company handle its last layoff or hiring freeze, if any?

This is directly answerable at most companies now; the specifics of how it was communicated tell you more than whether it happened at all.

What is the runway or path to profitability, for an early-stage company?

A reasonable interviewer expects this from a candidate evaluating risk, and a defensive reaction to it is itself informative.

How does the company decide what to build next?

A clear answer — customer research, a specific planning process — suggests product decisions are not purely reactive.

Culture and day-to-day process

What is the company’s approach to remote or hybrid work, and has it changed recently?

Policies have shifted quickly across the industry; ask about the current policy and whether another change is being discussed, not just what is in the offer letter.

How would you describe the engineering culture — code review norms, test coverage expectations?

Concrete process details, like review turnaround time or test requirements, are more useful than "we move fast."

What tools does the team use for its day-to-day work?

Practical, and can surface a tech-stack mismatch with what you were told during earlier screening.

What do people who leave this team tend to say when they leave?

A blunt question, but a thoughtful interviewer will usually give you a real answer, and a "nobody ever leaves" response is a flag.

Closing the interview

What does the process look like from here, and when should I expect to hear back?

A practical logistics question that also signals how organised the hiring process is.

Is there anything about my background that makes you hesitant about this role?

Gives you a direct chance to address an objection before you leave the room, rather than losing the offer to something you could have clarified.

How this is worked out

• Twenty questions across role, manager, company and closing topics.
• Each one is paired with what to listen for in the answer, since the question itself is only half the value.
• Pick two or three that fit the round — a recruiter screen and a final round warrant different questions.

Questions people ask

How many questions should I actually ask?

Two or three well-chosen ones beat five generic ones. Time is usually short at the end of a round, and quality reads better than quantity.

Is it ever fine to say I have no questions?

Only if you have genuinely asked everything already in an earlier round with the same person. Otherwise it reads as disengagement, even if that is not the intent.

Should I ask the same questions to every interviewer?

Vary them by who you are talking to — ask a manager about feedback and growth, ask a peer about day-to-day tools and process.