Questions to ask the interviewer
In one line
Your questions at the end show genuine interest, help you judge whether the job suits you, and leave a final impression, so prepare specific ones for each interviewer.
What it is
Most interviews end with 'Do you have any questions for me?'. This is part of the interview, not a formality. Your questions show how you think, what you care about and how well you prepared.
It is also your chance to interview them: to learn how the team really works, what success looks like, and whether the role fits what you want. Good questions are specific, open-ended and suited to the person you are talking to.
Why interviewers ask
Saying 'no, I think you covered everything' can read as low interest. Thoughtful questions leave a strong final impression and give you real information to compare offers. Asking a hiring manager about expectations, or an engineer about their workflow, also shows you understand what each person knows best.
How it works
- 1Prepare 5-6 questions before each interview so you still have 2-3 left after some get answered during the conversation.
- 2Tailor them to the interviewer: engineers know daily work and tech; managers know expectations and team goals; senior leaders know strategy; recruiters know process and timelines.
- 3Prefer open questions about real experience ('What did your last week look like?') over generic ones ('What is the culture like?').
- 4Use what you learned in the interview: a follow-up on something they mentioned shows you listened.
- 5Save salary, benefits and leave for the recruiter or after an offer, unless the interviewer brings them up.
- 6Watch the time: ask 2-3 good questions, then thank them.
Worked example · Questions for a backend engineering interview, by interviewer
- With a peer engineer after a coding round: 'How does a change go from your laptop to production here, and how long does that usually take?' This reveals CI/CD maturity, code review and deploy frequency.
- Follow-up from the conversation: 'You mentioned migrating to Kubernetes. What has been the hardest part so far?' This shows you listened and gives insight into real challenges.
- With the hiring manager: 'What would a successful first six months look like for someone in this role?' This tells you expectations and how performance is judged.
- With the hiring manager: 'What is the biggest challenge the team is facing this year?' This shows interest in the team's problems and helps you judge whether they excite you.
- With a senior leader: 'How does this team's work connect to the company's goals for the next year?' This shows big-picture thinking.
- With the recruiter: 'What are the next steps and the timeline for a decision?' Practical and expected.
- Why this works: each question fits what that person knows, two are follow-ups from the conversation, and none could be answered by reading the careers page.
Picture it
It is like test-driving a car you might own for years: you would not just ask what colour it is, you would ask how it handles in traffic, what servicing costs and what other owners complain about.
Key patterns
Match the question to the person
When: Every interview
How: Engineers: daily work and tech. Managers: expectations and team challenges. Leaders: strategy. Recruiters: process.
Follow up on what they said
When: The interviewer mentioned a project, problem or change
How: Ask what made it hard or how it went; it shows you were listening and leads to honest detail.
Ask for real examples
When: You want honest answers about culture
How: Instead of 'is work-life balance good?', ask 'when did the team last work late, and why?'.
Real-world use
Understanding the work
'What does a typical week look like?' or 'How are projects chosen and planned?' tells you whether the day-to-day matches what you want.
Engineering practices
'How do you handle on-call and incidents?' or 'How much time goes to tech debt?' reveals working conditions and quality culture.
Growth and expectations
'How is performance reviewed?' or 'How have people in this role grown over the last two years?' shows ambition and helps you judge career paths.
Team and culture
'What do you enjoy most about working here, and what would you change?' gets more honest answers than 'what is the culture like?'.
In a project
You have a final-round loop of four interviews at one company (two engineers, a hiring manager and a director) and want to use your questions well.
- Research the company: engineering blog, recent product launches, job description and the interviewers' public profiles.
- Write a question list per interviewer type, with at least two questions each that are specific to this company.
- During each round, note one thing they mentioned that you could follow up on.
- Ask different questions to each person, but ask one question (for example about the team's biggest challenge) to two people to compare answers.
- After the loop, write down what you learned to compare against other offers.
Impact: You finish every round with a strong, engaged impression, and you leave with enough real information to decide whether to accept an offer, rather than guessing.
Trade-offs
Use it when
- At the end of every interview round, including technical ones
- When a question would help you decide whether you want the job
- When you can follow up on something specific from the conversation
Avoid it when
- Questions answered on the company's homepage or in the job description
- Salary and benefits with an engineer interviewer mid-process
- Questions that sound negative or demanding, like 'how soon can I get promoted?' or 'how strict are working hours?'
Common mistakes
- Saying 'no questions', which can signal low interest or poor preparation.
- Asking generic questions you could have answered by reading the website.
- Asking every interviewer the same question, regardless of their role.
- Opening with salary, leave or remote work before showing interest in the job.
- Asking too many questions and running over time.
Interview questions
Quick revision
- Always have questions; prepare 5-6, ask 2-3.
- Tailor by interviewer: engineer, manager, leader, recruiter.
- Ask for real examples, not opinions about culture.
- Follow up on something they said.
- Great default: 'What does success look like in the first six months?'
- Great default: 'What is the team's biggest challenge this year?'
- Salary and benefits: recruiter or offer stage.
Check yourself
1. Which is the best question to ask an engineer interviewer?
2. Why is answering 'no questions' risky?
3. Which question gives the most honest view of culture?
4. Who is usually the best person to ask about salary and benefits?
Saved on this device. Create a free account to keep it on every device.
Practise this with Sam
A real mock interview, out loud, with an honest scorecard. Free to start.