Code

How to go from student to IT manager and company co-owner

How to go from student to IT manager and company co-owner

Dive into the World of Python: A Free Mini-Course for All Skill Levels Four impressive projects for your portfolio and the opportunity to communicate live with the speaker Find out what knowledge and skills you can acquire in our course

Learn More

Head of Message Bus at Ozon Tech and host of the "Koda Koda" podcast.

  • How I ended up in IT
  • How I became a boss
  • The CTO is a key figure in the company, responsible for technology strategy and product development. Their main task is to ensure the effective use of technology to achieve business goals. He manages technical teams and makes decisions regarding the architecture and implementation of new technologies.

    Unlike the CTO, a tech lead (technical leader) typically focuses on managing a specific development team and is directly responsible for the technical aspects of project implementation. A tech lead is often involved in coordinating the group's work, helping solve complex problems, and ensuring quality standards are met.

    A team lead (team leader) typically performs a broader set of functions, including managing people and processes. The team lead is responsible not only for technical results but also for motivating the team, distributing tasks, and interacting with other departments.

    The CEO (chief executive officer) stands at the top of the company's hierarchy. He or she shapes the overall business strategy, makes key decisions, and is responsible for financial results. Unlike the CTO, the CEO does not delve into technical details but focuses on the strategic management of the entire organization.

    Thus, although all of these roles involve management and coordination, each has unique responsibilities and focuses on different aspects of the company's operations.

  • When a person takes on a management position, their life undergoes significant changes. Firstly, a new level of responsibility appears, as it is necessary not only to make decisions but also to take full responsibility for them. This includes project management, monitoring task completion, and caring for the team.

    Secondly, your social status changes. Now you find yourself at a higher level, and your interactions with colleagues and subordinates are transformed. This can lead to changes in relationships, sometimes even distance from former friends and colleagues, since the boss and subordinates are often perceived as different groups.

    It is also worth noting that the work schedule may become more stressful. Often, managers are faced with the need to resolve urgent issues even outside of working hours, which can affect their personal life and leisure.

    Furthermore, increased demands on personal effectiveness and leadership skills can also be a source of stress. It is important for a leader to be able to inspire and motivate a team, which requires special communication skills and emotional intelligence.

    In general, the transition to a leadership position entails not only new opportunities, but also many challenges and changes that require adaptation and rethinking the usual way of life.

  • How to cope with life's mistakes
  • Every leader, in a sense, remains a student throughout their career.
  • Effective interaction with a team requires a careful approach and understanding of many factors. For starters, it is important to set clear goals and expectations so that each member knows what to strive for. Regular meetings help maintain open communication, allowing you to discuss current tasks and identify potential problems.

    Equally important is creating an atmosphere of trust and respect, where each team member feels valued and is willing to share ideas. Support and recognition of achievements also play a key role in building a cohesive team.

    Pay attention to a diversity of skills and opinions, as this can enrich the decision-making process. Flexibility and the ability to adapt to change will help the team successfully cope with emerging challenges.

    Finally, it is important to regularly analyze performance to identify strengths and areas for improvement. This approach will not only help achieve goals but also develop the team as a whole.

  • What is the cost of specialist services?
  • There are certain situations and behaviors that clearly require an employee's dismissal. These include serious violations of corporate ethics, such as theft, deception, or fraud. It is also worth paying attention to cases of gross violations of labor discipline, such as systematic lateness or absenteeism.

    Furthermore, if an employee displays aggressive behavior towards colleagues or clients, this may be a compelling reason for parting with them. Situations where an employee intentionally sabotages the team's work or creates a toxic atmosphere within the team cannot be ignored.

    It is important to note that actions such as alcohol or drug use in the workplace can also be grounds for dismissal. Each of these factors undermines trust and safety in the work process, making further collaboration impossible.

  • How to measure happiness
  • The reasons why I left my position as CTO were multifaceted. First, I felt that the time had come for new ideas and approaches at the company, and I believed that a fresh perspective could be more beneficial. Secondly, personal circumstances also played a role - I needed more time for my family and self-realization outside of work. As a result, I came to the decision that it would be better to transfer my responsibilities to someone who could continue the development of the company with renewed energy and perspective.
  • About personal media
  • Information sources can be varied, and their choice depends on the purpose and topic of the research. Firstly, books and scientific publications remain reliable sources, providing a deep understanding of the subject. Secondly, the internet offers a wide range of resources, from specialized websites and online libraries to databases and academic journals.

    Don't forget about scientific conferences and seminars, where you can obtain up-to-date data and exchange opinions with experts. Interviews with professionals in the field of interest can also be useful. Finally, experience and observations can be a valuable source of information, especially in practical research.

Hello, my name is Viktor Koreisha. I currently head the Message Bus department at Ozon. Previously, I held the position of CTO and was one of two co-founders of the Phoenix web studio. My experience includes website development, programming in various languages, as well as work in advertising and technical management at several large IT companies. I am also the author and co-host of the "Code of Code" podcast. I hope my experience and views on the industry will be of interest to you.

How I ended up in IT

It's hardly a childhood dream. I didn't have my own computer at school—I got one much later than many of my classmates. Because of this, I didn't have time to master it as I should have. I couldn't even complete the most basic assignments in computer science classes, like working with Excel. So for a long time, I truly believed that this world of technology wasn't for me.

After graduating from school, I entered the Moscow Institute of Physics and Technology, and people passionate about information technology began to appear in my circle. They shared fascinating stories with me about Linux, network protocols, and how torrent systems work. These stories inspired me so much that just six months later, without even realizing it, I found myself on the second-line technical support team of one of the Internet service providers, working there together with a classmate.

With each step, I delved deeper into the world of web development. At first, I used ready-made content management systems, but soon moved on to independent development, experimenting with a variety of technologies. At that time, I already realized that this was far from true programming; I was drawn to the high workload, exciting projects, and new challenges.

After some time, I began working for an organization that handled projects of a completely different scale. We focused on online stores, implementing significant automation, processing large volumes of goods and orders, and developing complex logistics and fulfillment mechanisms. Soon, we began using testing and version control systems in our work—and that was how I fully immersed myself in my profession.

Nevertheless, I was unable to gain in-depth knowledge of programming. However, this didn't become a serious obstacle for me, as the basic knowledge I acquired at university in physics and mathematics turned out to be quite useful.

How I Became a Boss

I can point out two key moments when I took on more than I was capable of. The first is related to how I moved from the role of developer to team lead, although at that point I wasn't even a senior. At best, I could say I was at the middle level, but more likely, I was a very advanced junior with a plus: I was familiar with the theory, but I had little practical experience, and although I could implement any project, it was rather at a "crooked and sloppy" level. And then I was offered to take on management. I thought: "Why not?"

I didn't have to force myself at all - this desire arose naturally. I didn't so much want to manage, which is inherently boring, but rather to achieve results that are impossible to achieve alone.

Let's say I'm capable of developing a project of X volume. However, by working in a team, I can achieve not just 10X, but significantly greater results, because each participant has unique skills that are unavailable to me. This is truly impressive - thanks to the team's efforts, I can implement projects that I could never have accomplished alone, both in terms of time and the necessary knowledge.

Ultimately, I will take over the management of this project the way a programmer manages code in a development environment. However, instead of code, my tools will be the creation of technical specifications, organizational development processes, the culture of the engineering community, design, and many other aspects.

The number of mistakes I have encountered and the bumps I have learned are impossible to count. Of course, if events had unfolded a year later, the outcome would have been significantly more successful and exciting, both in terms of technology and management. However, on the other hand, I was presented with a unique opportunity that I didn't ignore.

Then it happened again. By then, I already had more serious technical experience, and I had learned how to manage people. However, project management, technology selection, and recruitment remained completely unfamiliar tasks for me. And then, the opportunity to become a CTO presented itself—and again, I decided I couldn't refuse. As a result, I made quite a few mistakes! But nevertheless, there was no one at a higher level than me, and my options were limited. So, I had to build a tech stack, and I took it on.

I was incredibly lucky: the first two or three people I hired, even though I did things completely wrong in the process, turned out to be amazing people who had a significant impact on my development.

The Role of a CTO: Differences from a Tech Lead, Team Lead, and CEO

A CTO is a specialist who, in essence, combines all the skills and knowledge mentioned in the subtitle.

So, who is a team lead? This is a specialist who demonstrates high effectiveness in both programming and team management, and also has some project management skills.

A technical leader is responsible for making decisions regarding technology selection. He or she may be asked: "Isn't it time to upgrade to PHP 8?" or "Is it really worth implementing Grid in CSS, despite its limited support?" In such cases, the tech lead can justify their position. Or, for example, they might be asked, "How can we organize the system so that microservices can quickly deploy and scale?" They might reflect and decide, "Let's use Kubernetes."

The CTO combines the roles of tech lead, team lead, and project manager. However, they differ from these positions in that they are the final authority. They may be less technically competent than the tech lead and not as organized as the project manager. They also may not be an expert in people management or programming. But the main thing is that he makes the final decisions and is responsible for them.

The way he plans to do this—whether through intuition, advice from colleagues, using curriculum, or insights gained at a recent conference—is his personal concern, and, essentially, it shouldn't concern anyone else.

Life Transformations as You Become a Manager

The first thing that overwhelmed me was a feeling of guilt about no longer writing code myself: “Look, my colleagues are working hard, and I’m wasting my time, answering emails or simply moving tasks from one column to another.”

The situation with shame dragged on for quite a long time. In my head, I realized that this was part of my professional activity—to establish a workflow. However, accepting this was not easy. I notice that other colleagues are also experiencing similar difficulties.

The second aspect, which is especially important at the beginning, is to recognize your responsibility not only for your own actions, but also for the actions of others.

A new manager often feels that their employees should act as a mirror image of them: complete tasks at the same speed, analyze information with the same accuracy, and so on. However, this is a misconception - each person is unique.

First of all, it should be noted that specialist levels vary: it makes no sense to expect the same results from a junior developer as from a mid-level or senior one. In addition, each person has unique strengths. For example, someone may write code more slowly, but their developments are more successfully tested or already include the possibility of further expansion. Or, despite the slow writing pace, they grasp the essence of the technical specifications so clearly that they avoid the need for revisions. Everyone has their own strengths.

It is necessary to develop the ability to notice strengths in others. It's important to find the right people and give them the opportunity to reach their full potential.

Ways to Cope with the Consequences of Your Own Mistakes

Admitting their existence certainly doesn't evoke pleasant emotions. It's not just the fact itself, but also the fact that it often becomes impossible to change the current situation.

There was an episode in my life related to a purely technical problem when I had to make a statement: "The system we developed could handle the increased load until now, but this is no longer possible without significant changes to the architecture. We've been making do with temporary solutions for some time, but now we've reached a critical point. Therefore, we will either have to invest in improvements, or abandon this system and build a new one from scratch."

It's easy to declare the intention to invest, but the question arises: where will we get the funds for refactoring? We had to either extract the money from our business or approach the client, admit our mistakes, and try to negotiate.

We set out with the CEO, feeling a little nervous: what if the client suddenly gets up and hits us? Or perhaps delegates this task to one of his security guards? In such a situation, we had to activate all our communication and interaction skills.

Of course, it's not fair to say that "the meeting was comfortable and friendly," and everyone left in high spirits. Nevertheless, we did reach a certain agreement: we contributed part of the funds, and the client provided the rest. We had to pause new development and focus all our efforts on refactoring. However, it should be noted that the project continues to exist, although it is not developing as actively as it could have if not for this unpleasant incident.

Managers: Constant Learners in the Business World

One day I realized that I desperately needed knowledge, and from then on I began actively seeking it. I remember my first paid consultation on people management well. When I went to the specialist, I had the feeling that I had fallen for some kind of scam and was giving money to who knows who. However, returning, I felt incredibly inspired! In just an hour and a half, they explained to me what I had been pondering for months, but could not understand on my own.

Then I started applying a similar approach to technical issues. If something remained unclear, I simply found someone who knew the subject and asked them questions. More often than not, this was done without much difficulty.

Communicating with people about solving various problems is usually not difficult. All you need to do is turn to a friend who has established themselves as an expert in the area you are interested in and simply ask: “Hi! I have a problem. Can you tell me how to solve it?”

Sure, they may respond with something like: “Only Google provides free consultations.” However, more often than not, the reaction will be something else: “No problem. What did you want to ask?” If your question is clear and practical, you will most likely get an answer.

Besides, there is nothing wrong with paying for knowledge and professional experience. On the contrary, I like to reward quality work. Sometimes I even had to persuade people to accept payment for their consultations or mentoring services. The worst case scenario is when someone simply doesn't respond. They either say they don't have time or aren't interested. But that's okay—you can always find someone else.

Effective Teamwork Strategies

For a while, I was convinced that by gathering talented people, establishing collaboration, and providing them with a decent salary, the process would develop on its own.

Based on experience, if things are left unchecked, the outcome is likely to be negative. If you don't pay attention to your subordinates, don't hold one-on-one meetings, and don't discuss their career prospects, they will become increasingly dissatisfied over time.

First of all, over time, a person continues their professional development, one way or another. At the same time, prices are rising—inflation still has an impact. Meanwhile, you don't increase their salary, and they, being modest, don't dare raise the issue. Secondly, they are completely unclear about what's going on around them: they don't understand the company's strategy, the project's goals, or the direction of its technical development.

During one of the challenging moments in my management career, something unexpected happened: within the same week, two key employees decided to leave the company. They came and said, "We are ready to fulfill our obligations and work for two weeks, as stipulated by the Labor Code. However, this concludes our work at your company." This incident was a real test for me, as I relied on them not only as highly qualified specialists, but also as close friends. These people were with us from the very beginning and formed the core of our team.

Since then, I have radically changed my perception of how to interact with and develop a team. This blunder still sticks in my mind. As a decision-maker, I had the opportunity to engage a separate HR specialist to communicate with employees. I could also conduct one-on-one meetings or establish a semi-annual salary review cycle. However, I took none of these steps. I simply ignored their importance and, as a result, faced the consequences.

Compensation for specialists

There have been situations, and more than once, when my subordinate's income exceeded my own. Let's not forget the COVID-19 lockdown period: at the time, as not only the CTO but also one of the company's owners, I went without a salary for several months, although I continued to pay my employees. How did I perceive this situation? With complete calm.

In reality, it doesn't matter at all who holds a leadership position. Being the boss doesn't mean I have the most knowledge or, even more so, that my salary should be the highest. I simply know how to effectively lead a team, and you, Petya and Vasya, are excellent specialists in your fields—be it backend, frontend, design, or something else. If your work has a higher market value, that seems completely natural and normal to me.

However, I know their salary, while my colleagues are often unaware of my income. For this reason, from time to time one of them may say: "You earn more than anyone else here - so think about it."

Previously, this caused me dissatisfaction. Now I don't pay attention to it - I've adapted))).

Reasons why dismissal becomes inevitable

The process of dismissing employees is one of the most difficult skills. When you analyze the situation after some time, it becomes obvious: "Why didn't I do this sooner? It's time to part ways." However, at the moment of making a decision, doubts always arise: "Is this really the case? Perhaps I'm wrong and not seeing the whole picture?"

The reasons for dismissal can be counted on one hand. Obviously, if an employee comes to work intoxicated and begins to behave inappropriately, then continuing to work with him is unlikely to be appropriate. However, even in such a situation, there may be nuances: perhaps he is experiencing serious personal problems or a tragedy.

Working with technical specialists is a particularly challenging task. While I have no experience managing salespeople, I can assume that they can be fired for a prolonged lack of sales, for example, if their performance remains zero for several months. Or, for example, if a salesperson deceived a client with something completely absurd. However, in the case of developers, identifying clear criteria indicating that a given specialist is not a good fit is virtually impossible.

I can hardly recall a case where I fired an employee solely because they did not meet our requirements. In most cases, dismissals at Phoenix occurred due to internal conflicts, when an employee had a negative impact on the team or the organization as a whole. Or I observed a developer repeatedly failing to meet assigned tasks.

I'm not saying he's a bad specialist. Perhaps we're formulating their tasks incorrectly, or they're uncomfortable within our team. However, if the situation persists for a long time, we'll have to make a decision. When an employee starts sabotaging the workflow, it will sooner or later impact the entire team and can lead to the shutdown of an entire project. For example, a front-end developer expects an API from them, but they're unable to develop it for several weeks.

While I'm still far from an expert on firings, I still have a long way to go. In general, a significant difference between Russian and European companies is their attitude toward mistakes.

In our culture, there's a strong habit of punishing people for mistakes. This doesn't always mean immediate dismissal or a significant pay cut, but it usually becomes an excuse to remind them of the mistake in any situation. Every day at 10 a.m. at standups, someone is sure to mention how Petya botched production. This is an extremely negative aspect. I am convinced that such an atmosphere will soon disappear from our environment. In Western companies, a mistake is perceived as an opportunity for growth and learning, and not a reason for condemnation.

How to measure happiness

I began to realize the importance of such concepts as "employee happiness" and "team happiness" relatively recently - about a year ago. During this period, I came to the conclusion that this is one of the key metrics: what can better demonstrate your leadership qualities than the level of satisfaction of your subordinates?

Overall team effectiveness can indeed be assessed, but it is quite a difficult task. What exactly should be measured in - story points? The problem is that they can vary depending on the context.

You can determine how much money your team makes, but this is only a relative value. One group can create many high-quality products and still receive relatively little profit, because their offerings are not in great demand. At the same time, another team might accidentally develop something insignificant and suddenly make a billion if a major tech company decides to acquire it. Thus, financial metrics aren't always an objective criterion. A far more intriguing question is the happiness of team members.

Certainly, many factors influence happiness. At first glance, it might seem that the income level of each individual team member plays a key role in their satisfaction. However, this opinion is likely held by someone who has never delved into this research. If you surveyed one hundred randomly selected IT professionals about their happiness and then plotted their incomes, you'd find that the data would be completely inconsistent.

A person can be in a small town, earn 30,000 rubles as a tester, and feel completely satisfied. Meanwhile, another can work in Moscow City, earning huge sums, and remain deeply unhappy.

How can you really measure the level of happiness in a team? I usually ask my employees just two questions. The first is: "Please rate on a scale of 1 to 10 how prepared you are to continue working in your position at this company. 10 means 'I would like to stay here for my entire career,' and 1 means 'I have already prepared my resignation letter and am ready to submit it.'"

The second question is: "Do you wish to go to work?" If a person answers "yes" without hesitation, I give it a score of 5. If the answer is "no," it's 1 point.

Of course, these metrics are meaningless without context. For example, if I say, "My team's happiness level is 8," it won't give anyone a sense of the situation. However, if I track a specific employee's satisfaction level throughout the year and notice that in the first quarter they had a 5, then a 6, and then an 8, that will be evidence of our progress. We were able to create a more comfortable environment for this person.

Reasons for leaving my CTO post

As a CTO, you can't yet assume that you've achieved all of your goals. For example, in my case, I was a leading specialist in a small company that wasn't expecting significant growth. It would be amazing to wake up one day and find that we're on par with giants like Google or VKontakte. I had a desire for more.

Although the process of leaving turned out to be long and difficult. On the one hand, an abrupt end could harm the team. On the other hand, if you drag it out, you could stay forever. I came to the conclusion that the optimal solution would be to stay as a player-coach, acting as an external consultant.

The skill of being "the smartest in the room" contributes to the confidence that I can take on responsibility. Moreover, the ability to seek outside expertise allows me to use this approach in other areas.

For a certain period, I felt uneasy about my new role. However, now I feel proud of both my current activities and the experience I have accumulated. It's like a new turn of the spiral: on the one hand, I no longer occupy a leadership position and don't consider myself the smartest. On the other hand, the projects we are working on provide me with the opportunity to develop both technically and managerially. Ultimately, I'm still playing the same game, but at a higher level. 🙂

About personal media

My path in this area was not easy and lengthy. At a certain point, I decided to create a blog on the excellent Egeya platform, developed by Ilya Birman and his team of passionate people. I began publishing my thoughts, but the audience was only about 10 people, to whom I myself sent links to my posts. Now, when I look back at my articles written five years ago, I want to get rid of some of them, and I have already deleted several.

I tried sharing my thoughts on social networks, but this experience did not bring me significant results. I have a publication on Habr, but, unfortunately, it resulted in my karma being at a low level. I also decided to try my hand at Open Source, hoping that if I created something original, my name would become known and I would gain popularity. But, as you may have guessed, this didn't happen.

When I decided to start a podcast, I wasn't entirely happy with the concept of only one guest per episode. I wanted us to be able to examine any topic from different angles. So, I needed at least two participants, preferably representing different points of view, and even better, with opposing opinions. It was with this idea in mind that I recorded the first season.

When I started working on the second season, I realized that I wanted to share not only the opinions of my speakers, but also express my own thoughts. And not just by taking the position of host – I wanted people to discuss with me, express alternative views, and help me stay within reason. Basically, I needed an opponent for discussions. I paid attention to the participants of the first season and chose those with whom I had developed a trusting and comfortable dialogue, from whom I could truly benefit - there were several of them. In the end, Zhenya Antonov responded, and we began hosting the program together.

Sources of information: where to get knowledge?

I recommend paying attention to the channel "Teamlead Obviousness", hosted by my colleague Zhenya Antonov. I am confident that his materials will be extremely useful, especially for those just starting their career as a team lead.

I recommend paying attention to the channel "Notes from a Burning House", hosted by Anastasia Abrashitova, who holds a high position at Yandex. In my opinion, this is a truly wonderful and significantly underrated source of information.

I am also a fan of podcasts. I especially like "Launch Tomorrow" and "I'll Finish It Later". However, "Submarine" occupies a special place, as it presents a variety of topics: conferences, educational events, and various activities.

If your goal is to master a certain technology, there is no more effective way than actively working with it. If you can't do this as part of your main job, try creating your own project. If you can't start right away, go to the Codewars platform, choose a programming language that interests you, and work on solving simple algorithmic problems.

There are an infinite number of ways to use a programming language - these can be not only the languages ​​themselves, but also various frameworks, libraries, and much more. The main thing is not to be afraid to experiment and try new approaches, as there is no other way to master it.

Read also:

  • The CTO, or chief technology officer, plays a key role in a startup, responsible for the strategic direction of the company's technical development. Unlike a team lead, who manages a specific development team and focuses on current tasks, a CTO is involved in broader issues such as technology selection, system architecture, and long-term technical strategies.

    To effectively fulfill their responsibilities, a CTO must possess a number of skills. First, they need deep technical experience to help them make informed decisions. Second, leadership qualities are essential, as they need to inspire and manage the team. Communication skills are also crucial, as the CTO interacts with other executives, investors, and possibly customers, explaining the technical aspects of the business. Finally, an understanding of the market and business strategies will help the CTO tailor technology solutions to the needs of the company and its customers.

  • At one company where a group of programmers worked, the director was faced with the need to schedule their shifts. He understood that proper time management would not only increase employee productivity but also create a comfortable working environment.

    The director decided that for optimal scheduling, he needed to consider several factors. First, it was important to determine how many programmers were needed to complete tasks at different times of the day. Secondly, it was necessary to consider the employees' own preferences regarding their work schedules. Some preferred to start their day early, while others preferred working in the evenings.

    To create an effective schedule, the director conducted a survey of employees to gather information about each employee's preferences. He then began analyzing the data to balance workloads and ensure the necessary number of specialists during peak hours.

    As a result of this work, the director was able to propose an optimal schedule that met both the needs of the business and the wishes of the employees. He is confident that this approach will help increase the overall effectiveness of the team and improve the atmosphere in the team.

  • Frequently asked questions and typical tasks in interviews for testers