hard to think of a halfway competent developer failing to answer
"where I ask them to implement a simple function, implement a recursive function, write a simple SQL select (join across two tables), and create a simple object model (how would you represent a car as an object)."
in about a minute or so all told, even verbally, over the phone.
"YouTube phone interview because they asked me to "say" a function for finding the longest common subsequence of a set of strings."
This is (ever so slightly) different from OP's ultra simple questions above , but otoh , YouTube has a lot of tough algorithmic problems to solve. I am not sure what position you interviewed for, but the question itself sounds decent for a position that could involve algorithms and searching and so on. Now if the interview were for a job involving "code up a basic enterprise app" I can see how it could be inappropriate.
All that said, I am not a fan of extended phone interviews , but asking very basic questions (as the OP seems to have done) eliminates a surprisingly large number of looks-good-on-paper-but-can't-code-for-nuts type "programmers".
The key to not getting depressed is not to waste any time on people who can't answer ultra basic questions. If in 30 seconds you feel someone is too incompetent, shut the conversation down politely. Spending long periods of time with incompetents is depressing.
One solution is to send a (moderately complex) programming problem by email and ask them to send code back. This will weed out a lot of people without wasting your time.
I find anyone who immediately blames the environment for their lack of ability to answer the questions correctly to be suspect. These types of complainers are externally motivated and will never accept fault for their lack of capabilities. "You should have asked me in a different way." or "I need to be taught differently" or "There's too much pressure"... look, you can come up with whatever excuses you want, but the fact is, you can't solve the problem and what we are looking for is someone who can solve problems.
Case closed.
I don't say SQL queries out loud, and trying to do so would probably screw me up; I don't know about you, but I don't sit down to write stuff and get it perfect every time. I often start writing a query, go back and adjust something, start working on another part, tweak this or that, and then finish. You can't do that when you're forced to say something over the phone. And I don't solve problems I've never come across by just starting to code on my own and see where it gets me; especially when it sounds like the kind of problem that someone else out there, probably smarter than me, has already solved. AND I wouldn't want to hire anyone who took that approach. Sometimes, it's fun to reinvent the wheel, especially when you're trying to learn things, but I wouldn't want my developers sitting around all day reinventing everything.
If you really want these people to do these things, plop them down in front of a computer, give them a time limit of x minutes, leave the room and come back and see where they are. This relieves the pressure of you standing over them watching them, gives them time and space to work the problem out, and is much closer to how they'll eventually be working...unless you work at some freaky place where the boss stands over your shoulder and watches you type all day long, in which case I feel sorry for you.
Don't forget, our society rewards extroverts, is built for extroverts, and this is one way the ruling extroverts can weed out introverts.
There are definitely people who are capable of solving problems but whose performance drops appreciably under pressure. Now, you may not want to hire those people, but that doesn't mean it has anything to do with external motivation or making excuses, and you can keep your contempt for yourself.
There are many different kinds of pressure. The pressure in an interview is very different from the kind of pressure experienced when the database is down.
For example, I have no problem at all with on-site interviews but I choke pretty easily during phone interviews. I also have no problem with public speaking, but I have trouble engaging people I don't know in one-on-one conversations.
Appeal denied.
We don't ask trivia questions (what's the order of arguments to fputs, list all the overloads of foo in class bar) because knowing that (or anything else that's a 5 second lookup or context-sensitive help away) doesn't predict how someone will actually perform on the job.
Can any of us code as effectively on a whiteboard as we could in our favorite editor? I'd expect not, and if you were equally able on a whiteboard as in an editor, I'd wager that it's because you're not particularly good at either.
I mean, still coding without a computer - but it's something about standing up at a whiteboard. Maybe it's normally not so bad for me, but with the pressure of an interview, it's bad enough to give me problems.
I think my style is more trial and error, I make something and see if it works, if not I continue. So of course, a lot of great programmers actually are able to do that, but I think there are also a lot of people who work like I do.
I think you'd understand how I can take your argument to its extreme conclusion and justify posing psychotherapy problems to candidates.
You're seeing complaining where there isn't any. It's in the employers interest to ask questions that will narrow down candidates in a way that best fits the job. Putting candidates under extremely unusual circumstances and pressure to answer unrelated questions is only going to help you know how the candidate responds to unrelated questions under extremely unusual circumstances, and pointing this out is not complaining. Acknowledging that a high pressure phone interview does not accurately reflect your abilities is not complaining either.
I think it doesn't matter if it is consistent for all the candidates. A company can't change to suit every employee. Working for a startup like Youtube is high pressure. You have to be very self-aware and able to work under extreme circumstances. When your app crashes and millions of people are angry, you have to fix it! You can't create a special case scenario for your employees because they need to work in a stress free environment.
Of course that is a simple case, but high stress engagements occur at some point in almost every environment and how the candidate reacts to the high stress is very important, perhaps the most important.
IMO, it is more important for the employee to adapt to the environment than for the environment to adapt to the employee. Every candidate is going to want questions asked a different way. Every candidate is going to want their cube to be a different color -- that's why they are all gray or beige.
My point is, if you want A players on your team, you will be well served to waste as little time as possible on candidates that want you to ask them interview questions the way the candidate wants them asked and focus your attention on candidates that correctly answer the questions how the interviewer wants to ask them.
You make a case for developers needing to be able to handle "high stress" or "high pressure" conditions. Those are pretty broad terms, as they could mean anything from "very competitive and high standards" to "quick firefighting emergency work 24/7" to "your boss will micromanage the living hell out of you". So, in effect, you're saying, "Look, you complainer, working for YouTube is like being in a phone interview all day." All I can say is that if that is true, I am certainly not a match.
This is I think the best solution. A friend works at a company here called Tachyon and they have this part as part of the form on their jobs site where you can apply for jobs. http://tachyon.in/jobs.html
Once I'm alone at my desk though it's easy to get down to business.
Think it would be cool if companies just said show up to work, and you work for free for the first week. After that both parties can decide if they want to continue.
It works both ways. You are selling your time. They are selling their environment.
The problem is that the employer is accepting a lot more risk than the employee. Do you like paying for something you can't return and you can't get your money back for if it is crap? This is the situation a lot of companies are in. They hire someone, they pay them to write the code or build the project and it turns out it's all a lot of garbage and the company is out the money.
This problem is really tainting our industry. I think a lot of people who call themselves programmers are really just some kids off the street who grabbed an open source package and started hacking away. They can build a website with some graphics and stuff, but they have no vision, no experience with large systems that are actually going to be used for any significant period of time.
It is quite depressing actually.
How the hell does someone with a job arrange to take a week off to do this trial period for another company? Maybe it works for entry-level or the unemployed, but I don't think you'll find a lot of good senior developers who would be able to make this arrangement work. I've taken jobs entirely based on their interview process. "If I made it through that, and everyone else I'll be working with also did, I'm pumped to work with these people!" Same benefit would apply to the week long trial, but making it work logistically is difficult.
So would I. But since I'm WORKING for that one week, I expect to be paid for it. I really don't think anyone should be surprised by that!
A lot of people think of work as "sitting in a cube."
The question is, "How do we determine if the candidate's definition of work matches the employer's definition of work?"
Maybe what you think you are doing when you are working is actually causing more problems and moving the company backwards because they are going to have to undo all the crappy code you wrote. I'm not meaning to attack you, I'm just trying to illustrate a point. Know what I mean?
Maybe such an engagement could work out where, "If we hire you, we pay you for the week. If we fire you, we keep the money and you are out."
This reduces the risk for the employer while also giving the employee a chance to examine the company and be paid if the work is satisfactory.
Furthermore, I have no interest in reducing the risk for the employer: I expect them to do that. I reduce my own risks. If I'm the employer, then of course my perspective will shift 180deg.
FFS, it's a job, not a hobby!
How about a one week stipend. You're view point is too company-centric, I MUCH prefer to work for people-centered companies. Either way you need something a little more symmetric if you don't want to become standard laughing stock among developers. (Or maybe you and your-co are so badass you can't do wrong and developers intrinsically trust you so it doesn't matter.)
Many information systems can be implemented in a week. You could set up email, an e-commerce site, a CRM, SCM, or even substantial portions, if not an entire ERP system depending on the size of the company.
A week is a long time if you know what you are doing.
By not letting someone acclimate to your tech environment, your potentially shoving them off on the wrong foot (not to mention stressing them the fuck out,,,which WILL kill their productivity). A mistake that could cost you months of 50% productivity because you didn't (as a company) empower your developers to do their best work.
When I see managers pulling some "whip them harder" management styles, I can't help but be left with the want to remind them about the french revolution. Pointy-haired bosses will soon figure these things when "their" work force becomes a bit too empowered.
Well, the candidate would be giving away a week of his time, which can be a bit problematic. How would you arrange this if the candiate was already employed?
He'd take a week of unpaid vacation from his current workplace, and give it away on a chance he might want to switch jobs and be accepted? Besides, 1/4 of your monthly salary is definitely a noticeable loss.
What if this was a common practise? "Oh well, this didn't work out. I'll take another week of unpaid vacation to try out for that other company then"..
A lot of people think of work as "sitting in a cube."
Working for some place means exchanging your time for money. Whether that time is spent coding with a burning passion, moving a company in a desired direction, or looking at lolcats is another matter.
i'm perfectly willing to write code as part of a job interview. just not on a whiteboard or over the phone.
why not on a whiteboard?
Those skills, (being able to code complex problems when people are watching) have never been a requirement of any job I've seen so I've come out of many interviews feeling that they got an inaccurate picture of my skills.
If you try hard enough, you can be familiar with likely interview questions and then the problem is how best to present your solution, which is an important skill, and one worth practicing.
But to solve something say from project Euler on a whiteboard in front of three strangers and talk about my thought process at the same time, that's hard.
Good luck with your search.
Shameless plug: If your interested in a development position at CollegeHumor in New York City... Email [email protected].
That's rough, asking for a solution to an NP-hard problem over the phone? http://en.wikipedia.org/wiki/Longest_common_subsequence_prob...
Or maybe they were just expecting you to say "for each combination of subsequences of each string, check if they are equal ..."
http://en.wikipedia.org/wiki/Longest_common_substring_proble...
That's an interesting problem with some simple solutions worth understanding. I don't think it would be unrealistic to expect a high-quality programmer to be previously familiar with it, or, if not previously familiar, to be able to make progress toward the DP solution with some thought.
Good Point. And asking a clarifying question would be a very strong positive in a candidate.
Of course, I failed their day-long battery of on-site interviews later. But I did get interviewed by the entire development team, plus the CEO. That was kind of fun.
For example I consider myself a reasonable programmer, I can certainly do any project put in front of me. But I failed a YouTube phone interview because they asked me to "say" a function for finding the longest common subsequence of a set of strings.
I learned the following issues completely stop me from being able to program:
1. Someone waiting on an immediate answer.
2. Someone watching/listening to my though process.
3. Not being able to experiment with the code on a computer.
That didn't cut it for them because apparently at YouTube a lot of your programming is done over the phone (sarcasm).
I guess my point is, try to think of the exact tasks this hire would be doing, and ask them to do that. Will they really be writing recursive functions often? Also if possible give them a take home project, so they can work in a more natural environment.