One of the unprettier sides of the hiring process in R&D is the on-site-interview stage, when the hiring manager (or one of his peers) gets to ask the applicant highly technical domain-knowledge questions. This can be done skillfully or poorly. It gets ugly fast when it becomes a hazing ritual based on riddle-solving.
![]() |
| The correct answer to riddle questions. |
My advice to job-hunters: Don't hire the employer who subjects you to such assholery.
When I say "don't hire the employer," I'm referring to the fact that a job interview is a two-way process. The employer is interviewing the prospective employee, but the prospective employee is also interviewing the employer. Each is hiring the other. Both actors should be asking questions. (Reasonable questions.) Both should be engaged in meaningful conversation. Meaningless riddles are out-of-band.
Reject a riddle by asking if you can have a more concrete, job-related question. Ask if there's perhaps a difficult problem currently receiving attention in the department you'd be working in. Ask if you can take a crack at that problem, or something just like it.
If you're lucky (and if the interviewer is anywhere near as smart as he or she thinks he/she is), the interviewer will pick up on the fact that you're a serious, pragmatic individual with domain expertise and intelligence, who is anxious to apply hard-won knowledge to real-world problems. You're not a game-show contestant.
A really stubborn, inflexible interviewer will stick to the riddle strategy and defend it by saying something like "I don't really care if you get the question right, I just want to see how you think." Which is completely ludicrous. A candidate who immediately produces the "right answer" to a riddle will always impress this kind of interviewer far more than someone who doesn't. That's the whole point of riddles. If a person really wanted to "see how you think," wouldn't he or she want to get to know you a little bit, perhaps draw you out with a series of simple questions? Wouldn't it mean engaging you in two-way conversation about something meaningful?
Ask yourself: Do you want to work for the kind of manager (or company) that sees its new hires as successful game-show contestants?
The right thing to do if you're an interviewer who wants to see how a candidate "thinks" (or "reasons" or "problem-solves") is to ask open-ended questions that are both job-related, and call for domain expertise.
If you're hiring a Java programmer, by all means ask an open-ended question like "What would you do if an application is failing because of OutOfMemoryErrors?" This could lead to discussions (and further questions) around a whole host of issues relating to checked and unchecked exceptions, memory leaks, garbage collection, design patterns, good coding practices, debugging strategies, etc. Within a few minutes, you should know a lot more about the applicant's qualifications than whether or not he or she bought this year's "most asked job interview riddles" book before coming to the interview.
Let's be clear. There's absolutely no need, ever, to subject an interviewee to questions for which there's a "trick answer." The hiring process isn't about tricks and games, is it?
If you're a job candidate and you feel an interview is going in an inappropriate direction, it's up to you to speak out. Don't forget, you're doing some interviewing here, too. Ask politely if you can have another question. If the interviewer sticks with riddles and says "I just want to see how you think," you're dealing with a certain kind of person (colloquially known as a braying jackass), so dumb it down and (politely) ask the interviewer if you can have another question, job-related, that will allow you to demonstrate how you think. You may even have to suggest possible questions yourself, if the interviewer is a bit thick.
Hire an employer who values the real you, not the game-show you. Unless, of course, you're into humiliation and Who's the Alpha Dog bullshit, in which case, may you find happiness and fulfillment together.

@Terry A. Davis: WTF!!!!!!
ReplyDeleteSomeone wants some time travel. Maybe, God will oblidge. Please?
ReplyDeleteGod says...
C:\Text\BIBLE.TXT
presents.
17:4 And the king of Assyria found conspiracy in Hoshea: for he had
sent messengers to So king of Egypt, and brought no present to the
king of Assyria, as he had done year by year: therefore the king of
Assyria shut him up, and bound him in prison.
17:5 Then the king of Assyria came up throughout all the land, and
went up to Samaria, and besieged it three years.
17:6 In the ninth year of Hoshea the king of Assyria took Samaria, and
carried Israel away into Assyria, and placed them i
The maker bot ammo story was so laughably parochial -- low level jailors, I'm highly confident my Internet is fiction. It's really stupid to make an issue of ammo clips.
ReplyDeleteObama is probably not president, if ther is a president. i don't know reality.
God says...
C:\Text\QUIX.TXT
this shall come to pass ere the
pursuer of the flying nymph shall in his swift natural course have twice
visited the starry signs. And thou, O most noble and obedient squire that
ever bore sword at side, beard on face, or nose to smell with, be not
dismayed or grieved to see the flower of knight-errantry carried away
thus before thy very eyes; for soon, if it so please the Framer of the
universe, thou shalt see thyself exalted to such a height that thou shalt
not know thyself, and the promises whic
Electricity would have seemed a risk in 1890. I don't have an interest in makerbots, so they slightly unnerve me but I'm pretty sure it's just like electricity, so in theory I should fight for their right.
ReplyDeleteAmmo clips doesn't sound important. It makes them larger. That doesn't seem all that important. Larger ammo clips from a MakerBot sounds silly to worry about. You can use small clips and you'll never stop some existing ones.
ReplyDeleteAnd I totally agree. Let interview coaching Calgary help you and learn from them some techniques for the best resume.
ReplyDeleteI agree with the point you are making. But I would like to point out that most bridge/boat crossing problems are trivially solvable with basic graph search. Which makes me think maybe it becomes a better question if you approach it as a cooperative exercise in designing a system to solve the problem. That approach also has great follow on question opportunities around generalizing and optimizing the solution.
ReplyDeleteGood day! This is kind of off topic but I need some advice from an established blog.
ReplyDeleteIs it hard to set up your own blog? I'm not very techincal but I can figure things out pretty quick. I'm thinking about setting up my own but I'm not sure where to start. Do you have any points or suggestions? Appreciate it
My page: Nike Air Max