Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

My interview at Google:

First basic recruiter basic questions.

Second part, call from Mountain View to London. They couldn't organize a VOIP line that didn't sound underwater. They tried calling again and the line was still bad. They proceeded anyway.

I spent 5 minutes answering a basic question about deploying some changes across a thousand machines, then the interviewer mentioned he'd heard part of it, but how would I deploy it across a thousand machines?

I talked about things stored in inodes, including POSIX attributes, he asked for an example, I mentioned immutable. Google: WHAT? Me: IMMUTABLE. Google: WHAT? Me: IMMUTABLE. INDIGO MIKE MIKE UMBRELLA ...

The whole call went along those lines and was generally a massive waste of time.

Apparently they were going to organize a second interview with a working phone line. They haven't gotten back to me in the two weeks since.



Recruiters' decisions have nothing to do with how you actually are as a candidate, but are usually made on somewhat spurious grounds. Apparently, this is also true at Google!

At least the blogger that is linked to got the tired "well uh we've decided you're good but you don't have enough experience hurrrrr" excuse instead of silent treatment.

To give them credit, they are probably shoveling through thousands of candidates, so it's very hard to actually give them all a proper chance, and there are positive consequences (narrow the pool) for cutting people out.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: