Contents:
- How I ended up in IT
- How I became a boss
- Who is a technical director and how is he different from a tech lead, team lead and CEO
- What changes in life when you become a boss
- How to survive your mistakes
- Every manager is an eternal student
- How to work with a team
- How much to pay professionals
- What definitely should be fired
- How to measure Happiness
- Why I Stopped Being CTO
- About Personal Media
- Where to Get Information

Free Course: "Quick Start in Python"
Learn More
Head of the Message Bus department at Ozon Tech and host of the podcast "Koda Koda" is a professional in the field of technology and communications. His experience in the development and implementation of messaging systems makes him an expert in the field of IT. The podcast "Koda Koda" covers current topics in the world of technology, sharing knowledge and experience with a wide audience. The presenter actively discusses innovations, trends and challenges facing IT professionals, which allows listeners to stay up to date with the latest events.
- How I ended up in IT
- How I became a boss
- Who is a technical director and how is he different from a tech lead, team lead and CEO
- What changes in life when you become a boss
- How to survive your mistakes
- Every manager is an eternal student
- How to work with a team
- How much to pay professionals
- What definitely needs to be fired
- How to measure happiness
- Why I stopped being CTO
- About personal media
- Where to get information
My name is Victor Koreisha, and I currently head the Message Bus department at Ozon. Previously, I held the position of CTO and was one of the co-founders of the Phoenix web studio. In my professional career, I have worked in website development, programming in various languages, as well as in advertising and held management positions at several large IT companies. I am also the author and co-host of the media podcast "Code of Code." My experience and understanding of the industry can be useful to you and your business.
How I ended up in IT
It wasn't my childhood dream. During my school years, I didn't have a computer—one arrived much later than most of my peers. Consequently, I was poorly versed in technology. I couldn't even complete simple computer science assignments, such as working with Excel. Therefore, for a long time, I sincerely believed that this world of technology was not for me. However, over time, I began to master computer skills and realized that with persistence and practice, any obstacle can be overcome.
After graduating from school, I entered the physics department. People passionate about IT technologies began to appear in my circle. They shared fascinating stories with me about Linux, network protocols, and how torrent systems worked. These conversations made a strong impression on me, and within six months, I, along with a classmate, unexpectedly began working in the second line of technical support for an Internet service provider. Combining study and work gave me the opportunity to deepen my knowledge and skills in the field of information technology.
With each new stage of my web development journey, I strove for more. At first, I used ready-made content management systems (CMS), but soon began developing my own solutions, experimenting with various technologies. I realized that this wasn't quite what I was looking for, as I wanted to immerse myself in the world of high-load systems and solve more complex problems. It was important for me to find interesting challenges and expand my programming skills.
Over time, I joined a company that handled much more advanced projects. We worked with online stores that had significant automation, processed a large volume of goods and orders, and had complex logistics and advanced execution logic. Later, we began to actively use testing and version control systems in our work. This allowed me to delve deeper into the profession and gain valuable experience.
Despite my lack of formal education in programming, I found ways to successfully develop in this field. The fundamentals of physics and mathematics I learned at university became a reliable foundation for me. This knowledge helped me understand complex algorithms and programming logic, which allowed me to effectively solve problems and master new technologies.
How I Became a Boss
I can identify two key stages in my career when I managed to exceed my expectations. The first was the transition from developer to team lead. At that point, I wasn't even a senior developer, more like a mid-level developer, at a stretch, or perhaps a very advanced junior-plus. I'd read a lot, but had virtually no practical experience. Nevertheless, I could implement a project, albeit with flaws. And so, I was invited to take on a leadership position. I thought: "Why not?"
I never had to be forced—the desire for this was always within me. The main thing is not the management process, which actually seems boring, but the ability to achieve results that are impossible for one person.
I am capable of independently implementing a project of size X. However, working in a team, I can create not just 10X, but much larger projects. This is possible because the team members have skills and knowledge that are unavailable to me. By managing a team, I am able to deliver projects that I would never have been able to complete alone due to time and knowledge constraints. This demonstrates the power of teamwork and the ability to achieve much more ambitious goals.
As a result, I will manage the project in the same way a programmer works with code in an integrated development environment (IDE). However, instead of code, I use tools such as writing technical specifications, organizing development processes, implementing an engineering culture, design, and many other processes. This will ensure effective project management and the achievement of set goals.
I faced many difficulties and learned many bumps along the way. If events had happened a year later, they could have been more successful and interesting from a technology and management perspective. However, despite all the difficulties, I was presented with an opportunity that I did not miss.
The second time it happened, and by this point I already had more solid technical experience, as well as people management skills. However, managing the project and the tech stack, as well as the hiring process, were a completely new challenge for me. When I was offered the CTO position, I knew I couldn't refuse. I ran into more challenges, but at the time, I had no one above me, and there were no alternatives. I found myself in a situation where I needed to build a tech stack, and I set about it.
I was lucky that the first two or three people I hired turned out to be excellent specialists. Even though I mishandled the hiring process, these wonderful employees made a significant contribution to my development and the project's growth. Their professionalism and support were a crucial factor in my success.
Who is a CTO and how is they different from a tech lead, team lead, and CEO?
A technical director (CTO) is a key figure who combines all the necessary competencies for the successful management of technological processes in a company. They are responsible for strategic planning, innovation, and team optimization. The CTO plays an important role in business development, ensuring effective interaction between various departments and contributing to the achievement of goals.
A team lead is a specialist who combines programming and team management skills. They not only possess a high level of technical competence but also know how to effectively interact with their team members. In addition, the team lead is involved in project management, ensuring that tasks are completed on time and in accordance with established standards. Such a professional plays a key role in the team's success, helping to establish communication and increase overall productivity.
The technical leader is responsible for the selection of technologies for the project. They may be asked questions such as, "Is it worth migrating to PHP 8?" or "Should we use CSS Grid despite its limited browser support?" A tech lead must be able to rationalize their decisions. They may also be asked how to organize a system for effectively managing and scaling microservices. In this case, a tech lead can suggest implementing Kubernetes as a solution. A CTO combines the roles of a tech lead, team lead, and project manager, but differs from them in that they are the final decision-maker. While they may be less technically experienced than a tech lead, less organized than a project manager, and not always perfectly versed in team management or programming, their primary role is to make final decisions and be accountable for them. This makes their role critical to the successful implementation of projects and the achievement of company goals.
The way a task is completed—whether intuitively, by consulting with experts, using training materials, or drawing inspiration from recent conferences—is a personal matter. Ultimately, this is a question that only interests the performer and doesn't cause much concern to others.
What Changes in Your Life When You Become a Boss
I faced feelings of guilt about stopping programming. I watch my colleagues actively work, while I do routine work—answering emails and moving tasks between columns. This makes me doubt my usefulness and productivity.
The story with shame has been going on for a long time. I realize that my job is to organize processes, but it was not easy to accept. I notice that other colleagues are experiencing similar difficulties.
An important aspect, especially at the beginning, is the realization that you are now responsible not only for your own actions but also for others. This change requires adaptation and understanding of new responsibilities, which may include caring for the team, interacting with colleagues, and making decisions that affect others. Getting used to this responsibility can be challenging, but it is an important step towards personal and professional growth.
Of course, I am available to help with editing the text. Please provide the original text you wish to revise.
A new manager may feel that all subordinates should act as copies of each other, completing tasks with the same speed and accuracy. However, this is a misconception. Each employee is unique, with individual skills and approaches to work. Understanding these differences is the key to successfully managing a team. An effective manager must learn to adapt their management style to the strengths and weaknesses of each team member, thereby creating a harmonious and productive work environment.
It is important to understand that specialists of different levels have their own unique skills and approaches to work. It is incorrect to expect the same results from a beginner specialist as from a professional with extensive experience. Everyone has their own strengths: some may write code more slowly, but their developments are high-quality and easy to test, while others, although slower, are able to quickly and accurately understand technical specifications, which minimizes the number of edits and revisions. Each specialist has their own advantages that should be taken into account when evaluating their work.
It is important to develop the ability to notice strengths in people. You need to find the right people and provide them with the opportunity to reach their full potential.
How to survive your mistakes
Admitting your mistakes is always difficult. Not only is this frustrating, but the realization that the situation is often irreversible makes the process even more challenging. However, it's important to understand that admitting mistakes is the first step to fixing them and personal growth.
I once experienced a serious technical failure. I was forced to admit that the system we had built, although scalable at a certain point, was no longer capable of handling the growing workload without significant refactoring. We had been using temporary solutions to address the issues for some time, but soon we were faced with a critical situation. Now we need to decide whether to invest in improving the existing system or abandon it and develop a completely new one.
It's easy to talk about the need for investment, but the question is, where will we get the funds for refactoring? The options are to use the company's own resources or to approach the client, admit our mistakes, and try to negotiate further cooperation.
The CEO and I went to meet with the client with some trepidation. We were concerned that the client might become aggressive or communicate their frustrations to their security guards. In this situation, we had to fully utilize our communication and emotional management skills to successfully navigate potential challenges.
The meeting was not calm or friendly, and not everyone left in a good mood. Nevertheless, we came to a solution: we invested part of the funds ourselves, and the client provided the rest. This required us to pause new development and focus all our efforts on refactoring. Despite the difficulties, the project continues to exist, although it is not achieving the level of success it could have achieved without the problems that arose.
Every manager is an eternal student
One day, I realized that I lacked knowledge and decided to actively seek it. I remember my first paid consultation on people management well. When I handed over the money, I felt as if I'd fallen for a scam and was spending it on something I didn't understand. However, on my way back, I felt incredibly enlightened. In just an hour or so, something I'd been pondering for a long time but couldn't grasp on my own was explained to me. This experience showed me the importance of knowledge and proper guidance in managing people.
I began applying this same approach to technical matters. Whenever I encountered a misunderstanding, I sought out people with the necessary knowledge and spoke with them. More often than not, this was accomplished without much difficulty. This method allows you to effectively solve problems and deepen your knowledge in various fields.
People are happy to answer questions, especially when posed to experts in a particular field. It's enough to ask a specialist you know for help: "Hello! I have a problem. Can you tell me how to solve it?" This approach not only increases your chances of receiving helpful advice but also helps you build stronger relationships with professionals.
In theory, they might respond with, "Only Google provides free consultations." However, more often than not, the response will be, "No problem, tell me your question." If your question is specific and to the point, you'll likely get an answer.
Paying for knowledge and experience is normal practice, and there's nothing wrong with that. On the contrary, I value high-quality work and am willing to pay for it. Sometimes, I've had to persistently ask professionals to accept payment for consultations or mentoring. The worst-case scenario is when someone simply doesn't respond or says they can't help due to a lack of time or interest. But even in such cases, don't despair—you can always find another specialist.
How to Work with a Team
For a long time, I thought that if I assembled a talented team, organized their work, and provided a stable salary, then the business would develop on its own.
Experience shows that allowing processes in a company to develop on their own, without proper control, can lead to negative consequences. Failure to pay attention to your employees, failing to hold regular one-on-one meetings and discussing their professional development can impact the team's motivation and productivity. With each passing month, a lack of attention to employee growth and needs leads to a decrease in their satisfaction and engagement. It is important to actively participate in the HR process to avoid a decline in efficiency and maintain a healthy team atmosphere.
Of course, I am happy to help with text editing. Please provide the text you wish to change.
Over time, everyone inevitably develops professionally. At the same time, prices rise, and inflation affects purchasing power. If you do not raise an employee's salary, they may be embarrassed to ask for one, even if their contribution to the work has increased. In addition, it is important for the employee to understand the company's strategy, project goals, and their place in technical development. This understanding contributes not only to his motivation but also to the overall effectiveness of the team.
In my management practice, I experienced a difficult moment when two key employees decided to leave the company within a week. They stated that they were willing to work for two weeks in accordance with the labor code, but did not intend to continue working there. This episode was one of the most difficult in my career. I valued them as professionals and as friends, because they had been part of the team from the very beginning and represented the foundation of the company.
After a serious experience, I reconsidered my approach to communication and team development. This incident still stands out in my mind. As a responsible person, I could have hired a separate HR manager to interact with employees, organized regular one-on-one meetings, or implemented a semi-annual salary review. However, I ignored these measures, not realizing their importance, and ultimately faced negative consequences. This taught me a lesson about the importance of being actively involved in team management and creating a healthy work environment.
How Much to Pay Professionals
I've seen cases where my subordinates earned more than me. This was especially noticeable during the COVID lockdown: as the CTO and co-owner of the company, I went without a salary for several months, but continued to pay my employees. I was okay with this situation.
It doesn't matter who holds the leadership position. Being the boss doesn't mean I have the most knowledge or that my salary should be the highest. I simply know how to effectively organize a team, and you, Petya and Vasya, are talented back-end developers, front-end developers, and designers. If your professional role is valued higher in the market, this is completely natural and does not raise any doubts. It's important to value every contribution to the team's overall success, regardless of position.
I'm well aware of my colleagues' salaries, while they're usually unaware of mine. This sometimes leads to one of them remarking, "You're the highest paid here—make your own decision." Situations like these highlight the importance of being open about pay and building rapport within the team.
This used to trigger negative emotions in me, but now I don't react to it—I've adapted to the situation.
Why You Should Definitely Fire Someone
Firing employees is one of the most difficult skills for a leader. In retrospect, it becomes clear that the decision to let someone go was long overdue, and you wonder why the decision wasn't made earlier. However, at the moment of decision-making, uncertainty often arises: is this really the time to let someone go? Perhaps the employee's evaluation was biased, and alternative options should be considered. A proper approach to termination requires a thorough analysis and understanding of the situation, which will help avoid mistakes and make the process more humane and effective.
Reasons for termination that are truly unambiguous can be listed fairly quickly. For example, if an employee comes to work intoxicated and behaves aggressively, continuing with the job is unlikely to be advisable. However, even in such situations, there may be exceptions, as sometimes an employee experiences difficult life circumstances that can explain their behavior. It is important to consider the context and approach termination matters with understanding and attention to each individual case.
Managing technical specialists is a complex task. Unlike salespeople, who can be fired for prolonged lack of results or unethical behavior with clients, the situation with developers is different. Determining that a specialist does not meet the requirements can be extremely difficult. There are no clear markers that can unambiguously identify an unsuitable developer. This makes the process of evaluating and making decisions regarding technical employees more complex and requires an in-depth analysis of their performance and teamwork.
In my experience, I have rarely seen employees dismissed solely due to insufficient professionalism. Most dismissals at Phoenix occurred as a result of internal conflicts, when an employee negatively impacted the team or the organization as a whole. I also frequently observed cases where a developer systematically failed to complete assigned tasks.
I wouldn't say the employee is bad. Perhaps the problem lies in our incorrect formulation of tasks or the team atmosphere that they don't like. However, if the situation persists for a long time, a decision must be made. If an employee sabotages the work process, this will ultimately impact the entire team and may lead to the project being halted. For example, a front-end developer expects an API from them, but they can't develop one within a few weeks.
I'm not yet an expert in dismissals, and I need to learn more. One of the key differences between Russian and European companies is their attitude toward mistakes, which can be called a "error culture." European companies are more likely to view mistakes as opportunities for learning and growth, which fosters a more open and productive work environment. It's important to understand that this approach can significantly improve work processes and increase overall team effectiveness. Our culture often punishes employees for mistakes. This can manifest itself not only in dismissal or salary deductions, but also in constant reminders of past mistakes. Every morning at our standup, someone inevitably mentions how Petya made a mistake that impacted the production team. This negative attitude hinders development and creates a toxic atmosphere within the team. I am convinced that this culture will soon become a thing of the past. In Western companies, mistakes are viewed as opportunities for learning and growth, which fosters a more open and constructive approach to work.
How to Measure Happiness
The concepts of "employee happiness" and "team happiness" became significant for me about a year ago. I realized that this is one of the key metrics of success in management. Nothing demonstrates a leader's effectiveness better than the level of satisfaction of their employees. Happy employees are not only more productive but also create a positive atmosphere within the team, which ultimately contributes to the achievement of the company's overall goals. It is important to understand that caring for employee well-being is not just a fashion trend, but a necessity for successful management.
Measuring overall team performance is a complex task. One possible assessment method is the use of story points, but it is important to keep in mind that their meaning varies depending on the context and the team. This makes performance comparisons between different teams difficult. For a more accurate assessment, it's necessary to use a comprehensive approach that considers the specifics of the team's work, the type of tasks performed, and other aspects that influence performance.
You can estimate how much your team earns, but this metric is quite relative. One team may create numerous excellent products and earn little because their offerings aren't in high demand. Meanwhile, another team may accidentally develop something insignificant and earn billions thanks to unexpected interest from large tech companies. This isn't an objective measure of success. A far more meaningful indicator is the satisfaction and happiness of the team.
Team member happiness depends on many factors. At first glance, it might seem that salary is the most important one, but this assertion doesn't stand up to scientific scrutiny. If you survey a hundred random IT professionals about their happiness levels and compare this data with their income, you'll find no clear correlation between salary and satisfaction. This suggests that happiness in a professional environment is shaped not only by material aspects but also by other important factors, such as the team atmosphere, opportunities for growth and development, and work-life balance.
A person can live in any region, working as a tester for 30,000 rubles, and still be perfectly happy. At the same time, living in Moscow City and earning huge sums, they can experience profound unhappiness. Happiness is not determined by income level, but depends on the inner state and harmony with oneself.
Measuring team happiness is an important aspect of management. I often ask my employees two key questions. The first question is: "On a scale of 1 to 10, how prepared are you to continue working in your position at our company? 10 means 'I'm ready to work here forever,' and 1 means 'I've already written my resignation letter and am ready to show it.'" This approach helps me identify employee satisfaction levels and understand how to improve the work environment and increase motivation within the team.
The second question is: "Do you want to go to work?" If someone immediately answers "yes," I give it a conditional score of 5. The answer "no" gets 1 point.
Numbers alone may not be informative. For example, if I say: "My team's happiness is 8," it won't give a clear understanding. However, by analyzing the happiness level of a specific employee throughout the year, I can notice changes: in the first quarter - 5 points, in the second - 6, in the third - 8. This allows me to conclude that the trend is positive. We were able to create a more comfortable working environment for this employee. Therefore, regularly monitoring employee happiness helps us understand how we can improve the work environment and increase team satisfaction.
Why I Left Being CTO
Being a CTO doesn't mean you've reached the pinnacle of success. In my case, I was the chief technical officer at a small company that was struggling to achieve rapid growth. I would have been surprised to wake up one day and see our company at the level of giants like Google or VKontakte. I always strived for more and looked for opportunities to develop.
Leaving a team is always a difficult and lengthy process. A sudden decision can seriously damage the team, while delaying the departure can lead to the move never being completed. I came to the conclusion that the best option was to remain as a player-coach and external consultant. This allows me to stay connected with the team while still maintaining opportunities for personal growth and development.
The experience I've gained from becoming "the smartest person in the room" gives me the confidence to take on responsibility. My ability to draw on outside expertise allows me to effectively use this resource in other professional roles.
At first, I felt intimidated by my new position, but now I'm proud of what I do and my experience. This has marked a new stage in my career: on the one hand, I no longer hold a leadership position and don't have all the knowledge. On the other hand, the projects we work on contribute to my development in both technical and managerial aspects. Overall, I continue to play the same game, but at a new level.
About personal media
My path in this direction has been long and difficult. At some point, I decided to create a blog on the Egeya platform, developed by Ilya Birman and his team of like-minded people. I started publishing my thoughts, but only about ten people read them, and I personally sent them the link. Now, when I reread my articles from five years ago, I realize that I would like to delete some of them, and I already have.
I tried writing on social media, but it didn't bring me any success. I have an article on Habr, and unfortunately, this attempt led to my karma being at a low level. I also decided to try my hand at open source, hoping that creating a project would attract attention to my name and make me famous. However, as experience shows, this didn't happen.
When I decided to start a podcast, I didn't like the concept of inviting only one guest per episode. I was striving for a more objective discussion of various topics. This required at least two speakers, preferably from different corners of the world, and even better if their opinions were opposing. So, I recorded the first season following this logic.
When I moved on to the second season, I realized that I wanted to not only present the opinions of my speakers, but also actively express my own point of view. It was important for me not just to be the host, but to have the opportunity to lead discussions, receive feedback, and engage in dialogue with the opponent. I analyzed the guests of the first season and chose those with whom I felt easy and comfortable communicating, from whom I truly benefited. Eventually, Zhenya Antonov responded, and we began hosting the program together.
Where to get information
I recommend the channel "Teamlead Obviousness," hosted by my co-host Zhenya Antonov. His materials provide valuable advice and insights, especially useful for aspiring team leaders. The channel's content covers key aspects of team management and leadership development, making it an indispensable resource for those striving to successfully lead their teams.
I recommend checking out the Telegram channel "Notes from a Burning House," hosted by Anastasia Abrashitova, a top manager at Yandex. This channel offers unique and valuable content that, in my opinion, is underrated. Subscribing to it is a great solution for anyone interested in insights from the world of business and technology.
I actively listen to podcasts, and my favorites include "Launching Tomorrow" and "I'll Finish It Later." I'm especially drawn to "Submarine," as it covers a variety of topics, such as conferences, educational programs, and interesting events. Podcasts are a great source of information and inspiration for personal and professional growth.
If you're looking to master a specific technology, the best way to do so is to actively work with it. If you can't implement a project at your main job, create your own pet project. If you can't start a pet project right away, head to the Codewars platform, choose the language you want to learn, and solve simple algorithmic problems. This will help you gain practical skills and strengthen your knowledge.
In the programming world, there are countless opportunities to use languages, frameworks, and libraries. In fact, there are literally billions of them. Whether you choose a programming language or a specific tool, the key is to simply start experimenting. Practice is the only path to success and technology mastery. Try new approaches, create projects and develop your skills, because without practical experience it is impossible to achieve true mastery.
Read also:
- Who is a CTO in a startup, how is he different from a team lead and what skills are needed
- The problem about the director and the programmer shift schedule
- Popular questions and tasks at a tester interview

