"If temporary employees come to projects,
Posted: Mon Jan 20, 2025 3:11 am
Ksenia Zamukhovskaya, HR Director at PPG Development LLC, noted that "nomadic" employment is not a new trend in the domestic market, but this scenario has proven ineffective in the area of systems programming, where product development can take several years.
in three to six months albania whatsapp number databa se they will create not a finished product, but only a part of it - this will become a big problem," she said.
The situation is similar with freelancing in the IT market. According to Alexey Kirpichnikov, head of the development department of JSC "PF "SKB Kontur", when playing the long game (that is, during long-term software development), the developer's commitment to the product and the desire to build it qualitatively, with an "eye" on future development, are important.
"The value of a freelancer who comes to solve a specific task, completes the task and leaves may be at odds with the product approach. However, we have a certain number of tasks that can be outsourced. Usually in such a situation, we prefer to contact a company that provides the relevant services, but not hire temporary developers on staff," said Alexey Kirpichnikov.
According to the development manager of UserGate LLC, Alexander Lugansky, employee leasing remains relevant for IT, since implementing a project by an external specialist or working group can be cheaper and easier than hiring them on staff. But in the field of information security, such a practice is possible only in auxiliary projects not related to the development of information security solutions.
"All the projects that we implement for the market are a long-term game. That is why we use only our own teams. They are well-coordinated and have played for many years of development. The process of incorporating new participants into them occurs gradually and takes a long time. If we consider the issue in general, then any technological project must be supported. There is no ideal code. Over time, errors are discovered that need to be fixed, new versions of operating systems for which it needs to be adapted, etc. Ideally, this should be done by the same team that was involved in the development. In real life, very often completely different people and entire teams are involved in technical support. The situation can be alleviated by competent acceptance of both the project itself and its documentation," concluded Alexander Lugansky.
in three to six months albania whatsapp number databa se they will create not a finished product, but only a part of it - this will become a big problem," she said.
The situation is similar with freelancing in the IT market. According to Alexey Kirpichnikov, head of the development department of JSC "PF "SKB Kontur", when playing the long game (that is, during long-term software development), the developer's commitment to the product and the desire to build it qualitatively, with an "eye" on future development, are important.
"The value of a freelancer who comes to solve a specific task, completes the task and leaves may be at odds with the product approach. However, we have a certain number of tasks that can be outsourced. Usually in such a situation, we prefer to contact a company that provides the relevant services, but not hire temporary developers on staff," said Alexey Kirpichnikov.
According to the development manager of UserGate LLC, Alexander Lugansky, employee leasing remains relevant for IT, since implementing a project by an external specialist or working group can be cheaper and easier than hiring them on staff. But in the field of information security, such a practice is possible only in auxiliary projects not related to the development of information security solutions.
"All the projects that we implement for the market are a long-term game. That is why we use only our own teams. They are well-coordinated and have played for many years of development. The process of incorporating new participants into them occurs gradually and takes a long time. If we consider the issue in general, then any technological project must be supported. There is no ideal code. Over time, errors are discovered that need to be fixed, new versions of operating systems for which it needs to be adapted, etc. Ideally, this should be done by the same team that was involved in the development. In real life, very often completely different people and entire teams are involved in technical support. The situation can be alleviated by competent acceptance of both the project itself and its documentation," concluded Alexander Lugansky.