How to divide programmers into categories (jun/mid/senior)?

D

Denis Savitsky2014-10-20 09:58:45

ruby

Denis Savitsky, 2014-10-20 09:58:45

The bottom line is that there is a project, 8 programmers have been working on it for several years, their tasks always intersect (today one fixes bugs in the RoR project, and tomorrow he sets up the network), moreover, while the salary levels and the kpi indicator, as such, do not defined at all. How to determine who occupies what level (from this it is already easy to determine the levels of salary)?

Reply

Answer the question

In order to leave comments, you need to log in

5 answer(s)

S

Suvo, 2014-10-31
@qweewq

In our company, we recently came up with the following scheme:
https://gist.github.com/Houdini/56211da3abb637c73907
It is not final, however, it has several important principles, in my opinion.
1. Encourage non-trivial solutions at the current place of work
2. Encourage open source
3. Encourage learning new technologies

V

Viktor Vsk, 2014-10-20
@viktorvsk

That is, you have a project that has been normally supported by 8 developers for several years and then you want to lose some of them, give some of them a reason to look for a new job, and some just reduce the desire to work?

P

Puma Thailand, 2014-10-20
@opium

I think it's not difficult to gather three leading programmers and sit with them for 10 minutes and scatter people into ranks according to their ability to motivate.

V

Valentine, 2014-10-20
@vvpoloskin

Probably, as in all other areas, not only programming.
We look from the height of the flight, who made the greatest contribution to the work, who works in the project earlier, who is more disciplined, who is older in age (the criteria are in descending order of importance).
We give the positions of a programmer, a senior programmer, a lead programmer, a head of a sector...
There is no need to enter the positions jun, mid, sen if you have not used them before. Who will be pleased to work in a position and get a demotion, albeit in a title.

V

Victor Maslov, 2014-10-30
@Nakilon

The amount of salary should be proportional to their contribution to the given project, and not depend on jun/mid/senior -- after all, a person can be a hundred times better programmer than another in all respects, but for a particular project it may turn out to be more useful tons of shitty code than quality.