From our research
What this interview looks like
Google India typically starts with a recruiter conversation and, for campus and early-career candidates, an online coding assessment or a 45-minute technical phone screen in a shared editor.
The onsite, now usually virtual, is typically four to five interviews of about 45 minutes each: for software engineers three or four coding interviews on data structures and algorithms plus one Googleyness and Leadership conversation, with a system-design interview added for experienced levels.
Interviewers are engineers from other teams rather than the hiring manager, and each writes structured feedback that a hiring committee reads before any offer. Team matching follows the committee, so a strong candidate can wait while a team is found.
Product manager candidates typically see a PM phone screen and then a loop of product design, analytical, technical, strategy and leadership interviews, again decided by a committee.
The number of rounds, their order and the timeline vary by level, office and year, and Google does not publish cut-offs, so treat anything you read online as a pattern rather than a rule.
ExamPilot compresses the loop into a 17-minute panel: an HR screen, a hiring-manager conversation on your past work, a coding or design or product round in your chosen specialisation, a Googleyness and leadership round in STAR form, and a closing on expectations, scored on role knowledge, problem solving, communication and attitude.
How it is weighted
No single round decides. Each interviewer writes structured feedback against coding, algorithms and data structures, problem solving, communication and Googleyness, and a hiring committee of engineers who did not interview you reads the packet and decides. Team matching follows.
One weak coding round can be outweighed by strong ones, but a clear lack of working code or dishonesty about what you built is hard to overcome. Here each round is scored against the corporate rubric (role knowledge 30, problem solving 25, communication 25, attitude 20).
Who this is for
Candidates who have cleared Google's online coding assessment or technical phone screen, either through a campus drive, a referral or a direct application. Campus candidates typically see coding interviews plus a Googleyness and Leadership round; experienced candidates add a system-design interview.
Google does not publish degree cut-offs or a fixed round count; the pattern here is what candidates typically report as of recent cycles.
The panel focuses on
- Thinking aloud in a shared editor: clarify, choose a data structure, state the complexity, then write code that runs
- Graphs, dynamic programming, heaps and hashing at Google depth, with edge cases tested on your own code
- System design for experienced levels: scope, scale numbers, data model, consistency and one trade-off defended
- Googleyness and leadership: ambiguity, feedback, collaboration and failure told as specific incidents
- Honesty about what you personally built, because the hiring committee reads evidence, not impressions
- Why Google and realistic expectations of team matching, global teams and the review culture
Step 1
Pick your domain
The expert on the panel probes these areas at the level of this role. Optional here; you can choose during setup.
Step 2
Choose how you want to be interviewed
1:1 interview
One interviewer runs every round and adapts the focus as you go. Lower pressure; ideal for a first attempt.
Ms. Nandini Rao
Hiring manager
Panel interview · 3 members
Most realisticEach member leads their own round and hands over to the next. They hear each other, so a weak answer will be revisited.
Ms. Neha Kulkarni
HR member
Ms. Nandini Rao
Hiring manager
Mr. Abhinav Kashyap
Technical lead
What to expect
5 rounds · 17 minutes
A private-sector hiring loop compressed into one sitting, the way most Indian companies run it: HR screen → hiring-manager round on your actual work → role/technical round led by a lead → communication & behavioural (STAR) round → closing on expectations and your questions.
Works for software, product, sales, finance, HR, support and campus hiring by swapping the role bank.
- Round 1
HR screen
· 3:00Understand background, motivation for this role and company, and basic logistics; check that the resume story holds together.
Ms. Neha Kulkarni2–3 questionsup to 1 follow-up each - Round 2
Hiring-manager round
· 4:00Assess ownership, judgement and how the candidate actually works: what they shipped, closed or ran, their specific part, and how they would approach this job.
Ms. Nandini Rao2–3 questionsup to 2 follow-ups each - Round 3
Role / technical round
· 5:00Test role knowledge and problem-solving in the chosen specialisation: fundamentals, one scenario to think through aloud, and trade-offs.
Mr. Abhinav Kashyap3–4 questionsup to 2 follow-ups each - Round 4
Communication & behavioural round
· 3:00Assess collaboration, conflict handling, resilience and clarity of expression through Situation–Task–Action–Result examples.
Ms. Nandini Rao2–2 questionsup to 1 follow-up each - Round 5
Expectations & closing
· 2:00Cover practical expectations and let the candidate ask questions; close professionally.
Ms. Neha Kulkarni1–2 questions
Meet the panel
Your AI interviewers
Distinct personas, voices and questioning styles, briefed on this role.
Ms. Neha Kulkarni
ChairHR member
HR business partner, IT services
Friendly, efficient, detail-checking.
Female voice · 4 languages
Ms. Nandini Rao
Hiring manager
Engineering Manager, Google India (Bengaluru); hiring-committee member who interviews software engineers and product managers across Search, Payments and Cloud teams
Calm, curious, rigorous about evidence, generous with hints.
Female voice · 3 languages
Mr. Abhinav Kashyap
Technical lead
Senior Staff Software Engineer, Google India (Hyderabad); trained coding interviewer and interview-calibration lead for the India offices
Precise, patient, collaborative, quietly demanding.
Male voice · 3 languages
Languages
Answer in the language you think in
The panel asks in your chosen language. Switch mid-answer if you like.
- English
- हिंदीHindi
- Hinglish (Hindi + English)Hinglish
How scoring works
A report you can act on
Every round is scored on the rubric
Each interviewer scores only the criteria their round covers. Weights add up to your overall score out of 100.
Only what you actually said counts
Feedback quotes your own answers. Rounds you skip show as “Not assessed” rather than a zero.
Communication is always measured
Fluency, clarity, confidence and structure are tracked across the whole interview, in any language.
Pass mark, then a plan
You see the pass mark for this interview, your gaps, and the courses that close them fastest.
Scored on
- Role knowledge30%
Depth and accuracy of role/domain knowledge; understands the tools, concepts and trade-offs of the job; grounds claims in real work.
- Problem solving & structure25%
Breaks problems down, asks clarifying questions, reasons about trade-offs and edge cases, structures answers (context, action, result).
- Communication25%
Clear, concise, confident; listens and answers the question asked; adapts the explanation to the listener; professional register.
- Culture & attitude20%
Ownership, honesty about limits, coachability, collaboration, motivation for this role and realistic expectations.
Pass mark 65 / 100 · Corporate interview — HR, hiring manager & role round (panel)
Keep exploring