Internship Interview Questions India 2026: Tech, MBA, and Consulting Internships

Common questions: 'Tell me about yourself' (90 seconds: college, strongest project, why this specific internship). 'Walk me through a project you built' (what you built, what specific technical decision you made and why, what you'd do differently). 'What do you want to get out of this internship?' (evaluates whether you have a real learning goal; strong answers are specific: 'I want to understand how a team of 30+ engineers coordinates on a shared codebase').

DSA: for top companies, LeetCode easy to medium. Topics: arrays, strings, recursion, binary search, trees (DFS/BFS), graphs (DFS/BFS, shortest path), DP basics (Fibonacci, coin change, LCS). For Google/Amazon/Microsoft: sometimes medium to hard. For Indian startups: easy, with emphasis on clean code and thinking aloud.

Tech stack questions: any technology on your resume is fair game. If you listed React, expect components, props, and state. If you listed SQL, expect a GROUP BY or JOIN query. Only list technologies you can discuss in a basic interview.

'Why consulting/why this firm?': research specific practice areas (McKinsey's digital and analytics India practice, BCG's work with Indian conglomerates, Bain's consumer and retail India practice). Mention a specific project or publication you read. 'I want to build problem-solving skills' is not sufficient alone.

Case interviews: always present. Formats: market sizing, business problem diagnosis, operations. Preparation: Victor Cheng's Case Interview Secrets, PrepLounge.com partner cases, minimum 20 practice cases before the interview.

Behavioural: 'Tell me about a time you led a team through difficulty.' 'Describe persuading someone who disagreed with you.' 'Career goal in 10 years and how does this internship serve it?' MBA evaluators weight leadership signals and structured thinking heavily.

Four concrete ways: (1) Know one thing deeply. One complete deployed project with real users > 15 technologies at surface level. Interviewers remember depth, not breadth. (2) Ask an unusually good question. 'I read that your team recently moved to a micro-frontend architecture. What were the main challenges and what would you do differently?' This signals how you think on the job. (3) Show genuine product curiosity. 'I noticed Swiggy's estimated delivery time accuracy seems to have improved significantly. Is that a focus area for the engineering team?' Makes the interviewer imagine you already working there. (4) Have a rough idea of what you would like to work on. A direction ('I noticed the search latency seems higher than expected; I'd love to work on something like that') signals initiative.

Google (SWE internship): 2-3 technical rounds via Google Meet + shared editor. Topics: arrays, strings, recursion, trees, graphs, DP. Difficulty: medium to hard. No system design for internships. Communication is evaluated heavily: think aloud, explain before coding, recover gracefully from wrong approaches.

Microsoft SWE internship: 2-3 technical rounds, medium difficulty. More weight on collaboration signals than Google or Amazon. Expect questions about how you would handle disagreement with a teammate.

Amazon SDE internship: 2 technical rounds + behavioural round based on Leadership Principles (Customer Obsession, Ownership, Invent and Simplify, Bias for Action). Prepare 2-3 STAR stories per LP. Amazon evaluates LP fit as heavily as technical skill for internships.

Preparation: 100-150 LeetCode easy/medium with focus on trees, graphs, and DP. Practice thinking aloud before writing code. 5+ mock interviews (HireStepX for behavioural, Pramp for technical peer mock interviews).