Google L3 Interview Experience | Phone Screen and Googlyness

My Google L3 interview process in India included a phone screen and a Googlyness round. The process started in early August when a recruiter reached out to me on LinkedIn. Here’s how the process went, along with the coding question and behavioral questions I encountered.

Interview Timeline

• Early August: Recruiter reached out on LinkedIn.

• 2 days later: Completed the GHA (agree/disagree questions).

• 3 days after GHA: Received the online assessment invitation.

• About a week later: Completed the OA, which had two DSA questions. I was able to solve both.

• Around 10 days after the OA: Recruiter contacted me about the phone screen.

• 3 weeks later: Attended the phone screen.

Phone Screen (Virtual)

The coding question involved merging employee shifts into a timeline of non-overlapping intervals. Each shift was represented as [name, startTime, endTime], and the goal was to identify every time segment along with the employees working during that interval.

For example, if multiple employees had overlapping shifts, the output needed to split the timeline at the relevant start and end times and list the active employees for each segment.

I initially jumped into coding without clarifying my approach, which made things a little difficult. However, the recruiter was supportive, and I managed to complete the implementation within the allotted time. There was a bug in my solution, but after receiving a hint and an example, I identified and fixed it.

Googlyness (Virtual)

This round focused on behavioral questions and how I handle situations at work. Some of the questions included:

• Tell me about a time when project requirements changed midway. How did you handle it?

• Describe a conflict you had with your manager and how you resolved it.

• Tell me about a time you failed and what you learned from the experience.

There were around three to four basic questions. Overall, it was a positive experience, and I felt comfortable discussing my past experiences.

The phone screen tested coding ability and problem-solving, while the Googlyness round focused on behavioral skills and handling workplace situations. One important lesson from the coding round was to clarify the approach and edge cases before starting implementation.