What to Expect in a 30-Minute Interview: How Many Questions and What Each Part Tests
A 30-minute interview usually contains 5 to 8 questions from the interviewer, plus 2 or 3 that you ask at the end. The arithmetic is simple. About 5 minutes go to introductions and closing, about 5 to your questions, and the remaining 20 minutes are split among questions that take 2 to 4 minutes each to answer. Behavioral questions answered with a full example take closer to 4 minutes, so a behavioral screen fits 4 to 6 of them.
A 30-minute slot is almost always a screen. It is the first conversation with a recruiter, a hiring manager or one engineer, and its purpose is to decide whether you go on to a longer loop. It is not the place for a full system design question or a hard algorithm. The interviewer is checking a short list of things, and the rest of this page shows what those things are, minute by minute.
Minute by minute
| Minutes | What happens | Questions | What is evaluated |
|---|---|---|---|
| 0 to 3 | Introductions; the interviewer describes the role | 0 | Whether you joined on time with working audio and video |
| 3 to 6 | "Tell me about yourself" or "Walk me through your resume" | 1 | Whether you can summarize your background in under two minutes |
| 6 to 18 | Experience and role-fit questions | 3 to 4 | Whether your skills match the job description, and whether your answers include specific detail |
| 18 to 24 | Behavioral or situational questions | 1 to 2 | How you handle conflict, pressure and mistakes; how you work in a team |
| 24 to 28 | Your questions | 2 to 3 of yours | Whether you researched the company and are thinking about the job itself |
| 28 to 30 | Logistics and next steps | 0 to 1 | Salary range, notice period, availability, other processes |
The order changes with the interviewer, but the totals do not. A recruiter spends more of the middle block on logistics and motivation. A hiring manager spends it on your last two projects. An engineer replaces the middle block with one technical question.
How many questions, by interviewer
| Interviewer | Typical count | Where the time goes |
|---|---|---|
| Recruiter | 6 to 8 short questions | Background, motivation, salary range, availability, process |
| Hiring manager | 5 to 6 | Two or three deep questions on recent work, one or two behavioral |
| Engineer (technical screen) | 1 coding question plus 2 to 3 short ones | About 20 minutes on the coding question, a few minutes on your background |
In a 30-minute technical interview, plan for one coding question of easy to medium difficulty and nothing else. Twenty minutes is enough to state the approach, write about 20 to 30 lines, and trace one example. A second question appears only when the first one takes under 10 minutes.
How many behavioral questions
A screen with a behavioral focus fits 4 to 6 behavioral questions in 30 minutes. Each answer should take 2 to 3 minutes: the situation and task in two sentences, the actions in three or four, and the result in one, with a number where possible. An answer that passes 4 minutes costs you a question later, and the lost question is often the one on a topic where you are strong.
The most common ones in a short screen are "tell me about a time you disagreed with a teammate", "a project that went wrong", and "why are you leaving your current role". Prepare one story for each, and keep a fourth about a result you are proud of.
How many questions you should ask
Prepare 5 and expect to ask 2 or 3. Time is the limit, not interest. Good questions for a screen are about the work itself: what the team is building this quarter, what the first 90 days would involve, and what the next steps and timeline are. Save compensation questions for the recruiter, who expects them, and do not ask a hiring manager anything you could have read on the careers page.
The two mistakes that cost the most time
Long answers. The interviewer has a list and a clock. A four-minute answer to "tell me about yourself" removes one question from the list, and the removed one is usually the one you prepared for. Keep the opening summary under 90 seconds.
No questions at the end. "No, I think you covered everything" is taken as a sign of low interest. Even when the interviewer answered your prepared questions during the call, ask about next steps and the timeline.
How to Prepare
- Write a 90-second summary of your background and time it out loud. It answers the first question and leaves time for the rest.
- Prepare four stories in the situation, task, action, result format. Grokking the Behavioral Interview shows how to shape each one so that it takes 3 minutes, not 6.
- For a technical screen, practice easy and medium problems with a 20-minute timer. Grokking the Coding Interview groups them by pattern so that the approach is fast to name.
- Do one timed run with a stranger. A mock interview with a 30-minute limit shows whether your answers fit the clock.
- Know what happens after. Ask for the timeline in the last two minutes, and expect a longer loop of 3 to 5 rounds if the screen goes well.
GET YOUR FREE
Coding Questions Catalog
$99
$197
$72
