Questions for the Interviewer

"Do you have any questions for us?" is part of the interview. You are showing how you think and deciding whether to work there. People who say "no, I think you covered it" waste the only time they will get unscripted information.

[!TIP] ELI5: You are buying a used car They already test-drove you. Now you kick the tires. Asking about the transmission is not rude. Asking only about the cup holders (perks, snacks) tells them what you optimize for.

What good questions do

1. Reveal priorities. Seniors ask how code gets to prod, how incidents work, how they decide architecture. Juniors often ask only about onboarding perks. Both can ask both; lead with work.
2. Collect signal. You might not want this job. Better to learn that in the round than in week two.
3. Use the conversation you already had. If they mentioned a monolith, ask about the strangler plan. That proves you listen.

Ask 2–3 questions you actually care about. A list of 12 sounds like a blog post.

Questions that produce real answers

Engineering and process

• "What does a PR look like here — who reviews, how long, what gets blocked?"
• "Walk me through the last production incident you were in. What broke, and what changed after?"
• "How does a change get from a laptop to production? What's manual?"
• "How do you decide to pay down tech debt versus ship the roadmap?"

Listen for: blameless postmortems vs "we don't have incidents." Multi-hour deploys vs boring CD. "We never have time for tests" is a forecast of your next year.

The role

• "What would good look like in 90 days for this seat?"
• "Is this a backfill or a new role? What did the last person struggle with?"
• "What's the hardest problem on the team's board right now?"

Listen for: a real problem vs "we'll figure it out when you start." Vague 90-day success often means the manager has not thought about you.

Manager and growth

• "How do you give feedback? Can you give an example from last month?"
• "When someone on the team was stuck, what did you do?"
• "How do staff/senior engineers spend time besides tickets?"

Ask the manager what their calendar looks like if you want the truth about meetings vs making space.

Strategy (use sparingly)

• "What's the bet the company is making in the next year that engineering has to enable?"
• "Where does this team sit relative to revenue?"

Senior questions that are not theater

These work if you can handle the answer:

• "What's the most misunderstood thing about how this team actually works?"
• "If you could change one thing about the stack or the process tomorrow, what?"
• "How do you choose new technology — RFC, whoever yells, copy of the last job?"

[!WARNING] Do not ask these as a personality performance if you are interviewing for your first job. Ask about the on-call rotation, how they teach, and what a first-month project looks like. That is senior for that level.

What not to ask this person

On-call, remote policy, and "does the team ship on Fridays" are fair game — they are working conditions, not gossip.

How to run the last five minutes

1. You already took notes. Ask about something they said.
2. One process question, one role question.
3. If you have time, one culture or process pain question.
4. Stop. Do not fill silence with a fourth.

If they give a polished non-answer twice ("we're like a family," "we move fast"), that is the answer. Write it down.

What to remember

• This segment is scored. Empty "no questions" is a weak close.
• Prefer questions whose answers would change your decision.
• Follow up on their words from earlier in the hour.
• Save compensation for the person who owns the offer.