Kimberly Blessing is a computer scientist, a Web developer, a standards evangelist, a feminist, and a geek. This is where she writes about life, the Web, technology, women's issues, and whatever else comes to mind.
How not to recruit talent
Robert Scoble alerted readers to Jeff Barr’s post about Google recruiting. I had to laugh out loud here, because I’ve also been subject to some strange Google recruiting crap myself.
Most recently, I got an e-mail from a Google recruiter (who clearly did look at my Web site, because she commented on the pink-ness of my blog) with regards to a technical solutions engineer position. The first thing that struck me as odd is that, if you actually read my resume, you’ll learn that I’ve been in management positions for a while… so why would I be interested in an engineering position? The next oddity was the requirement that I complete a self-evaluation before discussions could proceed. Uh-huh. No thanks.
Of course, when I got that e-mail I was laughing pretty hard, because in the many years I’ve attended the Grace Hopper Celebration I’ve talked to Google folks many times about job opportunities there — and was basically told again and again that “Google doesn’t recruit Web developers because that’s not important to [their] business”. Whatever.
I have some friends that have gone to Google, but honestly, the more I learn about them, the more suspicious I am of them. I feel like they’re one giant social engineering experiment, and we’re all their guinea pigs.
Comments (1)
I’d have to agree. I’ve had a few friend’s that worked at Google and their practices are definitely a bit odd at times. In many ways, I think they’re just as bad about this kind of stuff as other companies, they just have a good PR team spinning it.