Live data from Hacker News

Google's interview system: it's not about solving the problem

threader.app

21–30 of 432 posts

Re: Google's interview system: it's not about solving the problem

#21
post #16

Why does everyone on HN seem to care so much about what Google does in interviews? We get it, no one likes weird off-topic brainteasers. Be a better engineer so you don't have to worry about having them on your resume and you'll be good.

> Why does everyone on HN seem to care so much about what Google does in interviews? Because all other companies just cargo cult what google does in interviews. If you want to switch jobs then this is interesting.

Fair enough

Re: Google's interview system: it's not about solving the problem

#23
When I get interview feedback about literally not having a coded complete solution despite strong communication skills, understanding of the solution and underlying cs concepts, i really cant help but conclude this as nothing but PR...

And then I read this >personal opinion

I'd rather take advice from /adv/

Re: Google's interview system: it's not about solving the problem

#24
Yet another "trust the system" message from the authority figure who enables the system. Similar:

- Police officer: Just follow our instructions, be cooperative.

- Car salesman: Just be upfront with what you want. Tell us about yourself, and we'll earnestly try to help you.

The message is the same; the authority "just wants to help," but in reality the relationship is adversarial to a larger degree than it is cooperative. On Blind, you know the real way to getting through the Google interview is LeetCoding like hell and not admitting you've seen the questions before.

Re: Google's interview system: it's not about solving the problem

#25

"its not about the problem" but if you cant correctly code one of these 200 algorithms on a whiteboard in sub 15 minutes while under extreme stress youre not getting an offer either.

Clearly some people can do that, since Google hires thousands of people every year. Why shouldn't they be hired over you?

Re: Google's interview system: it's not about solving the problem

#26
post #9

I've had Google recruiters reach out to me multiple times over the years and I've never taken them up on an interview. This last time, I told the recruiter I just wasn't interested in going through the process, and his response was a shocked "but why??" Is it so shocking that I don't want to subject myself to grueling demoralizing interviews to likely be rejected? I can get good work, with people I know, making good…

> Is it so shocking that I don't want to subject myself to grueling demoralizing interviews to likely be rejected?

Yes, it is. And this is a problem bigger than Google, this is simply one of the things that are going wrong on this planet. It is however one of the problems that are _relatively_ easier to fix.

Re: Google's interview system: it's not about solving the problem

#27

> Your interviewers try to understand what it feels like to work with you on a daily basis. If that were true then why not simulate those situations rather than riddles, google-able CS trivia, or whatever the interview flavor of the month is? I'd actually argue that for many companies this post is true (i.e. that getting it "right" is less important than the journey) but I still won't forgive companies that design th…

> The questions Google asks are disrespectful and unprofessional.

Yep. This is not the only instance were Google shows a culture of lack of respect for the dignity of the individual.

Re: Google's interview system: it's not about solving the problem

#28

"its not about the problem" but if you cant correctly code one of these 200 algorithms on a whiteboard in sub 15 minutes while under extreme stress youre not getting an offer either.

Clearly some people can do that, since Google hires thousands of people every year. Why shouldn't they be hired over you?

Because it's not a good measure of your programming skill. To be honest, I legit don't care whomst Google hires, what I hate is that there are all these other people who start adopting these attitudes and it can have a really shitty influence on the whole industry.

Re: Google's interview system: it's not about solving the problem

#29
post #9

I've had Google recruiters reach out to me multiple times over the years and I've never taken them up on an interview. This last time, I told the recruiter I just wasn't interested in going through the process, and his response was a shocked "but why??" Is it so shocking that I don't want to subject myself to grueling demoralizing interviews to likely be rejected? I can get good work, with people I know, making good…

I had a google recruiter reach out a couple years back, and I asked for just some ballpark idea of salary range. No dice - they wouldn't discuss even a ballpark range until I'd flown and and given up a couple of days or my time for travel and interviews. I didn't followup.

If you are in California, the employer is now required by law to disclose salary range.

Re: Google's interview system: it's not about solving the problem

#30

Earlier quoted context omitted.

My link from Glassdoor has feedback from interviewees from as recently as days ago. You can see the types of interview questions Google is asking right now. The sentence you're referring to was in the context of the FIELD which is why it said as much, and the specific question is a very well known stereotypical example: > But disrespectful and unprofessional interview questions ("why are manhole covers round?") has b…

> Why don't they ask questions relating to the job? When I hear of this sort of behaviour in interviews, I have to assume that the culture of the dept is such that x% of your job will entail fielding issues that are things that you consider outside your 'job'. If 20% of the time you'll be talking about stuff that you consider tangential, and you don't react well to that, you may self-select out. ?

Except this line of logic can be used to justify literally anything except illegal activity.
Post reply on HN