Some years ago, someone at Microsoft noticed that they were having a bit of a Resources problem. A Human Resources problem to be specific. There were a whole lot of job openings (thousands, in fact) and a whole lot of applications (hundreds of thousands, in fact), and no easy way to match the right applicants with the right jobs. So they decided to reinvent the Job Interview.
Traditionally, job interviews are used to ascertain two things: how competent the candidate is and how well his personality (or lack thereof) will fit in with the organization. With their introduction of Job Interview 2.0, Microsoft included both of those features and added one additional: how the candidate responds when presented with asinine, utterly pointless, and completely ridiculous brainteaser questions.
Of course, common sense tells us that a candidate who enjoys solving silly riddles would most likely enjoy solving a silly riddle at a job interview. The same can be said about pepperoni pizza: chances are, if a candidate enjoys eating pepperoni pizza, he will also enjoy eating pepperoni pizza at a job interview. Both are facts which, while completely enthralling (no way, you like pepperoni pizza, too?!), are equally as irrelevant when determining whether someone would make a good programmer.
If you havenít seen any of the Job Interview 2.0 questions offered by Microsoft, here are a few:
* How would you determine the weight of a Boeing 747?
* Given an opaque box with three light bulbs inside and three switches outside, how would you determine which switch corresponded to which bulb if the box could be opened only once and only after all the switches were permanently set?
* You are at a ravine with three others and need to cross a rickety bridge. You can cross it in one minute, the three others can cross it in two, five, and ten, respectively. A flashlight (your group has only one) is always required to cross, and only two people can cross at a time. How do cross as quickly as possible?
Naturally, being that theyíre brainteasers, no common sense or practicality is allowed. And this is precisely why I would fail miserably at this part of Job Interview 2.0:
* Iíd ask BoeingÖ I canít ask Boeing?! Uhh, Iíd ask a librarianÖ Of course a librarian would know, they look stuff up, thatís their job!
* Who would build such a stupid, broken box? Iíd fix it of courseÖ I havenít even seen the stupid box! How do you know I canít fix it?
* Obviously, weíd leave the slow guy behind. Weíre clearly in a bad place, in a bad situation, and we donít have any time for the big fat fatty to slow us down. Itís survival!
Thankfully, Microsoft realized that the type of people who enjoy these riddles arenít always good programmers, and good programmers arenít always the type who enjoy these riddles. In fact, some of the folks who can solve these riddles are precisely the type of people you donít want as programmers. Would you want to work with the guy who builds a water-displacement scale/barge, taxis a 747 to the docks, and then weights the jumbo jet using that, instead of simply calling Boeing in the first place?
Unfortunately, Microsoftís realization came too late: a whole mini-industry has spawned around the concept of Job Interview 2.0. If Microsoft did it, it must work, right? There are books written on brainteasers in the interview, consultants who will help your company annoy the hell out candidates with your very own custom brainteasers, and now, everyone from small software firms to big oleí banks are asking stupid riddle questions.
They will eventually realize how useless of a practice this is. They will eventually give it up. In the meantime, however, you Ė the job seeker Ė will have to put up with it.
Or not. One reader shared with me the story of his brainteaser interview.
During a screening interview, I was asked how I would design a bike fit for someone visually impaired. I responded something to the effect of, "What, like, for blind people?", and she answered yes.
I thought for a moment and then I responded, "Well.. a blind person riding a bike doesn't sound like a very safe idea, so I would make the bike stationary, maybe with a fan blowing in the person's face. He probably wouldn't even know the difference."
She was speechless.
Now, granted, he will not get the job. Despite the complete absurdity of the design request, and the complete practicality of his answer, the job will go to a candidate who manages to answer the question by designing an extremely overcomplicated solution for a completely non-existent problem. And that candidate will be the same person who designs their software.
I promised myself some time ago that if I was ever asked such daft questions and riddles at an interview, I would walk out there and then. I hope I keep that promise.
These questions are alive and well in smaller job interviews as well.
My daughter was being interviewed for a construction industry job this week and was set the task of imagining the 4 interviewers were aliens and new to earth. She then had to describe what Ice Cream was to them.
First question she asked was 'Do you speak English then?'.
And she's been offered the job!
'imagine 4 polish plumbers are new to the UK, you have the task of explaining to them why their services are no longer required'.
suitable questions to ask the 4 poles: 'Have any of you heard of the credit crunch ?'
Why is this flagged as NSFW?
If you gave the answer "I would use Google to find out", would you get to meet Steve Ballmer?
There are currently 1 users browsing this thread. (0 members and 1 guests)