Google SDE Hiring Process and Interview Experience

Mansishah
6 min readFeb 18, 2024

--

Navigating the Hiring Maze: A Comprehensive Exploration of Personal Interview Experiences Leading to Offer Success

Stages of Interviews at Google: A Comprehensive Overview

How I Secured the Interview Opportunity at Google?

I was contacted by a recruiter at Google who discussed with me the exciting Software Development Engineer (SDE) opportunity. During our conversation, the recruiter took the time to thoroughly explain the entire application process, including each step involved, as well as providing detailed insights into the specific requirements and qualifications needed for the position.

Expectations for the Coding/Technical Round: Understanding the Criteria

  • Crafting code that is not only clean and efficient but also exhibits conciseness while addressing edge and boundary cases comprehensively.
  • Application of Data Structures and Algorithms, showcasing proficiency in fundamental concepts as well as tackling more advanced problems with the most optimal coded solutions.
  • Demonstrating articulate communication by elucidating step-by-step actions and thought processes throughout the entire interview session.
  • Posing insightful questions at various stages, methodically checking assumptions before and during the problem-solving process, and meticulously addressing edge and boundary cases.
  • Showcasing the efficacy of problem-solving abilities through a harmonious blend of speed and accuracy.

A Glimpse into My Interview Experience

  1. Phone screening

This round serves as a filtering stage, determining the candidate’s eligibility to proceed to further interviews. It typically lasts for 45 minutes, during which the candidate is asked 1–2 questions.

The interview commenced with a succinct self-introduction, after which the interviewer promptly transitioned to a coding problem. I engaged in coding directly on a Google Doc, which the interviewer reviewed simultaneously. Solving the problem necessitated a comprehensive understanding of trie, maps, strings, and logical constructs. Initially, I successfully provided a solution, yet I was prompted to further optimize it. As I contemplated potential optimizations, the interviewer offered a subtle hint, which I swiftly incorporated into the code. Upon completion, the interviewer graciously extended the opportunity for me to inquire about any aspects of the interview. With that, the interview concluded, leaving me without explicit feedback regarding my performance.

2. Coding round

Having cleared the phone screening round successfully, I advanced to the technical coding rounds, which unfolded as follows:

ROUND 1 :

Question — Variant of Sliding window problem

The interviewer presented me with a seemingly straightforward one-line problem, which belied its underlying complexity. Initially, I grappled with determining an optimal solution, opting to explore the brute force approach first. Through discussion, I gradually refined my approach and ultimately arrived at an optimal solution. Crucially, clear communication of the thought process during solution development proved instrumental in earning approval from the interviewer.

ROUND 2 :

Question — Variant of Longest contiguous sub array

The interviewer presented me with a variation of the classic problem of finding the longest contiguous subarray. Following insightful discussions, I successfully devised an optimal solution and proceeded to implement it in code. After completing the initial version of the solution, we engaged in a discussion about its complexities. Subsequently, the interviewer introduced another question, building upon the previous problem we had tackled. I adeptly discussed and coded the solution for this extended problem as well.

ROUND 3:

Question — Leetcode medium problem based on queues and stacks

Surprisingly, the interviewer presented me with a medium-level Leetcode problem that delved into the fundamental concepts of queue and stack as data structures, along with DFS/BFS algorithms. Given my prior practice on Leetcode, this round turned out to be the easiest and quickest for me. I efficiently tackled the question, providing an optimized solution that garnered the interviewer’s admiration. The clarity in my explanations and the thorough discussion of solution complexities further contributed to a positive impression.

ROUND 4 :

Question — Application of Disjoint Set Unit

This problem also presented a variant of a Leetcode challenge, focusing on the application of graph theory concepts to reach an optimal solution. Upon analysing the problem and its parameters, I chose to employ the concept of disjoint set units. Through vocalising my thought process and engaging in discussions with the interviewer, I successfully devised an optimal solution with optimised complexities.

Googlyness round :

We delved into my professional background, dissecting my past work experiences and examining the motivations behind my desire to join Google. Subsequently, the interviewer introduced Googlyness questions, which were situational in nature. Engaging in a series of thought-provoking scenarios, I drew upon my past projects and experiences to provide insightful responses. The interviewer consistently maintained a friendly and supportive demeanor throughout the session.

In summary, this round unfolded seamlessly, and I left with a positive impression, feeling that it went well.

NOTE : Previously, for onsite interviews, Google would extend invitations to candidates to visit their office and undergo all interview rounds within a single day. The “Googlyness” round typically coincided with a lunch hour alongside a Googler, facilitating informal discussions on behavior. However, following the onset of COVID-19, these rounds have transitioned to virtual settings. Additionally, while all coding rounds used to be condensed into a single day, the introduction of virtual interviewing has allowed for greater flexibility, enabling interviews to be spread across multiple days.

3. Team matching round

The team matching process at Google is an extensive endeavor where candidates engage in several meetings with different team managers from various departments or projects. These meetings allow both parties to assess compatibility, explore shared interests, and evaluate skill sets, ensuring that individuals are placed in roles where they can make meaningful contributions and thrive within the organization’s dynamic environment.

4. Hiring Committee

Following the onsite interview at Google, each interviewer (excluding the lunch interviewer) is required to submit detailed feedback, which remains confidential to prevent bias. This feedback includes assigned scores and a decision on whether to hire or not. If the feedback indicates strong performance, the candidate’s application progresses to the hiring committee for further review. The hiring committee meticulously evaluates all feedback before making a final recommendation on whether to hire the candidate.

I got the decision for this round in my favor, hence my application packet moved to the next stage.

5. Compensation structure approval

At Google, there is a dedicated team responsible for defining and determining the compensation package for each candidate. Once finalized, this information is communicated to the candidates, initiating the offer negotiation process. Candidates have the opportunity to discuss and negotiate their compensation package with the hiring team, ensuring alignment with their expectations and market standards. Following negotiations, I provided approval for the offer to be generated.

6. Offer Letter

I got the offer after about a week.Viola!

P.S. I am reachable on LinkedIn or Email / Skype at mansishah1496@gmail.com

--

--