Focused preparation
Questions to ask at the end of an interview
“Have you got any questions for us?” can arrive just as you start to relax. A list of impressive-sounding questions is easy to prepare. A few that help you understand the job are more useful.
Ask about the work you would do, how the team makes decisions and what you would need to succeed. Choose questions whose answers could affect whether you want the role. Keep a few alternatives ready, then use what you have heard during the interview to decide which ones still matter.
Start with the work you would actually do
A job description can list responsibilities without showing which ones take up most of the week. These questions help turn broad expectations into something more concrete.
- “What would you most want the person in this role to make progress on in the first three months?” Listen for priorities and how much is already decided. If the answer is broad, ask which piece would come first.
- “What is the hardest part of the role at the moment?” This leaves room for an honest discussion about constraints, workload or unfinished work.
- “What prompted you to hire for this position?” A new role and a replacement can come with different expectations. Ask how responsibilities will be shared if the scope is still taking shape.
You do not need to ask all three. If the hiring manager has already explained the priorities, follow up on one of them instead of starting the list again.
Ask how the team works when things are difficult
“What's the culture like?” may produce an answer that is hard to evaluate. Ask about a recent situation when you want to understand a working habit.
- “Can you give me an example of how the team handled a change in priorities recently?” Listen for who made the decision, what stopped and how people were told.
- “How do people raise concerns about a deadline or a proposed approach?” You can follow up by asking what happens after someone raises a concern.
- “When two teams disagree about a decision, how is it usually resolved?” This can be useful when the role involves work across several functions.
For an engineering role, you might make the question more specific: “How does a change move from code review to production?” or “How are incidents and on-call responsibilities shared?” Use language you are comfortable discussing. There is little value in asking a complicated technical question just to sound knowledgeable.
Find out what support and feedback look like
Support matters whether you are joining your first team or taking on a more senior role. The details will differ, so choose a question that fits your situation.
- “What does onboarding look like, and who would I work with during the first few weeks?” This helps you understand how you would learn the systems, expectations and people around the role.
- “How would my manager and I review progress?” Ask what those conversations cover, rather than assuming a formal appraisal tells the whole story.
- “Could you share an example of someone developing a new skill within the team?” A recent example may tell you more than a general statement that development is encouraged.
Listen for how support works in practice. “There is a training budget” is useful information, but you may also want to understand how time for learning is agreed.
Use what you heard to ask a better follow-up
Here is a fictional exchange showing how a prepared question can become a conversation:
Interviewer: “The main priority is making releases more predictable.”
Candidate: “You mentioned earlier that several teams contribute to each release. Where does the uncertainty tend to come from, and which part would this role help with?”
The candidate connects two details and asks about their own responsibilities. They have not assumed that the problem is poor planning or offered a solution without understanding the situation.
If an answer remains vague, try one neutral follow-up: “What would that look like in a typical week?” Treat the reply as information to consider alongside the rest of the process. One interviewer may not know every detail, particularly in an early screening call.
Ask practical questions when you need the answers
Pay, working location, hours and travel can determine whether a role is workable for you. Ask the recruiter or appropriate contact when you need clarity, especially if an unanswered detail would affect whether you continue. You do not need to wait until the final stage to raise a genuine constraint.
Phrase the question around the information you need: “The advert mentions hybrid working. How many days are normally spent in the office, and are those fixed days?” That gives you more to work with than “Are you flexible?”
Before you finish, ask about the remaining stages and the expected timing if those have not been explained. There is no need to repeat a question just because it is on your prepared list.
Build a shortlist you can actually use
Take the job description and mark the things you still cannot picture. Turn the most important gaps into questions. Prepare a small reserve in case your first choices are answered during the conversation.
If there is time for only one question, choose the answer you most need. If everything has already been covered, say what you found useful and check the next steps. You can explain that your prepared questions were answered without inventing another one on the spot.
Afterwards, write down what you heard while it is fresh. Separate the employer's answer from your interpretation, and note anything you still need to clarify. These notes are for deciding whether the role fits you as well as preparing for another round.
For the earlier part of the conversation, practise your opening introduction and a couple of specific experience-based answers. You will then have something useful prepared for both sides of the interview.
Further reading: the National Careers Service interview tips recommends preparing your own questions and checking when you will hear back. The question selection and examples above are MockReps guidance.