Profession SDE (software development engineer)
Yesterday. spoke So today I decided to continue this topic and talk about SDE. This topic is interesting, since the main composition of tech companies are developers, but often in large companies they do not have much unity:
- They are divided into conditional directions backend, frontend, mobile, ... Within these areas there are divisions by language. n (c++, go, java, .net, ...)platforms (iOS, Android, cross-platform)framework n (Angular, React, Vue) and so on
I can see why this is happening.
- It's all about hiring, and it's easier for the hiring manager to say, look for a javist and it's easier for recruiters to find them.
- It's all about interviews - what do we ask a conditional Javist by his language?
- It can be tied to the matrices of competences - what we expect from the javist within his toolkit.
- It can be tied to the standards of the profession, general tuling and so on - it is convenient when all the Javis in the company on the same wavelength. (For example, we have a framework. kora for Java applications in Tinkoff)
But sometimes such a fragmentation interferes and, on the contrary, greater unification is required. In the case of a general vision matrix for SDE, where there is no stack specificity, but there are common points of view -- Scope What area of influence does the engineer have? -- Impact (Delivery) What is the engineer’s contribution to the product/project? -- Complexity What is the technical complexity of the task solved by the engineer -- Leadership What leadership qualities the engineer demonstrated and how successfully communicated with other employees -- Improvement What improvements an engineer has made to processes or how he has helped his colleagues and himself grow
As you can see, in such a matrix, much is focused on the significant achievements of the engineer who systematically demonstrates them. And as it moves along grades, it has less stack binding and more and more references to good engineering processes and demonstrations of technical leadership. If we consider the conditional classification, Middle developer can be described as SDE.> backend -> java (middle-level) Staff Engineer should be described as SDE. (staff).
Interestingly, the same Staff engineers have their own archetypes, but they are nailed not to the stack, but rather to the role he performs. (Further details can be read in article)
#Management #Leadership #Staff #Engineering #Software #SoftwareDevelopment