Question 1

What is the STAR method and how do I use it without sounding rehearsed?

Accepted Answer

Situation, Task, Action, Result: set the context in one or two sentences, state what you specifically had to do, spend most of the answer on your actions, and end with a concrete outcome. Keep it to about two minutes. The common imbalance is a ninety-second Situation and a ten-second Action. The interviewer is assessing what *you* did, so use "I" rather than "we" for your own contribution, and quantify the Result whenever you honestly can.

Question 2

How many stories should I prepare, and which ones?

Accepted Answer

Five to six flexible stories cover almost every question: a technical challenge you solved, a conflict or disagreement, a failure and what changed afterwards, a time you led or took initiative, a time you learned something quickly, and a project you are proud of. Prepare stories, not answers. One good project story can be told as a technical-challenge answer, a teamwork answer or a learning answer depending on which part you emphasise. Memorising per-question scripts breaks the moment the wording changes.

Question 3

How should I answer "tell me about a time you failed"?

Accepted Answer

Pick a real failure with genuine consequences, own your part in it without blaming others, explain what you learned specifically, and give evidence you applied that lesson afterwards. The evidence is what the question is actually testing. Two answers score badly: the humble-brag ("I work too hard") because it dodges the question, and the catastrophic failure with no reflection. A missed deadline because you did not flag a blocker early, followed by adopting earlier status updates, is a strong, honest answer.

Question 4

What are Amazon's leadership principles and how are they used in interviews?

Accepted Answer

Amazon has 16 principles — Customer Obsession, Ownership, Invent and Simplify, Bias for Action, Dive Deep, Deliver Results and others. Each behavioural question maps to one or two, and interviewers score your evidence against them explicitly. Amazon interviewers take structured notes and probe with follow-ups ("what data did you look at?", "what would you do differently?"), so shallow stories collapse. Prepare stories with real detail — numbers, decisions, alternatives you rejected — and know which principles each maps to. Dive Deep and Ownership are the most commonly under-served by interns.

Question 5

How do I explain a project in a technical interview?

Accepted Answer

State the problem and who had it, your specific role, the key technical decision and why you made it, one difficulty and how you resolved it, and the outcome. Two to three minutes, then let them ask. Interviewers probe the decision, so avoid claiming a choice you cannot defend. "I used MongoDB because the schema varied per source and I did not need joins" survives follow-up; "I used MongoDB because it is fast" does not. Be honest about which parts were yours in a team project — this is easily checked and badly received when overstated.

Question 6

What if my only projects are coursework or tutorials?

Accepted Answer

That is normal for an internship candidate and is fine, provided you can discuss the decisions in depth. Extend one tutorial project meaningfully — add a feature, tests, deployment, or handle a real edge case — so you have something you genuinely own. Interviewers do not expect production experience from an intern. They do expect you to know why your code works. One deeply understood project beats five cloned repositories every time.

Question 7

How do I answer "why do you want to work here"?

Accepted Answer

Name something specific about the company's product, engineering problems or scale, connect it to something you have actually done or want to learn, and be concrete. Generic praise about culture is transparently interchangeable. Spend fifteen minutes before the interview on the product, their engineering blog and a recent launch. "You process payments for millions of small merchants and I want to work on reliability at that scale" is specific; "you are a great company with great culture" tells them nothing.

Question 8

How do I answer a question about a conflict with a teammate?

Accepted Answer

Describe a genuine professional disagreement, show that you sought to understand their position, explain how the decision was reached — including if theirs prevailed — and state the outcome. Do not describe a personal grievance. Answers where you were entirely right and the other person entirely wrong score poorly, because they signal an inability to see other perspectives. Conceding on evidence is a strength, not a weakness, in this answer.

Question 9

What questions should I ask at the end of an internship interview?

Accepted Answer

Ask about the work itself and how you would be supported: what an intern actually ships, how projects are scoped, how feedback and code review work, what makes an intern successful there, and what the team is working on next quarter. Avoid questions answered on the careers page, and leave compensation to the recruiter rather than the engineer. "What does a successful intern do differently by week four?" is strong because it is specific, forward-looking and gives you genuinely useful information.

Question 10

How do I answer "tell me about yourself"?

Accepted Answer

Give a 60 to 90 second arc: what you study and where, what you have built or worked on that is relevant, and why this role is the logical next step. Present, then evidence, then direction. This is a framing opportunity — whatever you emphasise is what they will ask about next. Steer it toward the project you most want to discuss. Avoid the full chronological life history starting from school.

Question 11

What are my strengths and weaknesses — how do I answer honestly?

Accepted Answer

Give a real strength with evidence, and a real weakness you are actively working on with the specific step you are taking. Avoid disguised strengths; they are recognised immediately. "I struggle to ask for help early and lose time on blockers; I now set a 30-minute rule before asking" is credible and shows self-awareness. "I am a perfectionist" is the answer interviewers hear most and believe least.

Question 12

How much do behavioural rounds count for an internship?

Accepted Answer

More than most candidates assume. Technical rounds decide whether you can do the work; behavioural rounds often decide between several candidates who all can. At some companies a weak behavioural round alone will end the process. Interns are a mentoring investment, so signals about coachability, communication and reliability carry real weight. Rehearse your stories out loud at least once — the gap between a story you have thought about and one you have actually said aloud is large.

Question 13

What should I do in the final round or "super day"?

Accepted Answer

Expect several back-to-back rounds mixing coding, design and behavioural, often with different interviewers who do not share notes mid-day. Treat each as a fresh start and manage your energy — hydration, a break, and not re-litigating a round that went badly. Dwelling on a weak round is the commonest way candidates lose the two that follow. Panels typically calibrate afterwards, and a strong later round genuinely can offset an earlier stumble.

Question 14

Should I send a thank-you note after the interview?

Accepted Answer

A short note to the recruiter within a day is fine and occasionally helps. Keep it to three sentences: thanks, one specific thing you found interesting, and continued interest. It will not rescue a weak interview. Do not send long follow-ups with corrected solutions unless the interviewer invited it. In India, most internship processes run through the recruiter or campus placement cell, so send it there rather than hunting for personal emails.

Behavioural and HR Interview Questions Interview Questions and Answers

How to use this set