Live data from Hacker News

Google Interview Questions Deconstructed: The Knight’s Dialer

alexgolec.dev

131–134 of 134 posts

Re: Google Interview Questions Deconstructed: The Knight’s Dialer

#131

Earlier quoted context omitted.

Early Google was incredibly arrogant and aggressive around only hiring people they thought were brilliant. The model was small teams of super-elite people. They took some flack for hiring for high caliber people into even relatively menial positions (e.g. random office admins). Even for things like the cafeteria, they wanted a world-class chef. On the whole, it actually worked very well. Everyone wanted to work there…

You didn't address anything I said. Nothing I said was related to early Google.

Okay. Let me tie it together.

Early Google: Phenomenal ability to build effective, high-quality products. Everyone wants to work there. Stainless reputation with the public.

Current Google: Limited ability to build effective high-quality products (but retty good at sustaining the successful products they have). Mixed reputation as an employer. Mixed reputation with the public.

You can extrapolate from there. I'm concerned about the second derivative.

I think the second piece there is employee growth. In 2001, Google had 300. In 2004, it has 3,000. By 2011, it had 32,000. today, it's over 100,000. You can't quite fit an exponent to it, but it's pretty close. If revenues don't keep growing exponentially....

I'm not implying it's failing, by any means, but it's gone to the same place as any other large corporation, and not a strong position to maintain pole position from.

Re: Google Interview Questions Deconstructed: The Knight’s Dialer

#132

This problem was used at my work years ago. We now have a hiring guild dedicated to making a better interview process. Multiple people said they were originally in the guild to prevent this problem from being used haha.

It really makes you wonder whether puzzles like this are a valid measure for real life performance at Google. Probably not.

They are not (except for a very limited number of developers working on very specific things).

Re: Google Interview Questions Deconstructed: The Knight’s Dialer

#133

This is a fun problem, but it's a terrible interview question for trying to hire software engineers.

The point of leetcode problems isn't to find out if you're a good software engineer. It's to find out if you're willing to spend hundreds of hours practicing tedious bullshit to get a job and google. If you can solve this in the interview you can become a good software engineer.

Memorizing known solutions to known problems does not guarantee good problem solving skills.

Furthermore, you’re now selecting for people that are highly willing to “spend hundreds of hours doing tedious bullshit.” If you were a CEO, is this the type of people you’d want to stack your organization with?

Re: Google Interview Questions Deconstructed: The Knight’s Dialer

#134

Earlier quoted context omitted.

The point of leetcode problems isn't to find out if you're a good software engineer. It's to find out if you're willing to spend hundreds of hours practicing tedious bullshit to get a job and google. If you can solve this in the interview you can become a good software engineer.

Memorizing known solutions to known problems does not guarantee good problem solving skills. Furthermore, you’re now selecting for people that are highly willing to “spend hundreds of hours doing tedious bullshit.” If you were a CEO, is this the type of people you’d want to stack your organization with?

[deleted]
Post reply on HN