When assembling a team, you need to think not so much about seniors and middles, but about the distribution between those whom you will hire for a fix, who for an hourly rate, and who you will generally assign small chips to in a project. You need to think about the “team pie”, in which the “kernel on the fix” is just one of the layers.
They can be taken on an hourly basis by mentors to solve highly specialized tasks. Because if you take a crowd of seniors, You will receive learned advice – he will advise a lot and will do nothing.
Hours are very convenient because you can always get the necessary competence, even if there is an overestimated rate. For the budget, hourly schedules are generally very convenient: they are much softer for a financial plan than fixed ones. The fix gives rise to millions of rubles a year of expenses for each specialist, and the hourly work – an insignificant% increase in expenses per month. Financiers for attracting hourly workers will kiss you tenderly in the ass and love you with all the fibers of your soul!
A typical example is working with an external DBA.
There must be pluses from all sorts of Yandex Workshops, Skillboxes and Gikbrains! Their main plus is in the aggregation and organization of hundreds of different people who want to “enter IT”! Part of the routine operations can be safely given to a crowd of students. Due to their number, decent quality can be ensured.
Interns are the most fertile material for growing and throwing off any routine on them: they are highly motivated, there are many of them, and they themselves bring in their beak what they were taught. And this is actually the primary source of new new knowledge and new competencies. Yes, they may not understand much about this, but they can be used as a transport for knowledge – it is important to simply extract them correctly.
A typical example is working with monkey testing teams, when you need to run a complete regression based on ready-made test documentation and test cases.
Freelancers for project work
You can also dedicate small project tasks to some people, keeping in touch. This is the coolest group of performers – their very presence makes specialists from any other layer of the pie VERY accommodating. Friends had a case when a team could not migrate a database from one DC to another for almost a year. When their former colleague was called on a freelance basis, the team did a job in one night that the YEAR could not beat!
A typical example is the development of landingos.
Development team core
And only the very core of the business is given to fixers: this team lives in luxurious conditions of a “country rest home” – coffee, buns, masseuses, etc., etc. Their value is not in super-duper qualifications, but in immersion in business processes. This is what they need to be pumped up with – understanding the product and where it grows.
A typical example is billing development.
What are the advantages of this approach?
There are many of them, since the “pie” solves the problem of any competence management in general. Besides:
The budget is not inflated;
In none of the layers does a point specialist appear, on which everything depends;
Increased readiness to instantly respond to any changes in the business;
Personnel reserve for all occasions.
And what are the disadvantages?
Cons mainly stem from carelessness and lack of experience with such a “pie”. If an inexperienced leader tries, for example, to instruct an unfamiliar hourly worker to write the part that the “nuclear” team should actually do, then later, from the result of the work of these “hourly workers”, one can tear gray hair in all places. For they are actually not responsible for these consequences even in a short period of time. And most importantly, they do not care about the result, because they do not need to work with it further.
Thus, the “team pie” acquires responsiveness – there will always be the right specialist in the “personnel reserve” from the “academic council”. Until he entered the “core” of these specialists, you can shuffle dozens or even hundreds, and do it for free. Thanks to responsiveness, only the coolest specialists, filtered by interaction with the core, can get into this very core. The core provides stability, and all other layers – readiness for any changes.