---
title: First Round Interview Questions and Answers (2026)
description: The first round is a filter, not a conversation. The eight questions that decide it, the three things that get you cut, and how to end it with the next step booked.
url: https://usegreenroom.app/blog/first-round-interview-questions-and-answers
last_updated: 2026-08-01
---

← Back to blog

Interview prep

# First round interview questions: three ways to get cut

August 1, 2026 · 12 min read

![First round interview questions and answers — recruiter screen guide from Greenroom, the AI mock interviewer](/assets/blog/first-round-interview-questions-and-answers-hero.webp)

The call was scheduled for thirty minutes. It ended at nineteen. He thought that meant it had gone well — efficient, no problems, friendly enough. It meant the recruiter had heard everything she needed by minute twelve, which was when he had answered "so why are you interested in us?" with "I'm looking for a good opportunity to grow" and she had stopped writing.

The most useful thing to understand about **first round interview questions** is that this round is a **filter, not a conversation**. The person on the call has ten or twelve more today. They are not trying to discover your depth; they are trying to establish, quickly, that you are not one of the three kinds of no. Almost nobody is rejected here for a technical reason.

## The three ways people actually get cut

- **You cannot summarise yourself.** A rambling four-minute answer to "tell me about yourself" is the single most common cause of a quiet no. It is the first question, it is entirely predictable, and it sets how everything after it is heard.
- **You cannot say why them.** A generic answer here reads as mass-applying, and mass-applying candidates convert badly, so recruiters filter for it deliberately.
- **You cannot state a number.** Notice period, expected compensation, earliest start date. Vagueness on logistics reads as either unserious or as someone who will be difficult later, and it is the easiest thing in the world to prepare.

Everything else in this guide is downstream of those three.

## The six beats

![Diagram of the first round interview structure — introduction, your background, why this role, a technical sanity check, logistics, and your questions](/assets/blog/first-round-interview-questions-and-answers-diagram.webp)

Twenty-five to forty minutes, six predictable beats. The recruiter has eleven more calls today, which is the single most useful fact about this round.

**One — their introduction.** Two minutes about the company and the role. Actually listen: they will name the team's priorities, and repeating one back later — "you mentioned the platform team is being rebuilt" — is disproportionately effective.

**Two — "tell me about yourself."** Ninety seconds, present-past-future, ending on why you are on this call. Not your life story, not your resume read aloud. Our [how to answer tell me about yourself](/blog/how-to-answer-tell-me-about-yourself-software-engineer) guide has the structure.

**Three — your background.** A guided walk through the resume with one project probed lightly. Have a two-minute version of your most relevant project, jargon-free, with one thing that went wrong in it.

**Four — "why this role / why this company."** The highest-failure question. Answer with something that could only be true of them — the product, the team's problem, something they shipped, the domain — plus one line on why it fits what you want next. Our [why do you want to work here](/blog/why-do-you-want-to-work-here) guide covers this properly.

**Five — the sanity check and logistics.** A light technical confirmation that your resume is real, then notice period, location and expectations. Have all three as actual numbers.

**Six — your questions, and the close.** Two specific questions, then explicitly ask what happens next.

## The eight questions you will get

Prepare these and you have prepared the round:

- **"Tell me about yourself."** 90 seconds.
- **"Walk me through your current role."** What you own, the team, the stack, and one thing you shipped.
- **"Why are you looking to leave?"** Forward-looking, never bitter. Our [why are you leaving your job](/blog/why-are-you-leaving-your-job) guide covers the framing.
- **"Why this company?"** Specific, or you are cut.
- **"Tell me about a project you're proud of."** Two minutes, one failure included.
- **"What's your notice period?"** A number. In Indian IT, say whether buyout is possible.
- **"What are your compensation expectations?"** A range in fixed pay, with a reason. Our [what are your salary expectations](/blog/what-are-your-salary-expectations) guide covers the wording and our [CTC vs in-hand salary](/blog/ctc-vs-in-hand-salary-india) guide covers why fixed matters.
- **"Do you have other processes running?"** Honest, with your timeline. Our [do you have any other offers](/blog/do-you-have-any-other-offers-interview-answer) guide covers all four positions.

## The technical sanity check

If the first round is with a recruiter, expect surface-level confirmation rather than depth: which parts of that stack you have used, what you did in that project, how long you have worked with a given technology. The trap is over-answering — a four-minute architecture explanation to a non-technical recruiter is a misread of the room and it reads as poor communication.

If the first round is with an engineer or hiring manager, it goes deeper: one real technical question, or a discussion of a system you built. Ask the recruiter in advance who the call is with. It is a normal question and it changes how you prepare.

## The close, which almost nobody does

The last ninety seconds are free and most candidates waste them.

Ask two specific questions — about the team, the roadmap, or what success looks like in six months. Not "what's the culture like." Our [questions to ask at the end of an interview](/blog/questions-to-ask-at-end-of-interview-software-engineer) guide has better options.

Then state your interest plainly and ask for the next step: *"This sounds like a good fit — the platform work in particular is what I want to be doing. What's the next stage, and what's the timeline?"* That sentence does two jobs: it puts your interest on record for the internal writeup, and it gets you a date you can follow up against.

**The core truth:** the first round is decided by three predictable things — a tight self-summary, a specific reason for wanting this job, and confident numbers on logistics. All three are entirely preparable, and the candidates who lose here almost always lost to a lack of preparation rather than a lack of ability.

## Practical setup

- **Ask who the call is with**, and for how long.
- **Take it somewhere quiet with good audio.** Our [telephonic interview tips](/blog/telephonic-interview-tips) guide covers phone-specific issues.
- **Have your resume open**, plus one page of notes: your 90-second answer, your why-them line, and your three numbers.
- **Stand up if you can.** It genuinely changes how your voice carries on a call.
- **Send a short thank-you the same day.** Three lines. Our [thank you email after an interview](/blog/thank-you-email-after-interview) guide covers it.

## Where each option actually helps

- **The job description** — the source of your why-them answer. Read it twice and pull two specifics.
- **The company's own site and recent announcements** — fifteen minutes, and it is the difference between a specific answer and a generic one.
- **Your recruiter** — will usually tell you the format and who you are meeting if you ask.
- **ChatGPT** — good for generating likely questions from the job description in ten minutes. Its limit is that it lets you type answers, and this round is entirely spoken.
- **Greenroom** — the spoken layer. [Ari, the AI interviewer](/) runs the full round in order, so the ninety-second answer gets rehearsed against a clock rather than in your head. Honest tradeoff: it does not know that company's specifics — the job description and fifteen minutes of reading do.

## Frequently asked questions

### What questions are asked in a first round interview?

Eight recur almost every time: tell me about yourself, walk me through your current role, why are you looking to leave, why this company, tell me about a project you are proud of, what is your notice period, what are your compensation expectations, and whether you have other processes running. The round usually runs 25 to 40 minutes across six predictable beats, ending with your questions and the next step.

### What gets candidates rejected in the first round?

Three things, almost none of them technical. Being unable to summarise yourself, since a rambling four-minute answer to the opening question sets how everything after it is heard. Being unable to say why this company specifically, because generic answers read as mass-applying and those candidates convert badly. And being vague on logistics — notice period, expected compensation, start date — which reads as unserious and is the easiest thing to prepare.

### How long is a first round interview?

Typically 25 to 40 minutes. A call ending early is not necessarily a good sign — it often means the interviewer heard what they needed sooner than expected, which can cut both ways. The structure is usually their introduction, your self-summary, a walk through your background, why this role, a light technical or logistics check, and then your questions.

### How technical is the first round?

It depends who the call is with, which is worth asking the recruiter in advance. With a recruiter, expect surface-level confirmation that your resume is real — which technologies you have used and for how long — and be careful not to over-answer, because a four-minute architecture explanation to a non-technical recruiter reads as poor communication. With an engineer or hiring manager it goes deeper, usually one real technical question or a discussion of something you built.

### How do you end a first round interview well?

Ask two specific questions about the team, roadmap or what success looks like in six months, then state your interest plainly and ask directly what the next stage is and what the timeline looks like. That sentence puts your interest on record for the internal writeup and gives you a date to follow up against. Most candidates waste these final ninety seconds, which are free.

### Should you discuss salary in the first round?

Usually yes, because recruiters raise it deliberately to avoid wasting everyone's time on a mismatch. Give a range in fixed pay rather than total CTC, with a brief reason tied to the role and market rather than to your current package. Being vague here is one of the three things that reliably gets candidates cut, so decide your number before the call rather than improvising it.

This round is decided in the first ninety seconds, by an answer most people have only ever said in their head. [Greenroom](https://usegreenroom.app/) runs it in order with Ari, against a clock. Free to start. Curious how it works? See [how AI mock interviews work](/blog/ai-mock-interview).