A
A
Alex Murfy2019-09-12 16:38:42
Project management
Alex Murfy, 2019-09-12 16:38:42

Job title?

Good day.
We have the following situation: There is a company that has a product that was developed and finalized by different development teams. There is no product documentation. There is a lot of legacy code. Different modules with different code style. New features were uploaded immediately for sale, i.e. to master. New hires are doing exactly the same. In general, there are a lot of things that are not done right at the moment. Actually the question is, what is the name of the vacancy of a person who monitors all these moments and eliminates them? Googled, system analyst/architect is not suitable, sort of. Please advise how to properly call this person and what requirements should be presented to him. Thank you.

Answer the question

In order to leave comments, you need to log in

4 answer(s)
A
ApeCoder, 2019-09-13
@qxcoder

Looks like a tech lead https://techrocks.ru/2018/03/24/8-engineering-lead...

J
Jacob E, 2019-09-12
@Zifix

This will be done by any intelligent programmer who will be given authority. In a sense, he will write down all the processes point by point, but how much the team will follow them depends on both the lead and the RM.

H
hack504, 2019-09-12
@hack504

- finalized by different development teams
- There is no documentation on the product
- New features were uploaded immediately to the prod
- New employees now do exactly the same
as the name of the vacancy of a person who monitors all these moments and eliminates them?
Dqhm4kTX0AAQCSf.jpg

V
Vasily Mazhekin, 2019-10-03
@mazhekin

This is a devops engineer, not a tech lead tech
lead-team lead is a muddy role and a strange name for a specialist, when it is impossible to formulate a circle of occupations and remember a profession, they choose "any smart programmer", "express their admiration for him", give the honorary title of team leader-tech lead-schmimlid , loaded with an incomprehensible range of duties and powers (from hr to setting business tasks, and this happens), they give him a quiet gag so that he paints all the processes as he sees them))). And the development turns into a sect led by this shaman.
For example, when a person names his specialization, it is immediately clear what a person is doing on a project, whether it is a devops engineer, or a ux designer, or a scrum master, tester, backend developer, frontend developer. There are no questions, it is clear what people do and what they are responsible for. The tech lead or team lead, usually vaguely and incomprehensibly explains his position on the project and owns a little bit of everything, but nothing deeply and professionally.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question