Position: CTO, TPM, System Architect, Engineering manager
Category: Lead
English level: upper
Years of experience: 11

- Launch OKR approach in the whole company. It helps to avoid micromanagement and raises independence, as well as promoting responsibility and initiative in employees.
- Move the project from servers to cloud. Moving the project, we tried to resolve the bottleneck with the DevOps team and remove hard dependency on DevOps. As a result, almost any Developer using the GitOps approach can fix any problem on Stage or Prod env.
- 100% automation. A developer has just written a code. All other actions were automated, such as: releases, tests, git branching strategy, create releases in jira, and so on …
- The last 10 sprints did not fail :)
I am a proficient, self-motivated Software Engineer, and Manager. I like to solve difficult tasks and achieve goals, which helps to motivate all my colleagues to move forward. And, my experience helps me with this. I have over 15 years of experience in IT, 10 years of which have been spent writing code. The last 6 years, I have been concentrating on management. During this time, I have worn many hats in projects, such as: CTO, Delivery manager, Software Architect, Technical Product Manager, Scrum Master, Project Manager, Team Lead, Developer, as well as Designer.

In my current position, I have had a lot of problems and have gained a huge amount of  experience in solving them. As a result, I can help you to solve many types of problems, such as:
- Team efficiency. Building and developing a team is always challenging, it is really hard to motivate each person in a team. But, if you organize a good atmosphere inside the team, set the right goals, and give everyone opportunities to grow, you can achieve efficient command. In order to accomplish these goals, I am helping people to implement self-developing plans, having one-to-one meetings, solving conflicts, and so on.
- Tune and set up processes. Creating and leading roadmaps, in addition to following best practices of agile methodology. Find bottlenecks in processes, facilitate knowledge sharing etc.
- Stable product performance/Quality of product. When you are afraid to deploy a new release because you don’t know which result you will get, if it will work on production, or how many issues you will have.
- Decrease lead time (End-to-end time to market). As a result, you will decrease the cost of any feature you release, and speed up business reaction to new environments or users requirements.
- Create efficient and cost effective infrastructure. With active monitoring, we can predict problems and know about issues before the end user is even aware of them. Using the GitOps approach allows us to avoid the bus factor, and provide inheritance of both knowledge and infrastructure.
- Fast deployment and stability. Nowadays, I can’t imagine a project without automation, autotests, or CI/CD. All these approaches help to release products more often, as needed, and with good quality.

This is not the full list of challenges I ran across, so if you are interested, you can find more information about me on my linkedin page.