Last week I posted the following to twitter, somewhat inspired by Margaret Heffernan’s TED Talk on the Pecking Order and also by my own experiences in being interviewed and interviewing applicants for jobs (some ideas captured here in a earlier post/rant on broader dysfunctions).
Some questions in interviews are valid but when it takes a demeaning, condescending tone – that’s when you know you’re in trouble.
Friend and colleague, Ryan Musgrave, in response, posted this video from Jacob Kaplan-Mosson (a self confessed mediorce programmer), which is related to the subject. Those 10x programmers that some dream of hiring just aren’t as thick on the ground. In fact hiring them could also reduce the through put of your team (read Five Dysfunctions of a Team to get a real life account of this).
We mostly fall in the middle for talent
We mostly fall in the middle of a normal distribution as the video explains. It’s time to stop dreaming of hiring superstars and look to develop the skills of high potential applicants. They needn’t know the Agile Principles off by heart or recite every little bit of Object Oriented doctrine that could easily be memorized anyway.
Look to test applicants on more meaningful questions about how they deal with technical problems, how they learn, how they deal with people problems. Again these need not be perfect answers but should give you a feeling of potentiality. Ultimately a good applicant wants to develop mastery in what they do. Think of questions that will give you clues to this and give you a feeling of genuineness.
Ultimately Values, Principles and Philosophy should align best they can. If your own Vision is strong then finding those who want to follow should not be hard. As those looking to hire, perhaps starting there and looking inwards is the place to start.
Those feeling belittled by by the superstar programmer, take solace, also look inward and look to get the best out of yourself. If your a superstar programmer and maybe not as generous to others in the team, you can improve as well by helping others to improve technically. Collaboration is hard but does reap many benefits personally and for others and for the bottom line.