Hacker News Reader

Comment by lokar | Hacker News Reader

I did over 400 interviews working there, and many hundreds more serving on hiring committees. I never gave a leetcode interview, and saw only a modest amount of them in committee.

“It’s all leetcode BS” makes a great offhand d complaint but was not the actual truth.

View on HN

I only interviewed once with them, but there wasn't anything I'd consider leetcode.

There was a rather aggressive interviewer who drilled me on an architectural web services question despite interviewing for a systems programming position on Fuchsia and having a resume solely in embedded/systems programming. From my limited experience I'd say the interview process is broken, but not in the way people on here think.

Then I'm super unlucky because my last phone interview there 3 weeks ago was definitely Leetcode.

I’ve interviewed there multiple times over the years. It was full of typical leetcode shit. There’s a reason there’s a list of problems on leetcode tagged as Google having used them recently…

I personally like the story of the hiring committee that refused to hire themselves

https://youtu.be/r8RxkpUvxK0?t=531

I watched this a while ago and thought I’m clearly too dumb to work at Google because I’m not going to come up with convex hull algorithms in an interview room.

Google reached out to me a few times to see if I'd interview with them. On the one or two phone calls I had with their recruiters, they explicitly advised me to practice algorithms (leetcode et al) if I wanted to move forward. Perhaps what you were doing was not the norm.

Okay, then what questions did you give in interview?

I personally did a lot of system design, debugging (systems or code), or deep technical dive (explain in more and more detail how something works and why it works that way).

Then why is there hundreds of Google tagged questions on LeetCode?

It’s a big company, and I left 5 years ago

Reply on news.ycombinator.com