Hey folks,
Just wanted to get some insight into how Google evaluates candidates in Round 1.
I recently had my first-round interview and unfortunately got a rejection call today. The interview itself was for a graph problem specifically, we were given a directed graph and had to identify all the cyclic nodes. I explained my approach using DFS along with a set to track visited nodes. I also walked through an array-based approach since the interviewer suggested that direction, and I made sure to clarify why I opted for DFS + set instead.
During the interview, it felt like things went well. The interviewer seemed convinced and the discussion was pretty smooth. But here’s the kicker: the interviewer wasn’t really comfortable with Python. At one point, he even thought using def to declare a function was a typo… yeah.
So, now I’m just wondering did I miss something important? How does Google actually assess candidates in that first round? Would love to hear your thoughts.
Be the first to comment.
Hey all, just wanted to add here about the first interview round that I had with Google. I can't disclose the exact question but it was a Topological Sort Graph based problem (something like Course Schedule on Leetcode). I almost got the...
Just got dinged by Google in Round 1 only. Throughout the interview i felt like what the fuck, and why the fuck am i solving such a problem.
45 minutes went very fast, and couldn’t cover all the aspects of product design.
I need to s...
@Faang Folks - From Sep 25th till Oct 25th I had 5 rounds of interviews done for a TPM role. Out of these 5 (1 phone screen+ 4 on-site [2 Tech + 2 Functional]), I believe I did well on 4, except 2nd Technical round where I was not able t...