It's been a rollercoaster of emotions, late-night coding sessions, interviews, and a lot of hope — but finally, I made it to Google as a Software Engineer-I. Here's how my journey unfolded.
🛤️ The Application
Like many aspiring Googlers, my journey started with a simple application on the Google Careers page. I found an open role that matched my experience and aspirations, and submitted my profile.
📅 03-Apr-2025, 10:46 AM
I received a call from a recruiter, who asked to schedule a quick 15-minute screening discussion. The call was scheduled for the same day from 2:00 to 2:15 PM.
⚙️ Round 1: Screening (Rapid Fire)
💬 The first round was intense — a rapid-fire session with short questions covering:
- Data Structures & Algorithms (DSA).
- Computer Networks.
- Web Technologies.
It tested not just depth but also the breadth of my understanding. It was fast-paced, but I kept my cool.
📅 04-Apr-2025, 11:56 AM
I got an update — I had cleared the screening round!
The recruiter invited me for a 15-minute prep call the same day (3:15–3:30 PM) to explain the next steps.
During this call:
- He gave an overview of the interview structure.
- Shared documents for preparation (though advised not to rely solely on them).
- Provided tips on what interviewers generally look for.
That conversation really helped me prepare strategically.
💻 Round 2: Technical Interview
📅 10-Apr-2025, 2:15–3:00 PM
This was a DSA-focused coding interview. I was asked a problem and had to:
- Discuss the optimal approach.
- Explain corner cases.
- Analyze time and space complexity.
I coded confidently and interacted well with the interviewer. He seemed impressed and nodded positively throughout.
📌 Verdict: Strong Hire
🧠 Round 3: Technical (Dynamic Programming)
📅 29-Apr-2025, 2:30–3:15 PM
This round focused on a dynamic programming problem.
- I approached the problem optimally.
- Explained the logic clearly and walked through a dry run.
- Due to time constraints, I couldn’t finish writing a bug-free version of the code.
📌 Verdict: Hire
🏗️ Round 4: System Design
📅 06-May-2025, 2:00–2:45 PM
The problem: Design an automated parking lot system.
I structured the solution methodically:
- Covered the key components.
- Discussed scalability and concurrency.
- Focused on real-world implementation aspects.
📌 Verdict: Hire
💬 Round 5: Googliness Interview
📅 05-Jun-2025, 9:00–9:45 AM
This round was delayed a bit due to scheduling issues but was one of the most interesting.
This behavioral and culture-fit round tested:
- Leadership traits.
- Collaboration mindset.
- Handling ambiguity and difficult situations.
📌 Verdict: Hire
📞 The Call — and the Twist
📅 06-Jun-2025, 10:13 AM
The recruiter called to inform me that all rounds went well. He asked:
- My location preference (Hyderabad vs. Gurugram).
- My notice period.
- Expected salary.
He said he would discuss everything with the hiring manager and share the offer in 4–5 days.
😞 The Setback
📅 13-Jun-2025, 11:00 AM
Since I hadn’t heard back, I called the recruiter.
The news hit me hard:
- The hiring committee decided to put my application on hold.
- They liked my profile but chose another candidate who could join sooner.
- There was still a chance if a similar role opened up, but it wasn’t guaranteed.
I was heartbroken. After coming so far, it felt like I was just inches away — and then back to square one.
🌈 The Comeback
📅 24-Jun-2025, 10:00 AM
Out of the blue — the recruiter called again!
“There’s a similar opening in a different team, and we’d like to go ahead with you,” he said.
The same day, I received the offer letter.
💥 I accepted it. And just like that — I became a Googler!
🎉 Final Thoughts
Getting into Google wasn't just about technical knowledge. It was about perseverance, preparation, and staying composed — even when things don’t go your way.
To all those aspiring for similar roles: Don’t give up.
Your story might also take a detour, but it’ll be worth it in the end.
Hureeeyyyyy! 🎊
See you on the other side of the Googleplex. 💻🚀
Top comments (0)