views:

579

answers:

4

So I'm leaving my job for a role at another company and before I leave I have one last task: I must hire a replacement for myself <gulp>. The reason for the <gulp> is that this is the last thing I will do for my team, and I really don't want to leave them with a dud as they are great bunch of guys.

As a team lead I've interviewed for developers before with mixed success - from my perspective recruitment seems really tough and it's not something you get to practice very often. However there are already some excellent posts on Stackoverflow on the subject of hiring pure developers. I've been through these and got some great tips on the technical side of the recruitment process.

The problem I'm facing is that the skills that I need for my job as a team lead are very different to those required for a developer. The successful person needs to be part man manager, part project manager, part problem-solver-in-chief, part agony-aunt. They've also got to be able to stand up in front of clients and management and give a good account of themselves.

So any thoughts, advice, shared experiences or pearls of wisdom on the subject of hiring a team lead would be greatly appreciated.

Suggestion: Jorge makes a great suggestion - get the team involved in the process. Get the candidate to sit down and talk to each team member and quiz them about what they working on, how they are going about doing it. As a nice twist we could get each team member to pose question/problem to the candidate about what they are working on.

+14  A: 

You've worked with your team for the last couple of years. I guess they trust you and you trust them. Why don't you let them choose?

I'm not saying you should just blindly let them pick the project leader they want but I think you can involve them in the selection process. You could even let them take part in the interview... let them have a say in who is gonna lead them. If they feel comfortable with him, if they feel they've choose the guy they'll probably will work better with him.

Also consider a team member to do your ex job. They know the bussiness, they know how things are done and they might be good at it. If one of them is interested, at leas take it into account.

Jorge Córdoba
+1 completely agree - especially on the aspect of involving the team in the selection process
jpoh
Lots of references to 'him' in this answer! Just thought I'd point it out. :p
ThePower
Recruiting from within the team was the first thought, but unfortunately it's a no-go. Either they are too inexperienced, or else don't want the hassle and baggage that comes with being a team lead
Steve
I really like the idea of getting existing team members involved in the process somehow. Maybe I could get prospective candidates to sit with the guys and ask them about what they are working on, what they think about their current project etc.
Steve
The power, sorry about the him :) No offense intended...
Jorge Córdoba
agree... when you interview have a couple of your team members from the team sit with you (not //just// one-on-one) and see how the interaction goes... As a bonus you get to see how the candidate deals with a stressful situation -- the panel interview.
beggs
This is a great idea, assuming your team members don't have hidden agendas. I'm glad that you clarified that none of your existing members want the job, as a jaded team member could cause a lot of damage. As a compromise, I would suggest getting your most senior members involved.
Jin Kim
Depending on the team members of course but one risk with bringing everyone in the team into the process is that they might not agree. As a result there is a risk that the few that put their vote on another candidate will feel grumpy and that the new team lead will have to spend too much time trying to win them over. I have seen this happen a few times and I think it is better to let a few (2-3 of them) who have the team's confidence be part of the process.
Fredrik
+2  A: 

I think that the key thing that you should grill a prospective team lead over is management style.

Now obviously you cannot ask "What is your management style?" <grin>

You could though infer it by asking leading questions like that old chestnut "Why are you leaving your current job" or, more subtly "What has your greatest frustration been over the last 6 months?"

You want someone that will take other people's opinions into account without not having one of their own, and also have the stones to take a stand, both with management and with the developers, if either is being unreasonable.

Team lead can be a difficult job :-)

Joon
oh yeah, I'm hearing that :)
Steve
I think this is also a really good suggestion: tell me about a team you have managed in the past, tell me about a problem you faced with a member of you team, tell me about a management-type problem...
Steve
+1  A: 

Why not pick one of your team members?

By now you should already know what the strengths of each are.

flybywire
Unfortunately this is not an option, either they lack the experience or they don't want the extra responsibility
Steve
+2  A: 

just to add you may want to see my answer on SF..has some relevance on processes.

You can then adjust for the technologies -way you develop ...

You can then ask the team, and management what they want from the team leader and incorporate that.

http://serverfault.com/questions/11908/how-do-you-interview-a-database-programmer-admin-applicant/13572#13572

this is quite a neat approach
Steve