Slashdot Mirror
Google Adjusts Hiring Processes
Carl Bialik from WSJ writes "Google is attempting to fine tune its hiring process as it ramps up recruiting to keep pace with its success, the Wall Street Journal reports. From the article: 'In Google's early years, [Sergey] Brin or co-founder Larry Page interviewed nearly all job candidates before they were officially hired. A former Google executive recounts how, on occasion, Mr. Brin would show up for candidates' job interviews in unconventional dress, from roller blades to a cow costume complete with rubber udders around Halloween. Even today, at least one of the co-founders reviews every job offer recommended by an internal hiring committee on a weekly basis, sometimes pushing back with questions about an individual's qualifications.' While the interview process can remain 'glacial,' Google's new head of human resources notes that the average number of in-person interviews for each candidate offered a job has declined to 5.1 from 6.2. The company continues to seek overqualified employees who can be promoted quickly."
From TFA: "[Google] has traditionally focused a lot on candidates' academic performance and favored those who went to elite schools"
Nice to know that the new hotness is still the same old and busted.
I worked in HR for a while, and the boss there - someone I regard highly - had a saying: "Problems aren't encountered, they're recruited". By that token, the converse is also true. If you actively seek people who expect to do better things (not just want to), they probably will, and so will your company.
Word to the wise.
Meta will eat itself
Not at Google, there you can simply use a real-time computer-based translator to communicate efficiently ;)
python>>> q="'";s='q="%c";s=%c%s%c;print s%%(q,q,s,q)';print s%(q,q,s,q)
The results? Zero persons hired. And we are all card-carrying, Linux-using, OpenBSD-loving, certified nerds. Heck, just check my Journal if you don't believe me (Last entry: "How to compile gcc-4.1.1 on Solaris 8").
(All the names have been changed to protect the guilty, of course)
The moral of the story: it's tough kids. It's even worse than that. It's double-extra tough, with a heaping plate of steaming geekiness on the side. Is it worth it? Hey, don't ask me, I don't know. What I know is that we all now have great jobs, that are well paid, and did not take all this insanity to get. But these jobs are not 'cool' Google jobs, of course. YMMV.
Ask me again in a couple of years, when I try to get another job at the Googleplex...
The right to offend is far more important than the right not to be offended. (Rowan Atkinson)
When you delegate hiring to these, you completely f*ck up the future of any company.
These people, without knowing any little shit about really what a particular position would require psychologically and technically from an applicant, mess up whole system by putting forth absurd and utterly stupid "psychological evaluation" crapola in front of the candidates. Check this one out :
"You have come back late from work, and suddenly phone rings, and a group of 10 of your friends announce that they are coming to your place for dinner. You check around the cupboards, and find out that there is only one sack of flour and some pepper. What do you do ?"
Stupid bitch (in this case), i pick up the phone and tell the fucking friends to buzz off, of course. Moreover you are so stupid that you are totally incapable of realizing such above shit have the pitiful possibility of happening anywhere in this worldly civilization as :
1 - when you come home from work at 23.00 at night, noone rings and says they are coming to dinner
2 - only in military, and only high level officers can gather up a 10 people strong group at 23.00 in the night instantly.
3 - People after college do not tend to still live in and get around in herds.
4 - EVEN if somehow with great glory of existence such a crapola has happened, the most spectacular thing that anyone can do with a sack of flour, some amount of peppers and tap water is adding some water to flour and pepper, and showing the resulting mixture up his incoming friends' asses.
Furthermore, stupid bitch (in this case), you are SO stupid, SO overly away from realities is that the LEAST thing you would require in a production line supervisor mechanical engineer is extravertness, talkativeness, and high social activity. You are going to put him in front of a 15 m production line that never stops, constantly takes in raw materials and purports out intermediate parts. if you put someone with social wants or aptidude to such a position, chances are high that in 1.5 years time he will show up at work with a shotgun at hand and blow off 5-10 of his colleagues, probably including your bitchy (in this case) ass.
f*ck.
Read radical news here
I applied for a Software Engineering position at Google in Sydney being an Australian Resident a while ago. While I wasn't successful (it was a long shot, so I wasn't too concerned), I was utterly amazed at how incompetent their HR department at Mountain View was.
:-)
;-)
The story is as below:
1) So I get the 'thank you for your interest we really want to talk to you blah blah' email from one of the people in HR, requesting a phone interview from the US to my mobile (note: I live in AU), so I give them my full, prefixed international mobile number: +614XXXXXXXX, and we arrange a time. I was to be interviewed by their head honcho of Open Source Chris DiBona.
So, I wait patiently for a call a few days later, the phone never rings.
Turns our they couldn't get the number right, or at least, didn't know how to call an Australian international mobile number.
They said they left messages on my phone, but I don't have voicemail on, the mobile phone isn't an answering machine, and it's on and in full coverage all the time...
I only find this out later that day when I emailed them requesting what happened...
2) So, we re-organised the interview (over email with their HR people), again with Chris DiBona.
There's a mess up again, and nobody calls. Again, I waited patiently with the phone, awaiting for the call, nothing happened.
3) So, we reschedule the interview AGAIN (this time, not with Chris, but another person high up the chain who will remain unnamed). They forget to call.
4) So, it's a week and a bit later, as due to the time difference, the turn-around on sorting out these stuffups takes about 2.5 days each time.
I re-schedule again, but I don't pause my life for it anymore (decided to go to work anyway). Guess what, he forgets to call, and the HR girl who tries to contact me, forgot to press the '+' in '+61' to call my international phone number, so she couldn't get to me.
5) It's almost two weeks later now, and we re-schedule again, with a lady. I finally get a call in the morning.
40 minutes of questions on B+ trees and Index tables, and I'm done.
6) I get an email a week after that saying 'thank you for your interest blah blah, but you don't fit the profile for' - This being for a different job to that of what I actually applied for.
So, understandably, by the end of this all, I really didn't give a shit if I didn't get the job, well, at least the job I applied for.
My skill set is great, my academic record 'alright', but to be honest, if a company can't pull its shit together like that, then I'm really not that interested in working for them, regardless of the inherit 'coolness' factor.
In any case, I'm doing better now that I envisage I would be if I were simply a Software Engineer at Google in any case, but that's how things in life pan out don't they
I think you mean: "You're just the person we've been 'us'ing for."
In the mid-1990s, Microsoft had a problem: They just weren't cool enough any more. For the past decade, Microsoft's hiring strategy had worked on a very simple model: "Everybody wants to work here, so we just have to decide which people we want." When Microsoft stopped being cool, they suddenly had to work a lot harder, and in a completely different way, to attract the employees they needed. In a mature company, the hiring process works both ways; the applicant tries to convince the employer to hire them, and the employer tries to convince the applicant that they would like to have the job. Just like Microsoft ten years ago, Google is in the middle of shifting from "the cool place where everybody wants to work" to being one of many options to be judged each on their individual merits.
When I visited Google in August, I spent the entire day inside a 10'x10' room answering questions. When I asked questions of my interviewers, the response was always either "I don't know anything about that, you should ask someone else", or "I'd love to talk about that, but I've got a time limit and lots of questions I need you to answer". I don't blame my interviewers for this; they did the best they could. I blame HR for setting up the process the way they did. In the end, Google was absolutely certain that they wanted to hire me, but they hadn't done anything to convince me that I wanted the job they were offering. None of my interviewers took me to their corner of the building and showed me what it was like to work at Google; none of my interviewers talked about the interesting problems they had worked on recently; in fact, none of them told me even remotely as much about Google as I had learned in 15 minutes of looking at the Google jobs website.
Was the hiring process unusually bungled in my case? Probably -- Google HR had trouble figuring out what I do (which is a separate issue for Google to fix. Note to recruiters: If you can't understand something on someone's CV, ask someone with a technical background to explain it to you. The question "do you have a Master's degree?" should never be asked of someone who has a doctorate). But even if they had decided what job I was being considered for before starting to interview me, I doubt it would have made any difference.
If you want to hire good people, be prepared to spend at least as much time showing them why they should accept your offer as you do deciding if you want to make them an offer. "We're cool" may be enough to convince some people; but the smarter people are, the less likely they are to drink Kool-Aid.
Tarsnap: Online backups for the truly paranoid
"The company continues to seek overqualified employees who can be promoted quickly"
Remember, boys and girls: "overqualified" is simply HR's way of saying "can be underpaid."
How interesting. Much of the experience other /. posters have had with Google's HR are very similar to what I was put through when I interviewed with IBM in the mid '80s. And the opening (I hesitate to use the term "opportunity") at IBM wasn't even permanent: it was a 6 month contract.
First, it took 3 attempts to connect for a phone interview, and there was a significant degree of consternation at IBM that I would not permit such a call during the day (while I was working at a client's office). Then followed in person interviews at their Canadian head office, during which it became obvious in a hurry that they had not read my resume or confused it with another (my degree is NOT in Engineering from U of T, and I have NEVER worked as a mainframe systems programmer). Five different people, 4 hours. The only part that was really interesting was the lunch in the IBM cafeteria, where I quickly grew to understand where the "Big" in "Big Blue" came from.
Another phone interview followed, and then, despite two follow up letters from me, I heard nothing, so I just assumed that they were not interested and did not have the courtesy to contact me to tell me so. Fine. I took another contract I was interviewing for, and forgot about them.
Four months later, I got a phone call from IBM asking me when I can start. Huh? You think I'm going to wait around for 4 months while you decide? What planet did you say you were from?
What I took away from that experience was this: when HR and the company hiring process gets seriously confused and out of control, the company suffers big time. IBM had to take a major kick in the pants before they smartened up. Until they did, they were heading for irrelevance very quickly. I'm guessing that Google might have to go through the same thing. Not for a while, because they have a strong core and strong growth. But sooner or later it will happen. Every week that passes by, they take one more step away from upstart towards mature. And in IT, mature = complacent = stagnant = doomed.
How about a piece about people who turned Google down? Google were desperate to hire the writer of SquashFS onto their team of geeks, offering him all sorts of incentives to scrabble aboard (this was pre-IPO too). He turned them down because he didn't feel he would be free enough to continue development of SquashFS.
Kudos to the geek who puts OSS before a cushy job at Google and untold wealth in stock options.
Phone your friends and arrange for them to come around in order of size starting with the largest first.
Slaughter the first 3 as they step through the door and fry them up with peppers to provide a magnificent feast for the others. After you've eaten they can help you clean up the apartment and learn a salutory lesson about what happens to people who demand they come around to your house and eat your food without being invited.