Questions for interviewer that reveal the job behind the ad

Introduction

Most candidates treat "Do you have any questions for me?" as a polite way to end the interview. It's actually the only part of the interview where you collect evidence instead of giving it.

Good questions for interviewer conversations do more than make you look prepared. They show you how many hours the team really works, whether the manager coaches people or blames them, and why the last person in the role left. 

This guide gives you those questions, along with what a healthy answer sounds like and what should make you pause.

If you want advice on what to ask a recruiter versus a hiring manager at each round, our guide to questions to ask the interviewer at every interview stage covers that. This guide is about reading the answers.

TL;DR

• The answer matters more than the question. Listen for specific names, dates and numbers, not general reassurance.
• Ask about the last busy stretch, not "work-life balance." Past events are harder to dress up.
• Questions about feedback and the previous person in the role tell you how the hiring manager actually manages.
• Technical candidates should ask how code reaches production and how many on-call pages a typical shift gets.
• When an answer is vague, use a follow-up that asks for a recent example.

Why the answers matter more than the questions 

Both sides are selling during an interview. The company wants you to see its best side, and the person across the table may well be your future manager.

That matters more than most candidates think. Gallup estimates that managers account for at least 70% of the variance in employee engagement across business units. Your experience of the job will depend heavily on the person answering your questions.

The time you'll spend in the role also makes the effort worth it. The U.S. Bureau of Labor Statistics found that median tenure for workers aged 25 to 34 was 2.7 years in January 2024. 

Ten minutes of sharp questions to vet a job you might hold for nearly three years is a good trade.

What evidence sounds like in an interview answer

A useful answer usually includes at least one concrete detail: a month, a project name, a number, or a person. "Last March we had a big release and the team worked two weekends, so we moved the next deadline" is evidence.

"We really value balance here" is not. It may be true, but it gives you nothing to check.

Questions for interviewer about workload and hours 

Asking "How's the work-life balance?" almost always gets a positive answer. Nobody says "terrible." Ask about something that already happened instead.

"What did the team's last really busy stretch look like?"

A healthy answer names a cause and an end. Something like "the Q2 migration, about three weeks of long days, then we gave people time back."

Pay attention if the interviewer can't point to one stretch because every stretch is busy. "It's a startup, it's always like this" tells you the pace isn't a phase.

"How often do people work outside normal hours, and what happens when they do?"

You're listening for a policy or a habit. Comp time, rotating coverage, or a manager who pushes back on unrealistic deadlines are all good signs.

If the answer is a laugh followed by "you'll see," take that seriously.

Questions to ask a hiring manager about how they manage 

These are the questions that make some hiring managers uncomfortable. That discomfort is useful information, so ask them in a friendly, curious tone.

"Can you tell me about the last time you gave someone on the team critical feedback?"

Good managers can usually remember a recent example. They'll describe a private conversation, a clear expectation, and some kind of follow-up.

Watch for two weak answers. One is "I can't really think of one," which often means feedback doesn't happen until it's a problem. The other is a story that makes the employee look foolish, which tells you how you'd be talked about.

"How did the person who had this role before do, and where are they now?"

If they were promoted or moved to another team, that's a strong sign the role leads somewhere. If they left the company, a manager who explains why in plain terms is usually being straight with you.

A long pause or a quick topic change doesn't prove anything on its own. It does mean you should ask the recruiter or a future teammate the same question.

Questions about team stability and turnover 

Turnover isn't always bad. Teams lose people to promotions, relocations and better offers. What you want to know is whether the reasons make sense.

"How long have the people on the team been here?"

A mix of long-timers and recent hires is normal for a growing team. A team where nobody has been around longer than a year deserves a follow-up, unless the team itself is new.

"Why is this role open right now?"

The best answers are specific: a new project, a budget approved for growth, or someone moving up. Be cautious if the answer is "it's been open for a while" with no reason, or if different interviewers give you different stories.

Staffing recruiters see this often. A candidate accepts a role described as a "modernization project," then learns in week two that the job is mostly keeping an old system running. Asking every interviewer the same "why is this open" question is a simple way to catch that early.

Questions to ask a technical interviewer 

Engineers on the panel tend to give the most honest answers about daily work. They're not selling the role in the same way, and they live with the codebase.

"Walk me through how code gets from a pull request to production."

You want named steps: code review, automated tests, a CI pipeline, a release schedule. The specific tools matter less than whether the process exists.

"It depends on who's around" or "we usually just push it" points to a team that fixes problems by hand, often late at night.

"What does on-call look like, and how many pages does a typical shift get?"

Ask for a number. Google's Site Reliability Engineering team, for reference, aims to keep on-call work under 25% of an engineer's time and incidents to about two per 12-hour shift. Most teams aren't Google, but a team that tracks its page volume at all is usually trying to keep it sane.

"It's not too bad" with no number is worth one more question: "How many pages did the last person on call get?"

"How much of the work is new features versus maintaining what's already there?"

There's no right ratio. Some people enjoy maintenance work. The point is to make sure the split matches what you expect, and what the job description implied.

Reverse interview questions about growth 

"Is there room for growth?" gets a yes every time. These versions ask for proof.

"What has someone on this team learned or moved into in the past year?"

A real answer names a person or a role change: "Ana moved from QA into a data engineering role after we paid for her cloud certification." A vague answer sounds like "there's lots of opportunity here."

"How are raises and promotions decided?"

You're not negotiating yet. You're checking whether there's a process, like a review cycle or a leveling guide, or whether it depends on who asks loudest. Asking this as one of your questions to ask at the end of an interview is usually fine if you keep it about process, not your own number.

How to read the answers: a quick reference 

Use this table during prep, then jot notes against it right after each interview while the answers are fresh.

Red flag or normal growing pains?

Not every imperfect answer is one of the interview red flags you should walk away over. Here's how to tell the difference.

Follow-up questions when the answer is vague 

A vague answer isn't a dead end. It's a cue to ask for one recent example. Keep your tone curious, not skeptical.

One follow-up is usually enough. If the second answer is still vague, note it and move on. Pressing three times turns a conversation into a cross-examination.

When you're interviewing through a recruiter or staffing firm 

If a staffing firm placed you in the process, your recruiter is a second source for checking answers. Many recruiters have placed people with the same client before and know how those placements went.

After each round, ask your recruiter: "The manager said the role is open because of a new project. Does that match what you've heard?" A good recruiter will tell you if past contractors left early or extended.

Contract and contract-to-hire setups come with their own questions about who employs you and how conversion works. 

Our breakdown of the pros and cons of working with staffing companies explains that arrangement before you get to the offer stage.

Putting your questions for interviewer prep together 

You don't need to ask everything in this guide. Pick two or three questions for interviewer rounds based on what you're most unsure about. 

If you left your last job because of burnout, lead with workload. If you've had a bad manager, lead with the feedback question.

Write down the answers right after each call. Patterns show up across rounds, especially when two people describe the same team very differently.

Before you start, it helps to know what each round will look like. 

Our interview format guide walks through common round types. When you reach the last stage, our list of final round interview questions to ask before an offer picks up where this guide leaves off.

Start Strong With Consultadd

With 15 years in business and 5,000+ successful staffing engagements, we don't just fill roles, we build reliability into your process. We've supported 65 staffing companies in the past year alone and maintain MSAs with industry leaders like Robert Half and TEKsystems.

Here's what working with Consultadd looks like:

• Talent sourced in under 24 hours
• Ready-to-deploy candidates, vetted for experience and compliance
• Lower turnover risk: we match long-term goals, not just short-term needs
• Seamless compliance: visa, documentation, onboarding? Handled.
• Dedicated 1:1 account managers for responsive, personalized support
• Top 100 candidate matches delivered in the past year
• Strong partnerships with universities to tap into fresh, committed talent
• Post-placement support so your investment grows beyond day one

For candidates, your next opportunity is more than just a job title, it's a chance to build skills, gain experience, and move your career forward. At Consultadd, we connect technology professionals with projects and employers that align with their goals, whether they're looking for contract, contract-to-hire, or long-term opportunities.

The tech job market moves fast, but the right guidance can make all the difference. Ready to take the next step in your career journey? Explore Opportunities >>

Key takeaways

• Treat your closing questions as research. The goal is evidence about the job, not just a good impression.
• Ask about specific past events, like the last busy stretch or the last feedback conversation, instead of asking for opinions.
• Concrete details in an answer (names, dates, numbers) are a good sign. Repeated general reassurance is not.
• Technical interviewers usually give the clearest picture of daily work, so ask them about deployment and on-call.
• One calm follow-up turns most vague answers into useful ones. If it doesn't, write it down and compare notes across rounds.

FAQs

What are three good questions to ask an interviewer?

Try "What did the team's last busy stretch look like?", "Why is this role open right now?" and "What has someone on this team moved into in the past year?" Together they cover workload, stability and growth. Each one asks about real events, so the answers are harder to polish.

What are red flags in a job interview?

Common warning signs include interviewers who describe the role differently, no clear reason for the opening, and vague answers about hours or on-call. Discomfort when you ask about the previous person in the role is another one. A single odd answer isn't a dealbreaker, but a pattern across rounds usually is.

What questions should you not ask in an interview?

Skip anything you could answer from the job posting or the company website. Avoid leading with pay and time off in a first conversation unless the interviewer raises it. Questions that sound like accusations, such as "Is this place a sweatshop?", also tend to backfire even when your concern is valid.

Is it OK to ask about turnover in an interview?

Yes, if you frame it with curiosity. "How long have people on the team been here?" or "Where is the person who had this role before?" gets the same information without sounding confrontational. Most good managers expect the question and answer it directly.

What is a reverse interview?

A reverse interview is when the candidate actively evaluates the employer by asking pointed questions about management, workload and growth. It's less about flipping the power dynamic and more about making sure you have enough information to make a real decision. Most interviewers respect a candidate who does it politely.

How do you ask about work-life balance without sounding lazy?

Ask about a past situation instead of the concept. "How did the team handle the last big deadline?" tells you about hours and how the manager protects people. It also sounds like you're planning for real work, not trying to avoid it.