Internship Interview Q&A: Google, TCS, Deloitte, HUL 2026

Every company interviews differently — and preparing for a Google internship the same way you’d prepare for TCS Ninja, or walking into a Deloitte case round with the same script as an HUL LIME pitch, is one of the most common reasons strong candidates get rejected. This guide breaks down exactly how each of these four companies structures its internship interview, the real questions candidates report being asked, and how to prepare for each round specifically — not generically.

Interview formats and questions shift from cycle to cycle. This guide reflects patterns reported by recent candidates and official program details as of 2026; always confirm the current process from your specific interview invite or official communication.

Quick Comparison: What Each Company Actually Tests

Company	Rounds	Core Focus
Google	Application screen → Online assessment → 2–4 interviews → Team match	DSA, problem-solving, “Googleyness” (culture fit, curiosity)
TCS (Ninja)	TCS NQT exam → Technical interview → HR/Managerial round	Programming fundamentals, aptitude, communication
Deloitte	Online assessment → Group discussion/case → Technical → HR	Case-solving, business communication, domain readiness
HUL	Foundation School selection → Case competition (LIME/FinAce) → Video interview	Business thinking, marketing/finance acumen, teamwork

Google Internship Interview: STEP & Software Engineering Roles

Google’s internship hiring — whether through STEP (for second-year students) or the general Software Engineering internship track — follows a structured, skill-based process. There is no fixed CGPA cutoff; what matters is your problem-solving ability and how clearly you communicate your thinking.

The Process

Application screening — resume and academic transcript reviewed against the specific role listing.
Online assessment — coding questions for technical roles; case-based questions for non-technical/business roles.
Technical interview(s) — typically 1–2 rounds focused on data structures, algorithms, and problem-solving, conducted live with a Google engineer.
Behavioral/‘Googleyness’ round — assesses communication, collaboration, and learning mindset, especially important for early-career candidates like STEP applicants.
Team matching — successful candidates are matched to a team based on skills and interests before receiving a final offer.

Real Questions Candidates Report Being Asked

Q: Explain your approach to a problem before you start coding — how would you break this down?

A: Google interviewers weigh your reasoning as heavily as your final answer. Structure your response clearly: restate the problem, ask clarifying questions about constraints and edge cases, then talk through your approach before writing any code.

Q: Solve a problem involving arrays, hashing, or recursion (exact problems vary by round and rotate frequently).

A: Rather than memorizing specific problems, build genuine fluency in core data structures — arrays, hashmaps, trees, graphs, recursion, and binary search — since Google’s coding rounds test fundamentals, not tricks.

Q: Tell me about a project you’re proud of and what you learned from it.

A: Pick a project where you can clearly explain your specific contribution, a technical or logistical challenge you faced, and what you’d do differently — Google values reflective thinking, not just outcomes.

Q: What would you do if you disagreed with a teammate’s technical decision?

A: This tests collaboration and communication, not technical correctness. A strong answer shows you can disagree respectfully, explain your reasoning with evidence, and stay open to being wrong.

How to Prepare

Build strong command over arrays, hashing, trees, graphs, recursion, binary search, and dynamic programming — these come up repeatedly across reported interviews.
Practice explaining your reasoning out loud, not just solving problems silently — interviewers are evaluating your thought process throughout.
Have 2–3 well-rehearsed project stories ready that show genuine ownership, not just participation.
For non-technical roles (business, UX), prepare case-style reasoning — Google’s non-tech tracks use case-based assessments rather than coding tests.

TCS Ninja / NQT Internship Interview

TCS’s fresher and internship hiring runs through the TCS National Qualifier Test (NQT), which feeds into two tracks: Ninja (standard entry-level) and Digital (a higher band requiring deeper technical knowledge). Both tracks share the same interview structure, but the depth of technical questioning differs.

The Process

TCS NQT written test — covers numerical ability, verbal ability, logical reasoning, and a programming/coding section, split into Foundation and Advanced sections.
Technical interview (20–30 minutes) — for IT-background candidates, expect questions on programming, databases, and operating systems; non-CS candidates are tested on basic programming logic instead.
HR / Managerial round — focused on communication, willingness to relocate or work flexible shifts, and general fit.

Real Questions Candidates Report Being Asked

Q: Explain the concept of polymorphism with an example.

A: Use a simple, concrete example (like a Shape class with different subclasses) rather than a textbook definition — TCS interviewers are checking whether you actually understand the concept, not whether you memorized it.

Q: What’s the difference between an array and a linked list?

A: Cover both structure (contiguous memory vs. nodes with pointers) and practical trade-offs (access speed vs. insertion/deletion efficiency) — a complete answer touches both angles.

Q: Write a program to reverse a string or check if a number is prime.

A: These pattern-based coding questions are extremely common in Ninja interviews. Practice writing clean, working code for basic problems (string reversal, Fibonacci series, palindrome check, prime check) until you can do them without hesitation.

Q: Tell me about your final-year project.

A: Be ready to explain it in plain language even if the interviewer isn’t from your exact specialization — TCS interviews civil, mechanical, and other non-CS graduates too, so clarity matters more than jargon.

Q: Are you willing to relocate or work night shifts?

A: Answer honestly and directly — TCS asks this because many roles genuinely require flexibility, and a vague or evasive answer can cost you the offer regardless of your technical performance.

How to Prepare

Revise core CS fundamentals: OOP concepts, basic SQL, data structures, and operating system basics, even if you’re not from a CS background.
Practice simple, high-frequency coding patterns rather than complex algorithms — TCS Ninja rarely goes beyond fundamentals.
Keep your ID proof documents (Aadhaar, voter ID, college ID) ready — TCS interviewers commonly verify these during the process.
Prepare a clear, honest answer on relocation and shift flexibility in advance.

Deloitte Internship Interview

Deloitte’s internship interviews vary somewhat by service line (Audit, Tax, Consulting, Risk Advisory), but the overall structure is consistent: an assessment, a case or group round, and one or more HR/technical conversations. Consulting-track interviews go furthest into structured case-solving.

The Process

Online assessment — quantitative aptitude, logical reasoning, and English sections.
Group discussion or case round — candidates discuss a business case together, or for consulting tracks, complete a 30–45 minute individual or group case interview.
Technical/domain interview — questions tied to your specific service line (audit, tax, or consulting fundamentals).
HR interview — final round covering background, motivation, and cultural fit.

Real Questions Candidates Report Being Asked

Q: Tell me about yourself and why Deloitte.

A: Structure this in three parts: a brief academic/background summary, one or two relevant experiences or projects, and a specific, researched reason you want to be at Deloitte rather than a generic answer about ‘growth’ or ‘brand name.’

Q: Walk me through how you’d approach this business case (client facing a specific problem).

A: Deloitte’s case rounds value structured thinking over a ‘correct’ answer. Clarify the objective early, break the problem into clear components, and think out loud — interviewers are assessing your process as much as your conclusion.

Q: Which Excel functions are you comfortable with?

A: Be specific and honest — mention functions like VLOOKUP/XLOOKUP, pivot tables, and conditional formatting if you know them, since Deloitte roles often involve real spreadsheet-heavy work from day one.

Q: Describe a time you worked in a team under pressure.

A: Use the STAR method (Situation, Task, Action, Result) and, where possible, quantify the outcome — Deloitte interviewers respond well to measurable impact, even from a college or internship project.

Q: Are you willing to work long hours or relocate for client engagements?

A: Consulting and audit roles at Deloitte often involve travel and intense periods of work — answer honestly, since misalignment here shows up quickly on the job.

How to Prepare

Practice structuring case answers using a simple framework (clarify → break down → analyze → recommend) rather than searching for the ‘right’ answer.
For group case rounds, focus on collaboration and including quieter teammates — Deloitte evaluates teamwork and facilitation skills, not just who talks the most.
Revise basic Excel skills and any accounting/finance fundamentals relevant to your target service line.
Prepare 2–3 STAR-format stories from academic projects, internships, or extracurriculars in advance.

HUL (Hindustan Unilever) Internship Interview

HUL’s internship pipeline works differently from the others on this list — most students enter through the Unilever Foundation School, a short immersive workshop that grants access to India’s two largest B-school case competitions: L.I.M.E. (marketing) and FinAce (finance). Strong performers in these competitions get fast-tracked toward HUL’s summer internship program.

The Process

Foundation School application — a registration-based selection open to B-school aspirants and students, reviewed on academic background and profile.
Immersive workshop at HUL’s Mumbai head office — covering Sales & Marketing, Finance, Supply Chain, and HR fundamentals directly from HUL managers.
Case competition entry — L.I.M.E. for marketing-track candidates, FinAce for finance-track candidates; both are real, live business case challenges judged by HUL leadership.
Video interview round (HireVue-style) — candidates answer a mix of behavioral and case-based questions on camera, often with limited prep time per question.

Real Questions Candidates Report Being Asked

Q: Tell us about a brand you admire and how you’d improve its market position.

A: HUL evaluates commercial instinct here — pick a brand you can speak about with genuine insight (ideally one you’ve actually used or researched), and structure your answer around a specific, actionable idea rather than generic praise.

Q: You’re given a business scenario — how would you respond? (Case-based video question, typically 3–10 minutes prep and answer time per question.)

A: These are timed and structured, so practice thinking on your feet with short prep windows. Keep your answer organized: state your read of the situation, your recommended approach, and your reasoning, in that order.

Q: Describe a situation where you had to work with a difficult team member.

A: HUL’s case competitions are heavily team-based, so this question is assessing whether you can collaborate under real pressure — focus on what you did to move the team forward, not on criticizing the other person.

Q: Why FMCG, and why HUL specifically?

A: Avoid a generic answer about ‘loving brands.’ Reference something concrete — a specific HUL brand, a business decision you found interesting, or a trend in the FMCG sector you have a real opinion on.

How to Prepare

Study HUL’s brand portfolio and recent business moves — the company holds a wide range of household brands, and candidates who reference specifics stand out from those who speak generically.
Practice case competitions beforehand — join a few informal case-solving groups or Unstop challenges to get comfortable with timed, structured business reasoning.
For the video interview, rehearse answering out loud with a timer — the format rewards candidates who can structure a clear answer quickly, not just those with good ideas.
If you’re applying via LIME (marketing) or FinAce (finance), tailor your preparation specifically — the case types and evaluation criteria differ between the two tracks.

General Preparation Tips That Apply Across All Four

Do this regardless of which company you’re interviewing with • Research the company’s recent projects, products, or business moves — generic answers are the fastest way to sound uninterested. • Prepare 2–3 strong stories from your academic or extracurricular experience that you can adapt to different behavioral questions. • Practice explaining your thinking out loud, not just arriving at correct answers — every company on this list evaluates process, not just output. • Keep your documents (ID proof, transcripts, resume copies) ready and organized before the interview day. • Ask a genuine, specific question at the end of the interview — it signals real interest and gives you a final impression that isn’t just about your answers.

Final Word

These four companies test fundamentally different things — Google wants structured problem-solvers, TCS wants dependable fundamentals and flexibility, Deloitte wants organized business thinkers who can work in teams, and HUL wants commercial instinct under real time pressure. Generic interview prep will get you through the door at none of them. Study the specific format, practice the specific skill each company is testing, and walk in prepared for exactly the round you’re about to face.