RejectedL3 (SDE) at Google
- Difficulty
- Process took
- 3-4 Weeks
- Rounds
- 5
- Format
- Remote
- Applied via
- Company Website
How it went
- Edge cases first: Before coding, quickly think about tricky inputs.
- Dry run always: Even a small test can save you from major mistakes.
- Explain your thought process: Structured problem-solving matters more than rushing to code.
What they would tell you
- Edge cases first: Before coding, quickly think about tricky inputs.
- Dry run always: Even a small test can save you from major mistakes.
- Explain your thought process: Structured problem-solving matters more than rushing to code.
How to prepare
My advice:
- Always clarify the problem and discuss edge cases upfront. It helps show your thought process, even if you stumble on implementation.
- Use STAR format and prepare stories that show impact, ownership, and learning. Google focuses heavily on collaboration and mindset.
Round by round
- 1
Phone screen Round60 min
This round was scheduled for Feb 4th. We began with brief introductions, the coding task, find the smallest letter strictly greater than a target. I solved the task. I explained the approach and complexity, implemented it, and dry run.
- 2
Technical Round 160 min
Again with quick introductions.My task was Given two strings a and b, build a new string by alternating characters starting with the shorter string. If one string finishes first, append the remaining characters of the other. Return the result.
- 3
Technical Round 260 min
This round focused on Stack problem and I fumbled.I did well on clarifying questions and edge cases, but my chosen approach was off. Verdict: No Hire
- 4
Technical Round 360 min
The third on-site round on March 5th, I solved similar problem like Task Scheduler,The interviewer then gave a follow-up question , which I explained and implemented correctly. A second problem on valid palindrome checking with at most one deletion was also solved successfully, the interviewer seemed impressed.
- 5
Googleyness60 min
Finally, the fourth round on March 11th focused on Googleyness and behavioral questions, covering teamwork, manager feedback, adapting to changing priorities, and project experiences.
What came up
A candidate-reported account, lightly edited. Interview processes change by team and date.