| Situation | Who is in the room | Lead question to ask | Planning use |
|---|---|---|---|
| Early screen | Recruiter | What does the interview process look like, and how soon will feedback arrive? | Settles format and timeline before you spend preparation time on the wrong thing. |
| Manager round | Hiring manager | What are the main challenges and KPIs for this role? | Shows whether the expectations match the work you want to do. |
| Team rounds | Engineers | How does the team work together day to day? | Lets you compare the job description with daily practice. |
| Leadership conversation | Senior leader or executive | Where is the team or product heading? | Helps you judge whether the direction suits your own plans. |
| Live or remote round | Interviewer during a task | Can you clarify the requirements of the problem? | Keeps questions about the task separate from questions about the employer. |
Columbia’s career education team describes the technical interview process as a series of rounds, and Formation’s guide to recruiter screens and hiring manager interviews explains what each stage is for.
The best questions to ask in a tech interview depend on who is across the table. Ask the recruiter about process, the manager about expectations and growth, engineers about daily work, and leaders about direction.
This guide is one part of our wider career advice for tech professionals. Use it to build a short, role-specific list for each conversation rather than one generic set of questions.
When you are screening with a recruiter
A recruiter conversation is the cheapest place to remove uncertainty about the process. Formation describes recruiter screens and hiring manager interviews as the stages where a company decides whether it trusts you enough to invest more time, so keep your questions practical and brief here.
Ask about format and logistics
Columbia’s career services advice is direct: if you are not sure of the format, ask the recruiter. Technical formats can include writing code in real time, an on-the-spot coding test, a whiteboard problem or a panel presentation, and each needs different preparation. Knowing which one is coming lets you spend your time well, and our guide on how to prepare for a coding interview covers the practice side.
- Round structure: ask which rounds follow the screen and what each one covers, so you can match your preparation to it.
- Who you will meet: ask whether later conversations are with engineers, managers or both, because that determines which of the questions below you will need.
- Feedback timing: ask how soon you can expect to hear back after each stage, so you can plan around other applications.
Ask about the timeline
Columbia notes that the tech interview process may take several weeks and involve multiple interviews. A recruiter can tell you how this particular employer schedules them. If you are weighing other offers, this is the right person to ask, and it is a reasonable question to raise at the end of the first call. A vague answer on timing is worth noting before you commit to a long process.
When you meet the hiring manager
Columbia’s guidance says that after the initial phone screening you might meet with engineers and managers in the days or weeks to come. The hiring manager round is where your questions about the job itself carry the most weight, because the manager owns the role. Formation notes that hiring managers dig into your past work to understand how you operate in real situations, so expect your questions to be read as a sign of how you think about the work.
Ask about expectations and success
Questions about KPIs for the role and the challenges in it appear among the questions candidates commonly ask, according to Woven’s roundup of candidate questions. They suit almost every candidate. If the manager answers with specific outcomes, you can picture the work. If the answer stays abstract, ask for an example of what a strong first period in the role looks like.
Ask about growth and feedback
Formation says that at junior and mid levels the focus is on clear communication, growth and initiative, while at senior levels the emphasis moves toward leadership, influencing direction and mentorship. Shape your questions to match that stage.
- Junior and mid-level candidates: ask how feedback is given, how someone in this role usually develops and what support exists for learning.
- Senior candidates: ask how engineers influence technical direction and how mentoring is expected to fit alongside delivery.
Wait on this topic if the manager has not yet described the role itself. Growth questions land better once you understand the day-to-day scope.
Ask how the team works with other functions
Formation lists how you partner across functions and how you communicate technical decisions among the things hiring managers assess. Turn that around and ask the manager how engineers work with product, design or other teams, and how technical decisions are communicated. The answer tells you whether the role is mostly heads-down or involves regular coordination, which may or may not suit you.
When engineers join the conversation
Engineers can describe daily working life in a way that a manager summary cannot. Use these rounds for questions about practice and collaboration, and save role-scope and career-path questions for the manager.
Ask about day-to-day collaboration
Ask how the team plans work, how engineers hand over problems to each other and what a typical week looks like. Ask what the engineer would change about the way the team works if they could. Engineers tend to answer the second question candidly, and the answer is a useful read on the team’s culture.
Ask about the engineering process
Questions about how code is reviewed, how releases are handled and how problems are investigated when something goes wrong give you a view of the standards the team keeps. Phrase them as curiosity about the process rather than a test of the interviewer. If an engineer has just watched you solve a problem, follow up on how the team deals with trade-offs similar to the one you discussed.
When a senior leader is in the room
A conversation with a director, vice president or executive is usually short and broad. Questions about individual tickets or tools will not fit. Aim at direction and priorities instead.
Ask about direction and priorities
Good questions here are where the company expects the team or product to be in the future, what the organisation is prioritising and how this role contributes to that. They suit candidates deciding whether to join a team for the longer term, and they pair well with the senior-level emphasis on influencing direction that Formation describes. Skip detailed questions about process or tooling, which engineers and the manager are better placed to answer.
When the round is live or remote
Columbia advises candidates to be comfortable asking questions and asking for clarification, and says most interviewers want to hear you explain your thought process while working through a problem. During a live coding or whiteboard task, that means asking about requirements, not about the employer. Hold questions about the team for the end of the session.
Separate task questions from employer questions
Ask clarifying questions while you work, then switch to questions about the role once the problem is finished. Mixing the two can distract from the task, and the interviewer will often reserve time for your questions at the end anyway.
Keep remote questions short
On a video call, it is harder to read the room, so ask one clear question at a time and pause for the answer. If the answer raises a follow-up, ask it directly instead of moving to the next item on your list.
Putting your list together
Woven describes an interview as a two-way street, so write your list before each round and choose only the questions that fit the person you are meeting. Prioritise the few that would change your decision about the job, and drop any the interviewer has already answered.
Match the question to the person
- Recruiter: process, format, timeline and when to expect feedback.
- Hiring manager: role expectations, challenges, KPIs, growth and cross-functional work.
- Engineer: daily collaboration, review practice and how the team handles problems.
- Senior leader: direction, priorities and where the role fits.
Adjust for where you are in your career
If you are early in your career, lean on questions about feedback, learning and support, and read our guide on how to get an entry level tech job for the wider search. If you are more experienced, shift toward influence, mentorship and technical direction.
Frequently asked questions
| Question | Answer |
|---|---|
| Do my questions matter if the employer is the one assessing me? | Yes. Woven describes an interview as a two-way street, so your questions help you evaluate the employer as well as show your interest. |
| Is it fine to ask for clarification during a technical problem? | Yes. Columbia’s career education team advises candidates to be comfortable asking questions and asking for clarification, and to explain their thought process aloud while solving the problem. |
| What if I meet several people in one process? | Columbia notes that later rounds may bring engineers and managers, so keep a separate short list for each. Ask managers about the role and engineers about how the work gets done, and avoid repeating the same question to everyone. |
