Making Sure Interviews Don't Turn Into Free Consulting
We've talked in the past about what kind of questions should be asked of potential developer hires, and how being honest in exit interviews probably isn't worth the potential damage to your career. We're also familiar with the tricky questions some interviewers like to throw at people to test their thinking skills, and the questionable merits of gauging somebody's skillset through a pointlessly obtuse math problem. But there are also shady employers who conduct interviews to try to mine your knowledge and experience to find free solutions to their current problems. An actual job may or may not be on the table, but if they can get what they need from you before hiring, then at the very least your bargaining position will have gotten worse. Have you dealt with situations like this in the past? Since you can't know for sure the interviewer's intentions, it's tough to provide an answer demonstrating your abilities without solving their problem. "Before asking about the fixes they’ve tried, start by acknowledging the depth of the problem and find out whether the manager has the resources to solve it. Then, just like a consultant, use their answers to highlight your experience and explain the approach you’d take." You could also try explaining how you've solved similar problems, which won't necessarily help them, but will demonstrate your value. Of course, one of the biggest challenges is determining when somebody is getting a little too specific with their interview questions. What red flags should people keep an eye out for?
"Before asking about the fixes they’ve tried, start by acknowledging the depth of the problem and find out whether the manager has the resources to solve it. Then, just like a consultant, use their answers to highlight your experience and explain the approach you’d take." You could also try explaining how you've solved similar problems, which won't necessarily help them, but will demonstrate your value. Of course, one of the biggest challenges is determining when somebody is getting a little too specific with their interview questions.
Is this serious? Here's a big red warning sign for me: if my job can be jeopardized by twenty minutes of talking, I'm probably in the wrong industry. I can tell you how to implement a solution but it's the actual work and planning and care that should be paid for cash money.
What red flags should people keep an eye out for?
Here's a red flag: What company out there is so full of morons that they go to interviewees for direction? Man, if I ever got that feeling in an interview, I wouldn't want to work for them anyway and I'd walk away laughing when they try to turn small talk into a business plan! Is this why "consulting" is so stupid? They can have all the free advice they want, it's still going to shit out half way through when they go, "Okay we have hadoop and lucene, what was that 'blur' thing he was talking about?" or "Okay, we've built a rails app with the generator and scaffolds ... now what did he say about creating database migrations?" and on and on.
I mean, are there actually people out there that feel their job can be compromised by handing over thirty minutes of talking to a potential employer? The only thing I'd be worried about is if they started asking me to name names for other people they could hire.
My work here is dung.
only programmers and IT geeks would be so conceited as to even think this is a possibility.
"They were pure niggers." – Noam Chomsky
Strictly speaking, this wasn't an interview; but I think it applies.
Many many many moons ago, a friend asked me if I would be interested in setting up a Novell network for his employer. I put together a quote and sent it off. He called me up, and said that he needed a detailed walk-through of the work involved in order to explain the quote to his boss. I explained everything that was necessary. A couple of weeks go by, and I haven't heard anything so I call him. After learning what needed to be done, he decided he could do it himself; and that was the route they were taking. Lost a 'friend', but gained a cautionary tale; I think I came out ahead. (Yes, Jeff; this story is about you.)
-- This sig is only a test. If this were a real sig it would say something witty. --