Skip to content
Tutorials Center
My learning

Topics

Lesson 74 of 77 ยท Interview Day

Questions to Ask Your Interviewer

Which questions to ask at the end of a tech interview about the team, the code, growth and red flags, plus a small planner that builds your question list.

Near the end of almost every interview you hear the same sentence: "Do you have any questions for us?" Many candidates treat it as a formality and say "No, I think you covered everything." That wastes the one moment where you control the conversation, and it is also your best chance to find out whether you would actually want the job.

An interview goes both ways. The company is deciding on you, and you are deciding on the company. Good questions show that you think about how software gets built, and they give you facts that no job post will. This lesson covers what to ask, who to ask it, which answers should worry you, and how to prepare a short list in advance. Nothing here needs a runtime, so the real content is plain text; the runnable parts are small stand-ins that help you organize your list.

Why your questions matter

Interviewers remember the last ten minutes better than the middle of the session. Thoughtful questions do three things:

  • They signal curiosity and maturity. People who ask how code reaches production tend to be people who care about quality.
  • They collect evidence for your decision. An offer is easier to judge when you know the on-call load, the review culture and the reason the role is open.
  • They are scored, quietly. In many hiring loops, "asked insightful questions" is a line on the feedback form.

What a good question does

Reveals facts You learn how work really happens.
Builds rapport It turns a quiz into a conversation.
Guides your choice You compare offers with evidence.

Ask because you want the answer, not to look clever.

1 / 2

Match the question to the person

You will usually talk to several people, and each one can answer different things. Asking a recruiter about code review practice gets you a polite guess; asking an engineer about salary bands gets you a shrug.

Interviewer Good topics
Recruiter Process and timeline, team structure, compensation process, remote or office policy
Engineer (peer) Day-to-day work, code review, on-call, tooling, what they would change
Engineering manager Expectations, how success is measured, feedback cadence, team goals, hiring plan
Senior or staff engineer Architecture, technical debt, how decisions get made
Founder or executive Strategy, funding or revenue health, where the product is going

Write down two or three questions per interviewer before the day starts, and bring the notes. Reading from a short list looks organized, not weak.

Questions about the team

You will spend more hours with these people than with most of your friends, so ask how they work together.

  • "What does a typical week look like for someone in this role?" The answer tells you how much of the job is building, meetings and firefighting.
  • "How is the team organized, and who would I work with most closely?" You learn the real shape behind the org chart.
  • "How does the team decide what to build next?" Good answers mention users, data and trade-offs, not only the loudest stakeholder.
  • "Why is this position open?" Growth, a new team and a departure are very different stories. A vague reply is information too.
  • "How long have people on the team been here?" Heavy turnover rarely has a happy cause.
  • "How do you handle disagreement about a technical decision?" Listen for a process, such as written proposals or a clear owner, rather than "the loudest person wins."

Questions about the technology and the code

These show that you care about the craft. Keep them specific to what you have already heard about the stack.

  • "How does code get from a laptop to production? How long does that take?" A fast, boring pipeline is a strong sign. "Every other Thursday, manually" says something else.
  • "What does code review look like here? How quickly do reviews usually happen?"
  • "How do you test? What happens when a test is flaky?" Compare the answer to the ideas in the testing lessons of this track.
  • "What is the most painful part of the codebase, and is anyone working on it?" Every codebase has one. Honest answers beat "nothing, it is great."
  • "What is the on-call setup? How often were people paged last month?" Ask for numbers, not feelings.
  • "How do you decide between building something and buying it?"
  • "What did the team ship recently that you are proud of?" Enthusiasm is easy to hear.

Questions about growth and feedback

  • "How do people here get feedback, and how often?" Weekly one-on-ones and clear expectations are healthier than a single yearly review.
  • "What would success look like in my first three months? In the first year?" A clear answer means your manager has thought about the role.
  • "How do engineers move up here? Can you give an example of a recent promotion?" Examples are better than policy documents.
  • "Is there time or budget for learning, conferences or side projects?"
  • "How do you onboard new engineers?" A written plan, a buddy and a small first task are good signs.

Red flags to listen for

No single answer is a deal-breaker, but patterns matter. These are signals to look at more closely, not proof of anything.

Answers that should worry you

Vague answers No one can explain how work gets done.
Permanent crunch Constant urgency and "we are family" talk.
High turnover Many people left within a year.
Dodged questions Pay, on-call or tests get a shrug.

One yellow flag is normal. Three in a row is a pattern.

1 / 2

Other warning signs: interviewers who contradict each other about the role, a manager who cannot say what the team is trying to achieve, or a refusal to discuss compensation range at all late in the process. Compare what you hear with the job post, and remember that a rushed or disorganized process often mirrors how the company runs.

Questions to avoid, and how to phrase hard ones

Skip questions whose answers are on the company website, such as "What does your company do?" That signals you did not prepare. Avoid opening with "How soon can I get a raise?" or "How many vacation days do I get?" in an early technical round; those belong with the recruiter or at the offer stage, where negotiation is expected.

You can still ask sensitive things politely by tying them to a goal:

  • Instead of "Do people work weekends?" ask "How does the team handle deadlines and sustainable pace?"
  • Instead of "Is the product failing?" ask "What are the biggest risks to the company's plans this year?"
  • Instead of "Is my manager good?" ask the manager "How would your reports describe your management style?"

A question planner you can run

The code below is a stand-in for a note-taking app. It stores a bank of questions tagged by area and by who can best answer them, then builds a short list for one specific interviewer. Nothing here calls a real service; it only filters and sorts an array.

JS Build a question list per interviewer

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The next stand-in is a tiny "flag counter" for the notes you take after each conversation. You score what you heard from 0 (nothing worrying) to 2 (clear concern) and let the code show where the concerns cluster.

JS Tally what you heard after the interview

Press Run (or Ctrl + Enter) to see the console output here.

No output.

What is real here and what is a stand-in: the questions and warning signs are real advice from how hiring works; the code only organizes them. A spreadsheet or a notes app does the same job.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Who is the best person to ask "How often were people paged on call last month?"

    Engineers who live the on-call rotation can give real numbers. Recruiters usually only know the official line.
  2. 2. Which of these is the better phrasing for a sensitive topic?

    Tying the question to a goal gets you the same information without sounding accusatory.
  3. 3. An interviewer cannot explain how work is prioritized, and two interviewers describe the role differently. What is the sensible reading?

    One signal is not proof, but unclear priorities and mixed role descriptions are worth probing before you accept.
  4. 4. Why avoid asking "What does your company do?"

    Questions you could answer with five minutes of research waste your time with the interviewer and send the wrong signal.

Summary

  • "Do you have any questions?" is a scored part of the interview and your chance to evaluate the employer.
  • Match questions to the person: recruiters for process, engineers for daily work, managers for expectations, executives for strategy.
  • Cover four areas: the team, the technology, growth and feedback, and warning signs.
  • Ask for specifics (numbers, examples, named processes) and treat vague or dodged answers as information.
  • Phrase sensitive questions around goals, and keep pay questions for the right moment.
  • Write your questions down before the day and take notes afterward.

Next, put everything together on the day itself in Interview Day Checklist and Common Mistakes.