Interview Experience at Google (WSE Intern)

Overview

I interviewed with Google for the Web Solutions Engineer (WSE) Intern role.
The entire process spanned almost 3–4 months, making it one of the longest and most emotionally intense interview journeys I have experienced.

The process included:

1. Telephonic Screening
2. Technical Round 1 (Hashmaps – DSA)
3. Technical Round 2 (DP + Resume + Machine Coding)
4. Final Waiting Period & Result

---

Round 0: Telephonic Screening (20–25 Minutes)

After my resume was shortlisted, I received a telephonic call.

This round covered:

• My internship experience
• Deep discussion on my projects
• LeetCode/problem-solving background
• Core subjects: Operating Systems and DBMS

It was partly HR-driven but technically oriented.
After this, I was shortlisted for the technical rounds.

---

Round 1: Technical Interview (Hashmaps)

This round focused on a hashmap-based DSA problem.

• The question was relatively easy.
• I implemented the brute-force approach first.
• Then optimized it using a hashmap.
• Discussed time complexity thoroughly.

The interviewer went deep into:

• unordered_map vs ordered_map
• Average vs worst-case time complexity
• Collision handling
• Hash function optimization

At one point, he subtly suggested optimizing the hash function further.
This was a conceptual trap — the hash function could not meaningfully be optimized in that context.
I explained why it wasn't possible, which he seemed satisfied with.

I cleared this round and moved to Round 2.

---

Round 2: DP + Resume + Machine Coding

This round lasted 1 hour:

• First 45 minutes → Dynamic Programming question
• Last 15 minutes → Resume + Core CS + Machine Coding

DSA (Dynamic Programming)

• I first implemented a brute-force solution.
• Then optimized it using DP.
• Discussed time and space complexity.

The discussion was smooth and structured.

---

Resume & Core Concepts

The interviewer went deep into:

• RESTful APIs
• HTTP 1.1 vs HTTP 2
• gRPC vs REST
• Database indexing
• End-to-end optimization of a website (frontend → network → backend → DB)

He asked:

How would you optimize a search functionality?

I explained using debouncing, since I had implemented it in one of my projects.

---

Live Machine Coding – Debouncing

In the last 5–10 minutes, he asked me to implement debouncing in JavaScript.

• I explained how debouncing works.
• Implemented the logic.
• Minor syntax issues came up.
• He helped with small syntax corrections.

This again turned into an unexpected mini machine-coding round.

---

The Long Waiting Period

After completing all rounds, I was told:

The result would be announced in around 60 days.

During this period:

• I stayed in touch with HR.
• I was informed that my interviews were positive.
• I was hopeful.

However, after nearly four months from the start of the process, I finally received the rejection.

---

Final Result

❌ Not selected.

---

Honest Reflection

This rejection hurt.

Not just because it was Google —
but because of the long waiting period and the hope built during those months.

Waiting 60+ days while being told things were positive creates expectations.
After investing months emotionally and mentally, the final rejection was heartbreaking.

At times, I genuinely felt:

It would be better to receive a faster rejection than prolonged uncertainty.

---

What I Learned

Even though the result was negative, the experience taught me:

• Depth matters more than difficulty.
• Fundamentals (OS, DBMS, Networking) are extremely important.
• Real-world engineering discussions matter for WSE roles.
• Be prepared for unexpected machine coding.
• Emotional resilience is as important as technical strength.

---

Final Thoughts

This was one of the most intense interview journeys I’ve had.

It hurt. A lot.

But at the same time, it showed me that I was capable of reaching final stages at Google. That itself is proof of growth.

Rejections don’t define capability — they refine it.

On to the next opportunity 🚀