Every interviewer asks 5 questions. The exact wording varies — the structure is identical. Across hundreds of live rounds at FAANG-tier companies, the same 5 questions account for roughly 80% of the live-round content. Master the 5 questions, and you handle 80% of the interview. The remaining 20% is technical depth (covered in the STAR framework post).
This post is the 5 questions, the framework for each, sample answers, and the common mistakes candidates make. The First Day AI Interview Intelligence tool surfaces these 5 questions for any JD, with destination-domain-specific sample answers generated from your resume.
Question 1: Tell me about yourself
The framework: Present → Past → Pivot → Future (90 seconds)
The interviewer is asking 3 questions in this prompt:
- Can this candidate communicate clearly?
- Does this candidate have relevant experience?
- Is this candidate self-aware about their career trajectory?
The framework:
- Present (15 sec): "I'm a [current role] at [current company]. I work on [current focus]."
- Past (30 sec): "Before that, I was at [previous role] where I [key achievement]. I graduated from [school] in [year] with [degree]."
- Pivot (30 sec): "What I love about [destination domain] is [reason]. That's why I'm excited about [destination role type]."
- Future (15 sec): "In the next 5 years, I want to [aspiration]. This role at [company] looks like the right fit because [reason]."
Sample answer (a senior mechanical engineer applying for software):
"I'm a senior mechanical engineer at [company], where I work on heat-transfer modeling for industrial systems. Before that, I was at [previous company] where I led a 6-person cross-functional team across 3 design reviews. I graduated from IIT Bombay in 2018 with a B.Tech in Mechanical Engineering.
What I love about software is the scale — a single system serving millions of users. In mechanical engineering, the best work ships a few hundred units; in software, the same code can serve millions. That's the kind of leverage I want to build.
In the next 5 years, I want to be a senior software engineer at a company building infrastructure that matters. This role at [company] looks like the right fit because [reason tied to the company's product or mission]."
Common mistakes:
- The autobiography. "I was born in [city], I went to [school], my parents are [profession]." The interviewer doesn't care. Skip the first 18 years.
- The full resume readout. "I worked at [company] from [year] to [year] doing [X]." This is what the resume is for. The "tell me about yourself" question is a synthesis, not a recitation.
- The rambling answer. Going over 90 seconds. The interviewer's first impression is the most memorable. Make it tight.
- The fake interest. "I've always wanted to work in software." If your resume is 5 years of mechanical engineering, the interviewer knows you haven't always wanted to work in software. The honest pivot is more credible.
Question 2: Why this role?
The framework: Skill + impact + company-mission match (60-90 seconds)
The interviewer is asking 3 questions:
- Does this candidate understand what the role is?
- Is this candidate motivated by the right things?
- Will this candidate be effective in the role?
The framework:
- Skill (20 sec): "I see this role is for [role type]. My background in [source skill] maps well — I've spent 8 years on [specific thing]."
- Impact (20 sec): "What excites me is the impact — the team is responsible for [specific product or system], and that's the kind of work I want to do."
- Company-mission match (20 sec): "I also see [company's mission or values], which resonates with [personal reason]."
Sample answer (a senior mechanical engineer applying for a software role):
"I see this role is for a senior software engineer on the [team] team. My background in heat-transfer modeling maps well — I spent 8 years at [company] building predictive models in MATLAB, which is the same kind of work as a software ML engineer, just with different tools.
What excites me is the impact — your team owns the [specific system], and that's the kind of large-scale engineering I want to do. Mechanical engineering caps at hundreds of units; software caps at millions of users.
I also see [company's mission], which resonates with [personal reason]."
Common mistakes:
- The generic answer. "I want to work at a great company with smart people." The interviewer has heard this 1,000 times. Specificity wins.
- The "I need a job" answer. "I'm looking for a role where I can grow." This is honest but unmemorable. The interviewer's job is to find the candidate who will be most effective, not the one who needs it most.
- The over-researched answer. "I read your CEO's last 14 tweets, your last 6 quarterly earnings calls, and your last 24 Glassdoor reviews." This is creepy. The research should inform your answer, not replace your judgment.
- The role-mismatch answer. "I'm excited about this role because it's a great opportunity to learn." The interviewer's question is "why this role," not "why are you here." Focus on the role, not your motivation.
Question 3: Why this company?
The framework: Specific product/team + recent news + your fit (60-90 seconds)
The interviewer is asking 3 questions:
- Has this candidate done their homework?
- Does this candidate understand the company's strategy?
- Will this candidate be motivated by the specific work this company does?
The framework:
- Specific product/team (20 sec): "I've been following [product or team] for [duration]. The recent [feature or initiative] is the kind of work I want to do."
- Recent news (20 sec): "I also saw the [news, e.g., funding round, product launch, executive hire]. That tells me [interpretation]."
- Your fit (20 sec): "My background in [source skill] fits well with what the team is doing — I've [specific experience] that maps to [team's current challenge]."
Sample answer:
"I've been following [product] for about 6 months. The recent [feature] launch is the kind of work I want to do — the team is building infrastructure for [use case], and that's exactly the problem space I've been wanting to work in.
I also saw the [news, e.g., funding round or product launch] — that tells me the company is investing in [area], which is a strong signal for the next 18 months.
My background in heat-transfer modeling fits well with what the team is doing — I've shipped 4 models in production that map to the [team's current challenge]. I'd be ready to contribute from week 1."
Common mistakes:
- The "great company" answer. "I admire your company's culture and values." The interviewer knows. They work there. Get specific.
- The "I just want any job" answer. "I applied to a lot of roles and yours seemed interesting." The interviewer's question is "why this company," not "why did you apply." Be specific.
- The product-mismatch answer. "I'm excited about the company's role in [adjacent area]." The interviewer's question is about the company, not the area. If you don't know the company, don't pretend.
- The salary-first answer. "I see this role pays [range], which is what I'm targeting." Never mention salary in the first 3 questions. The interview is not the time.
Question 4: Tell me about a challenge you overcame
The framework: STAR (90-120 seconds)
The interviewer is asking 3 questions:
- Can this candidate structure a story?
- Does this candidate have real challenges to draw from?
- Is this candidate someone the team would want to work with?
The STAR framework:
- Situation (15 sec): "At [company], I was on a [project] where [context]."
- Task (15 sec): "I was responsible for [specific responsibility], and the team needed [outcome]."
- Action (45 sec): "I [specific actions you took]. The key insight was [insight]. I worked with [team or stakeholder] to [specific collaboration]."
- Result (30 sec): "We [outcome]. The measurable impact was [numbers]. The team [team outcome]."
Sample answer (a senior mechanical engineer applying for software):
"At [company], I was the lead engineer on a 6-month client engagement where we built a heat-transfer prototype for an industrial sensor system. The system needed to maintain a 0.4% tolerance across 14 sensors, and our first 6 iterations were off by 1-2%.
I was responsible for the calibration methodology, and the team needed the system to pass QC before the client's Q4 production deadline.
I redesigned the calibration approach: instead of calibrating each sensor independently, I built a multi-sensor calibration that accounted for cross-sensor interactions. I worked with the firmware team to integrate the new calibration into the device's runtime, and with the QC team to validate the tolerance on 3 production runs.
The final system passed QC at 0.4% tolerance on all 14 sensors. The client took the prototype to production in Q4, and the system has been in production for 18 months with zero calibration drift. The team adopted the multi-sensor calibration as the standard for the next 6 products."
Common mistakes:
- The "I" monologue. The story is about you, but the result is about the team. "I did X. I did Y. I did Z." The interviewer is testing for team-orientation. Use "we" for the result; use "I" for the actions.
- The no-numbers story. "I worked on a project. We had some challenges. We figured it out. The result was positive." The interviewer's question is testing for specificity. Numbers anchor the story.
- The "I saved the day" story. "There was a crisis, and I single-handedly resolved it." Hero stories read as red flags. The interview is testing for collaboration, not heroism.
- The "I had no control" story. "I was in a tough situation and there was nothing I could do." Passivity reads as a red flag. The interview is testing for agency. Take responsibility for your actions.
Question 5: Do you have any questions for me?
The framework: 3 prepared questions (5 minutes total)
The interviewer is asking 3 questions:
- Is this candidate genuinely interested in the role?
- Has this candidate thought carefully about what they want to know?
- Will this candidate be a good colleague (i.e., ask good questions)?
The framework: 3 prepared questions, in priority order:
-
Question about the team or the work (90 sec answer expected):
- "What does the team think the biggest opportunity is in the next 6 months?"
- "What does success look like for this role in the first 90 days?"
- "What are the biggest challenges the team is facing right now?"
-
Question about the interviewer's experience (60-90 sec answer expected):
- "What brought you to [company]?"
- "What's something about the team that isn't on the public docs?"
- "What's a recent decision the team made that you're proud of?"
-
Question about growth or next steps (60-90 sec answer expected):
- "What does the career path look like for someone in this role?"
- "What's the typical next role after this one?"
- "How does the team think about internal mobility?"
Common mistakes:
- The "no questions" answer. "I think you've covered everything." This is a missed opportunity. The interviewer expects 2-3 questions. "No questions" reads as disengaged.
- The salary question. "What's the salary for this role?" Never in the first interview. The interviewer's question is "do you have questions about the work," not "do you have questions about the offer."
- The over-easy questions. "When can I start?" / "What does the company do?" These are red flags. The candidate should have done basic research.
- The too-narrow question. "What version of React does the team use?" Specific tactical questions read as either (a) you're optimizing for a specific stack, not the role, or (b) you're trying to get the interviewer to reveal interview questions. Both are bad signals.
The 5 questions as a system
The 5 questions are not independent. They're a system. The "tell me about yourself" answer sets up the "why this role" answer, which sets up the "tell me about a challenge" answer, which sets up the "do you have any questions" answer.
The chain:
- "Tell me about yourself" → establishes the candidate's background
- "Why this role" → connects the background to the role
- "Why this company" → connects the role to the company
- "Tell me about a challenge" → proves the candidate has done the work
- "Do you have any questions" → tests the candidate's curiosity
If the chain breaks (e.g., the "tell me about yourself" answer is unrelated to the "why this role" answer), the interview reads as a sequence of unrelated statements. The interviewer leaves without a clear picture of the candidate.
If the chain holds, the interview reads as a coherent narrative. The interviewer leaves with a clear picture of who the candidate is and why they're a fit.
The First Day AI Interview Intelligence tool generates a 90-second STAR story for each of the 5 questions, calibrated from your resume. The stories are consistent across the 5 questions — the chain holds.
Common meta-mistakes
Mistake 1: The memorized answer.
A 90-second answer that sounds memorized reads as memorized. The interviewer's intuition catches the lack of spontaneity. The fix: practice the answer, but in the interview, deliver it as if you're saying it for the first time. Use the framework, not the script.
Mistake 2: The rambling answer.
A 90-second answer that goes 3 minutes is a missed opportunity. The interviewer's attention drifts. The fix: time yourself. Cut at 90 seconds even if you have more to say.
Mistake 3: The too-technical answer.
A 90-second answer that goes deep on technical detail is a missed opportunity. The interviewer's question is "tell me about yourself," not "explain your last 4 projects in detail." The fix: stay at the high level. Save the technical detail for the technical questions.
Mistake 4: The too-shallow answer.
A 90-second answer with no specifics is a missed opportunity. The interviewer's question is testing for substance. The fix: include 1-2 specific numbers or examples.
Mistake 5: The negative answer.
A 90-second answer that mentions what you didn't like about a previous role reads as a red flag. The interviewer's question is "tell me about yourself," not "tell me about your grievances." The fix: keep the focus forward, not backward.
How to practice the 5 questions
The 5 questions are pattern-matched, not memorized. The pattern is:
- 90 seconds each
- 1-2 specific numbers per answer
- 1 STAR story in Question 4
- 3 prepared questions in Question 5
- Consistent chain across the 5 answers
The 2-hour practice session:
Hour 0-1: Write out the framework for each of the 5 questions. Use the templates above. For Question 4, write out the STAR story. For Question 5, list 3 prepared questions.
Hour 1-2: Run 5 mock interviews, one per question. Time each. Get feedback from a peer or a coach. Iterate on the answers.
Repeat the 2-hour practice session 3-5 times across the week before the interview. The pattern is internalized by session 5.
The First Day AI Interview Intelligence tool generates sample answers for each of the 5 questions, calibrated from your resume. The tool is the practice partner. The deliverable is the candidate's own voice in the live interview.
FAQ: The 5 questions
Are these really the 5 most common questions?
Yes. Across hundreds of live rounds at FAANG-tier companies, the same 5 questions account for roughly 80% of the live-round content. The exact wording varies; the structure is identical.
What if the interviewer asks a 6th question that's not on this list?
The 6th question is usually a domain-specific or technical question. The framework for handling any unexpected question is:
- Pause (1-2 sec) — don't fill the silence.
- Acknowledge — "That's a great question, let me think."
- Answer using a related framework (STAR, the 5-question framework, or a domain-specific framework).
- If you don't know, say so. "I haven't worked on that specific thing, but here's how I'd approach it" is a strong answer.
What if the interviewer doesn't ask any of these 5?
The interviewer may skip some and ask others. The most important question is "tell me about a challenge you overcame" — if the interviewer asks only one question, it's usually that one. The STAR framework is the highest-leverage framework to master.
How long should each answer be?
90-120 seconds for the open-ended questions. 60-90 seconds for the more focused questions. 5 minutes for "do you have any questions." The total interview is typically 45-60 minutes, with 5-10 minutes per question.
What if I forget the framework in the moment?
The framework is a scaffold, not a script. In the moment, you'll say what you know. The interviewer's evaluation is based on substance, not structure. If you can deliver a clear answer with specifics, the framework is satisfied. The framework is a practice tool, not a live-rubric.
What if the interviewer interrupts me?
A 30-second interruption is a signal that the answer is too long. Stop. Acknowledge the interruption. Ask "would you like me to keep going, or would you like to ask a follow-up?" The interruption is a redirect; respect it.
What if I don't have a STAR story for Question 4?
The 90-day plan includes 5-10 mock rounds. The first mock round is "develop the STAR story." If you don't have a STAR story, the story is the problem. Build the story before the live round.
What if I'm not sure about the right answer to Question 5 (do you have any questions)?
3 prepared questions is the rule. The questions should be:
- 1 question about the team or the work
- 1 question about the interviewer's experience
- 1 question about growth or next steps
If you don't have a question, say "I have a few but I'd love to ask them in the next round when I have more context." The interviewer respects the honesty.
What if I'm asked the same question by multiple interviewers in the same loop?
This is normal. Each interviewer is asking the question independently. The same answer, delivered in the same way, is the right answer. The 5 questions are the 5 questions; the chain is the chain. Each interviewer is testing the same things.
What if the interviewer's style is very different (e.g., rapid-fire vs. conversational)?
Match the style. If the interviewer is rapid-fire, deliver short answers. If the interviewer is conversational, deliver longer answers. The 5 questions are the 5 questions; the style is the style. The interviewer's style is a signal; matching it is a sign of social fluency.
What if the interview is going badly?
The interview is a 2-way evaluation. If the interview is going badly, the candidate has 2 options: (1) finish the interview and learn from it, or (2) gracefully exit if the role is clearly not a fit. Most candidates finish and learn. The 5 questions are a practice tool; the next interview is the improvement.
Why the same five questions come up across Indian IT
The repetition is not laziness — it is a shared screening rubric. Indian service companies and product companies both draw their first-round questions from the same competency buckets: project clarity, conflict handling, learning agility, ownership, and a salary-expectations check. A candidate who has answered the five buckets well can walk into most first rounds in Bengaluru, Hyderabad, Pune or Chennai and sound prepared rather than rehearsed.
The one that catches candidates out is the expectations question, because it is asked differently in India: "what are you currently drawing" carries more weight than the number you quote, and a candidate who has not costed their own CTC — including variable pay and the joining bonus — negotiates from a position they cannot defend.
Related reading
- STAR framework: 12 real answers — the full breakdown of the answer structure referenced throughout this post.
- How to negotiate salary in India — because the expectations question is the one that decides offers.
- AI interviewer copilot without getting caught — the honest version of live-round AI help.