My Job Interview at Google • Hacker News Board

Re: My Job Interview at Google

#111

Post by cmars232 » Wed, Nov 26, 2008, 2:37 PM UTC

strlen wrote: post #44

JesseAldridge wrote: post #13

"The questions were about Linux systems administration, algorithms, computer architecture and C programming." Couldn't you just Google for the answers to these questions in order to bring yourself up to speed where necessary? I'm not sure I see the value in trying to keep vast libraries of arcana in your head at all times.

Part of the interview is an intelligence/memory/experience test. They don't want to use rigid requirements ("must absolutely have five years experience") and it would probably be illegal to administer an IQ test (and the sort of intelligence IQ measures isn't always the same as the sort of intelligence needed for the job). In addition their culture seems to be that once you're on the job (as a salaried employee vs. a…

I've heard you can freely move from team to team, but only if its one of the locally staffed projects at your office. Location makes a big difference.

Re: My Job Interview at Google

#112

Post by strlen » Wed, Nov 26, 2008, 11:23 PM UTC

webwright wrote: post #107

strlen wrote: post #92

Earlier quoted context omitted.

that's not very easy to do in a big corp environment. in a startup- it's a lot easier for both one being fired and the one doing the firing: being fired from a start-up can happen for many reason others than pure performance, where-as if one is fired from a bigger corporation that carries a bit more of a negative stigma with it. in addition firing in a company like google is expensive: there's three months of trainin…

Those are actually really good points... Hiring people is more expensive than saying, "Sure-- come on aboard. We'll see how you do!". That being said, I'm still not convinced that 10 hours of interviewing is any better than 2 hours of interviewing in terms of predicting success/fit in an organization.

I think 2 hours would be sufficient for 90% of the candidates. That's acceptable when you're in a start-up environment (where you generally have to fight for candidates and the pool is self-selecting to start with), but the 10% at Google could really make a big difference: google's pool of applications is bigger and the "laws of large numbers" come into play.

Also there's something else I haven't thought which is also a matter of "laws of large numbers": you simply can't hire every qualified one (and there would be opportunity costs in hiring the first person to pass the minimal qualifications).

Re: My Job Interview at Google

#113

Post by minoko0000 » Fri, Nov 28, 2008, 5:50 AM UTC

gaius wrote: post #10

josefresco wrote: post #7

The "I got interviewed by Google" articles are getting old for me. I just don't care, and their process isn't that interesting anymore.

Agreed. They have, what, 20,000 employees now? It's as exciting as getting an interview at HP or IBM.

This is my recent job interview with one of the above comapany . Aug - 1st Interview Sep - We really like you but can you wait for 2 months? Oct - I have another job offering .. I called the Hiring manager to confirm if he is really going to hire me. his exact words :" Yes of coz , reject the other company . It's confirm we'll start in the new FY. Don't you trust me? End Oct - hey , I need you to meet up w another dept hiring manager .. and when I spoke to the new hiring manager I found out that the role is totally different and doesn't fit my profile and my experience

Later did I know he hired someone else for the role.

Too big a company , too many employess , to value you is not the 1st thing in mind.

Re: My Job Interview at Google

#114

Post by andreyf » Sun, Nov 30, 2008, 11:08 PM UTC

andrewf wrote: post #85

webwright wrote: post #74

Earlier quoted context omitted.

I dunno-- I'm a big fan of "fire fast". If you can't detect a charming, conniving, free-riding bullshitter in 1-2 weeks of working with them, how are you going to detect 'em with 10 man-hours worth of interviews?

I don't see how firing someone after they've left their previous job behind is better for either the employer or the employee.

In this case, you'd also have to pay relocation/visa fees...