Google onsites - Need opinion
Google Onsites - Need Opinion
I’ve recently wrapped up my Google coding onsite interviews, and I must admit, I’m feeling quite anxious about the experience. I wanted to share my journey here and would love to hear your thoughts and opinions.
Overview of My Experience
Technical Phone Screen (TPS)
- Question Type: LeetCode medium-level question.
- Outcome: Solved it using an optimal approach.
- Feedback: The recruiter mentioned that I did very well.
- Self Verdict: Strong Hire (SH)
Onsite 1
- Question Type: LeetCode medium to hard-level question.
- Outcome: Initially struggled to come up with the optimal approach within the first few minutes. However, the interviewer provided a hint, which helped me to finally devise the optimal solution and code it.
- Feedback: The recruiter reassured me that it’s okay this interview didn’t go “well.” I still have two more chances.
- Self Verdict: Low Hired / Low Hire (LNH/LH)
Onsite 2
- Question Type: LeetCode medium-level question.
- Outcome: I was able to quickly formulate the optimal approach and code it efficiently, without any bugs or follow-ups. The interviewer seemed pleased with my performance.
- Feedback: The recruiter informed me that the feedback was positive.
- Self Verdict: Strong Hire (SH)
Onsite 3
- Question Type: LeetCode medium to hard level.
- Outcome: I shared three different approaches during the interview. It took me some time to arrive at the third optimal approach, after which I successfully coded the solution. However, there was a follow-up question that we didn’t have time to discuss.
- Feedback: The interviewer acknowledged the solutions provided, but we ran out of time for the follow-up.
- Self Verdict: Low Hire / High (LH/H)
Reflection
As I reflect on my experiences, I realize that each interview presented its unique challenges and opportunities for growth. While I felt confident in some areas, I also recognized moments where I could improve my problem-solving speed and efficiency.
Key Takeaways
- Preparation is Crucial: Understanding common question types and practicing them can help reduce anxiety and improve performance.
- Adaptability: Being open to hints or suggestions during the interview can be beneficial. It’s essential to remain flexible and leverage the interviewer’s guidance.
- Time Management: Balancing the time spent on coming up with solutions and coding is critical, especially in a timed setting.
Conclusion
Overall, I appreciate all the support and feedback I received during this interview process. I’m eager to hear what you all think about my journey. What would you have done differently? Were there specific techniques or strategies you found helpful in similar situations?
Top Comments
- Can you mention question types/topics?: Absolutely! The questions ranged from data structures like arrays and trees to algorithms involving dynamic programming and graph traversal. If you have any specific areas you’re curious about, let me know!
I look forward to your insights and advice as I navigate this exciting yet nerve-wracking process!