Three candidates describe Gemini's engineering interviews: a recruiter or manager screen, then coding, system design and behavioral conversations. Reports cover algorithms, e-commerce design, code review and a mobile take-home.
$170K
Avg. Base Comp
$220K
Avg. Total Comp
3-6 rounds
Typical Rounds
Not reported
Process Length
Three candidates describe Gemini's engineering interviews. Two interviewed for senior software engineer roles and one for a mobile engineer role, so treat the mobile details as specific to that team.
Both senior candidates describe a conversation with a hiring manager or engineering director before the technical rounds. One said the director conversation mixed behavioral questions with a code review exercise, where they critiqued sample code. The other described a four-interview panel covering system design, coding, cross-functional and behavioral topics, followed by a culture-fit conversation with a skip-level manager.
The coding questions they mention are algorithmic. One candidate got a multi-part dynamic programming problem where each follow-up built on the previous answer. Another got the happy-number problem, which rewards recognizing the cycle-detection trick early. System design came up in both senior reports. One described it as standard, and the other was asked to design an e-commerce site with a cart and purchase flow.
The mobile candidate had a different experience. It began with a recruiter screen and a four-hour React Native and TypeScript take-home that built a crypto watchlist. A hiring manager round, a technical interview and a system design interview followed. That candidate found the process long and inconsistent and did not receive an offer.
The candidates disagree on how the process felt. One called it smooth and well prepared, while another found a peer interview rushed. Confirm the schedule and each round's focus with your recruiter, and practice explaining trade-offs aloud as a problem grows more complex.
Synthesized from 3 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Gemini process.
There are a total of 5 interview rounds, followed by a final HR discussion.
After the client round, there will be a final discussion with HR regarding the overall outcome and offer details.
The biggest surprise for me was how much time the interviewers spent digging into my real project experience rather than asking tricky theoretical questions. I felt most confident while explaining the systems I had actually built and the problems I had solved. The moments that made me sweat were the follow-up questions—every answer led to a deeper "why?" or "what if?" discussion, so having a genuine understanding of my work was much more important than memorizing interview questions.
Questions asked: From what I remember, here's what was covered in each round:
This round focused on the fundamentals of my tech stack and previous experience. Some of the questions included:
This was much more focused on project deep dives. The interviewer kept asking follow-up questions to understand whether I actually built the features I mentioned.
Topics included:
Almost every answer was followed by a "Why?" or "What if?" question, so they were testing depth of understanding rather than surface-level knowledge.
This round was primarily about my projects and ownership.
The discussion covered:
There was no take-home assignment in my interview process.
Overall, my advice would be to know your resume and projects inside out. The interviewers spent far more time exploring the work I'd actually done than asking random textbook questions.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Gemini
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Empty Neighborhoods | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Closest SAT Scores | |
| Employee Salaries | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Total Spent on Products | |
| String Shift | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Prime to N | |
| Top 3 Users | |
| Google Maps Improvement | |
| Over-Budget Projects | |
| P-value to a Layman | |
| Over 100 Dollars | |
| Minimum Change | |
| Find the Missing Number | |
| Scrambled Tickets | |
| Maximum Profit | |
| Size of Joins | |
| Last Transaction | |
| Hurdles In Data Projects | |
| Project Pairs | |
| Retailer Data Warehouse | |
| Sum to N |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report starting with a recruiter call or a hiring manager conversation. One senior candidate was contacted by a hiring manager through a job platform. The mobile candidate began with a recruiter phone screen. Expect to discuss background and role fit, and ask what the later rounds will cover.
One senior candidate met a Director of Engineering for a mix of behavioral questions and a code review exercise. They were given sample code to analyze and critique. This may be worth practicing by reviewing unfamiliar code for correctness, quality and maintainability, and explaining your reasoning out loud.
Candidates report algorithmic problems. One was a multi-part dynamic programming question where each follow-up extended the previous solution. Another was the happy-number problem, where spotting the cycle-detection trick early keeps you from getting stuck. Prepare to discuss complexity and trade-offs as constraints change, not just to reach a first working answer.
System design appears in the senior reports and in the mobile report. One senior candidate called it standard. Another was asked to design an e-commerce site where users add items to a cart and complete a purchase. Practice separating cart and checkout concerns, defining data models and explaining your trade-offs.
One senior candidate had four back-to-back panel interviews, including cross-functional and behavioral rounds, followed by a culture-fit conversation with a skip manager. Another said the final round combined coding, behavioral and system design. The mobile candidate also faced a take-home and several later rounds, so round structure may vary by team.
