Recruiting Good Team Players

Good evening, guys! When gathering a team for joint work on a project, you should determine whether a particular person is a good team member or not and whether his skills and personal qualities are appropriate enough for the productive work. Knowing how to distinguish a perspective candidate from an unsuitable one can be crucial to your project management success. Each company's HR has its own ways and tricks to deal with the goal, but is there an unified algorithm to avoid mistakes in hiring employees?

In the army there is a wonderful, in our opinion, criterion, by which it is not difficult to distinguish a good soldier from a bad one. It is about the expression: "I would not go in exploration with him". Indeed, when it's asked about the consistency of the combat comrade, the criteria can differ a lot, and each of these criteria vary depending on the advantages and experience got. For someone it is important whether the partner shoots well and runs fast. Another one is looking for somebody who is silent and cooks tasty. And the third one needs a person who isn't afraid of snakes and is able to control a combat helicopter. Trying to create any more or less universal list of required qualities and properties of a fighter, we very soon skip to the listing of characteristics of some kind of RPG like "Fallout" or "Skyrim". And it will be extremely difficult to distinguish a good fighter from a bad one.

But the following subjective assessment of a comrade-in-arms will very easily make it clear whether this javascript developer is a good fighter or not very good. Ask yourself two questions:

  • Would you agree to work in a project where he is a team lead?
  • Could you trust him with a task which you are responsible for?

If both answers are "no", then such a fighter needs to be urgently sent to the building battalion and kept away from the production.

Team work

Riter development team