Questions to Ask During an Interview: Role, Team and Next Steps
Choose useful interview questions about expectations, teamwork, pay and hiring steps. Includes follow-ups and guidance on interpreting answers without guessing.
On this page
Your questions can help you understand the role and decide whether it suits you. Prioritize what would affect your decision: the work, expectations, support, schedule, compensation or hiring process. You do not need to perform curiosity by asking questions whose answers you already understand.
The ten questions below are a practice menu, not a script or a proven way to win an offer. Each includes details to listen for and a possible follow-up. A pause, brief answer or nervous expression does not establish dishonesty; distinguish what the person said from what you still need to verify.
Ten useful questions, with follow-ups
Choose a few questions that fit the person you are meeting and the time available. Keep backups in case the conversation already covers them. Ask about the process if it remains unclear; there is no need to repeat information simply because it is on a checklist.
For additional preparation, Harvard’s interviewing guide includes employer-question prompts about role challenges, development and hiring timelines.
1. "Why is this role open?"
Ask whether the position is new, a replacement or a change in scope. Then explore what the team needs from the hire. Follow-up: “What has changed in the work since the role was first defined?”
The interviewer may be unable to discuss a previous employee’s circumstances. Growth does not prove funding is secure, and a departure does not by itself prove a management problem. Focus on the role’s current responsibilities and any unresolved questions.
2. "What would you need to see from me in the first six months to call this hire a success?"
Listen for priorities, how progress is assessed and what support is available. Follow-up: “Which outcome would come first, and what resources would help me deliver it?” Adjust the time period to the role.
If expectations are still developing, ask who will set them and when. An evolving role may suit some candidates and not others. Treat unclear priorities as something to investigate, rather than proof that no one has thought about the job.
3. "What's the hardest part of this job that isn't in the posting?"
This can reveal workload, dependencies or practical constraints that a short posting leaves out. Follow-up: “Can you describe a recent example and how the team handled it?”
A person may need time to think or may have limited knowledge of the role. Ask who else could provide detail. Do not treat “nothing comes to mind” as evidence that the person is concealing a problem.
4. "When the team disagrees on something that matters, how does it get resolved?"
Listen for decision-making responsibilities, how evidence is discussed and how a decision is communicated. Follow-up: “What happened the last time people preferred different approaches?”
A general answer such as “we are aligned” gives limited detail, so ask for an example. It does not prove that the team avoids conflict or that one person controls every decision.
5. "Who will I work with most outside the team, and where does that relationship get hard?"
Identify the main partner teams and the handoffs you would own. Follow-up: “Where do priorities most often need clarification, and who helps resolve that?”
A collaborative relationship can still have constraints, but friction is not mandatory evidence of honesty. Look for enough detail to understand your work rather than trying to make the interviewer admit a conflict.
6. "What separates someone who's been great in this role from someone who was just fine?"
Ask about observable work, feedback and performance criteria. Follow-up: “How are those expectations communicated and reviewed?” This can help distinguish a formal requirement from one manager’s preference.
Repeating the job description may simply reflect the agreed criteria. If you need more detail, ask for an example without requesting private information about named employees.
7. "What's the one thing this team has to get right this year?"
Listen for the team’s priorities and how this role contributes. Follow-up: “If priorities compete, how do you decide what to delay?” A team may reasonably have more than one important objective.
Ask what is approved and what is still proposed when that distinction matters. Connection to a priority does not guarantee resources, future funding or protection from reorganization.
8. "How do you like to stay informed about work in progress?" (hiring manager only)
Ask the prospective manager about check-ins, feedback, decisions and support when work is blocked. Follow-up: “What would communication look like during onboarding, and how might it change later?”
Daily contact can reflect onboarding or the work itself; “hands-off” can mean different things. Explore the actual expectations rather than treating either phrase as proof of micromanagement or neglect.
9. “What does development look like on this team?”
Ask about training, feedback, promotion criteria and opportunities to take on different work. Follow-up: “Could you share an anonymized example of how someone developed here?”
A new team may have no past promotion example, and an interviewer may protect employee privacy. Ask about the current process and constraints. A past promotion is useful context but does not promise your own progression.
10. "What are the remaining steps, and when will I hear from you?"
If it has not been covered, ask about the remaining stages, expected timing and appropriate contact for updates. Follow-up: “If the timeline changes, how will candidates be informed?”
Distinguish an estimate from a commitment. A clear explanation helps you plan, but it cannot guarantee a response date. A technical interviewer may need to refer process questions to recruiting.
Match the question to the person in the room
People have different knowledge and authority, and the boundaries vary by organization. Use the table as a starting point. If someone cannot answer, ask who can rather than assuming they are evasive.
| Conversation | Useful topics | Example | If more detail is needed |
|---|---|---|---|
| Recruiter or HR | Process, pay range, location and application logistics | What stages remain, and who can confirm the compensation range? | Ask who handles detailed team or technical questions. |
| Hiring manager | Responsibilities, expectations, support and decision authority | What should the hire prioritize first? | Ask who can confirm benefits or contractual details. |
| Potential teammates | Workflows, handoffs and daily collaboration | How does a typical workweek vary during a busy period? | Compare concrete descriptions respectfully without asking them to disclose private personnel matters. |
| Senior leader | Priorities, role scope and organizational dependencies | How does this role contribute to the current plan? | Ask the relevant owner for operational details outside their remit. |
Compare information from different conversations, but do not use facial expressions as a lie detector. If two accounts differ, ask a neutral clarification: “I heard weekly releases mentioned earlier; how does that work for this team?” Different roles, periods or definitions may explain the difference.
Clarify concerns without turning guesses into conclusions
A reposted role, a public review or an unclear answer can prompt a question, but none establishes what the workplace is like by itself. Ask about facts relevant to your decision and separate confirmed information from interpretation.
- “How has the team’s size or structure changed recently, and what prompted the change?”
- “How long has this particular vacancy been open, and has its scope changed?”
- “What changes should the person joining expect during the first few months?”
- “What resources or dependencies are most important for the team’s current work?”
Listen for a coherent explanation and whether the person can identify the limits of what they know. Confidentiality may prevent some answers. Nervous humor, pauses or communication style do not establish that a story is false.
If an important issue remains unresolved, record it and decide what further information you need before accepting. You can weigh uncertainty as part of your decision without diagnosing a team from one interaction.
Scope, headcount, and budget questions for senior roles
For a role involving leadership or ownership of a function, clarify the responsibilities and authority together. Ask which resources exist now, which are proposed and who makes decisions that affect your work. These questions can be relevant before the final round if the answers would determine whether you continue.
- “Which positions in the hiring plan are approved, and which are proposals?”
- “What spending decisions would this role own, and what approval process applies?”
- “Which decisions can I make directly, and which require consultation or escalation?”
- “What is the current reporting line, and are any changes planned?”
- “Who sponsors the work, and how are priorities maintained if leadership changes?”
A role may intentionally include designing a new process or building a team. If the answer is “we will define it together,” ask what authority, resources and time are available for that work. Do not assume the phrase has one meaning at every seniority level.
Seek written confirmation of material responsibilities and terms where possible. Distinguish an offer or approved arrangement from an informal expectation that may change.
Asking about salary, and when in the process to do it
If compensation affects whether you can continue, ask at an appropriate early opportunity: “Can you share the budgeted range and pay structure for this role?” If a range is posted, confirm the currency, location and whether it describes base pay or another measure.
A recruiter often handles this topic, but a manager or other contact may own it in a smaller organization. Ask who can provide the answer. There is no supported rule that raising pay with a hiring manager automatically costs an offer.
Likewise, discuss essential schedule, location or benefit needs when they affect your decision. You do not have to wait until the final round to discover a fundamental mismatch. Our salary-expectations guide discusses how to respond when asked for your own range.
Three topics to phrase clearly
The topics below are legitimate areas to clarify. The suggested wording aims to get a useful answer; it is not evidence that another phrasing inevitably causes rejection.
1. Public information that needs clarification
Review accessible information before the interview, then ask about anything unclear or relevant to the role. For example: “The website describes a focus on X. How does this team contribute?”
You can also ask a basic question if the available information is confusing, outdated or inaccessible. Do not pretend to understand a product just to avoid a question, and do not assume one basic question automatically ends an interview.
2. Progression and promotion
Ask how development and promotion decisions work, what evidence is considered and what opportunities currently exist. If progression is important to your decision, say so directly and respectfully.
Rather than asking for a guaranteed promotion date, clarify the process and constraints. A candid answer may be that progression depends on future business needs. Decide whether that uncertainty fits your goals.
3. Hours, flexibility and monitoring
These are reasonable working-condition questions. Ask for the current expectations: “What are the required hours and on-site days?” or “What monitoring tools are used, and what information do they collect?”
State any requirement you need to resolve and ask the appropriate contact to confirm it. Do not frame a candidate’s concern about flexibility or privacy as evidence that they are looking for loopholes.
What to ask on a final round that you couldn't ask earlier
Use later conversations to close the gaps that remain, especially material duties, resources, working conditions and offer terms. A final round is still an assessment; it does not mean the employer has already decided to hire you.
- “What would onboarding look like, and who would support the first few weeks?”
- “How will the final decision be made, and what is the expected timeline?”
- “Have any priorities or responsibilities changed since our first conversation?”
- “Is there anything about my experience that I could clarify?”
The clarification question is optional. It can create an opportunity to add relevant evidence, but an interviewer may not share evaluations during the process. If a gap is raised, respond accurately and briefly rather than arguing or inventing experience.
The STAR method can help organize a real example. It does not remove a genuine qualification gap or guarantee that the concern is resolved.
Take notes in a way that supports the conversation
Ask about any note-taking rules and use an approach that works for you, including agreed accessibility arrangements. Paper, typing or another permitted method may be suitable. Eye contact and note-taking style are not reliable measures of attention or interest.
Capture key facts and unresolved questions, then review them afterward. Do not record audio or use an automated meeting tool without the required permission. Keep sensitive information private.
A useful note format is: topic → what was said → what remains unclear → why it matters to me. For example, “On-site schedule → three days mentioned → fixed or flexible days unclear → affects commute.” This separates evidence from assumptions and helps you choose a follow-up question.
Use your resume and the posting to identify details you want to understand, then practice asking a few questions naturally. You can organize application documents in Roleframe, but generated suggestions need review. Do not let a tool invent employer facts, assess honesty from body language or predict a hiring decision.
Frequently asked questions
- Which five questions are a useful starting point?
Consider why the role is open, initial priorities, important challenges, available support and remaining hiring steps. Adapt the selection to what you need to know; it is an editorial starting point, not a proven universal top five.
- What should I ask if time is short?
Choose the most important unanswered issue and clarify next steps if needed. You do not have to complete a fixed number of questions. Ask whether another contact or follow-up would be appropriate for remaining details.
- How many questions should I prepare?
Prepare a short prioritized list with backups, then adapt to the conversation and available time. It is fine to clarify something already discussed if the answer was incomplete or unclear.
- Can I ask about salary early?
Yes, particularly when it affects whether continuing is practical. Ask the contact who can confirm the range and pay structure. A recruiter may handle this, but responsibilities vary; asking a manager is not automatically a hiring mistake.
- Is it bad if all my questions were already answered?
Not necessarily. You can say that the discussion covered your main questions and briefly identify what was useful. Clarify any remaining uncertainty rather than inventing a question purely to appear interested.
- Can I ask how candidates are evaluated?
You can ask about the format, relevant criteria, remaining stages and any automated assessment. The person may need to refer you to recruiting or may be unable to disclose some details. An incomplete answer alone does not prove an unfair or disorganized process.
Ready to start your new resume?
Writing a resume takes time, and even a polished one can miss what a hiring manager is looking for. Roleframe helps you build a clear, ATS-safe resume in minutes and tailor it to the job you want.
