Contents:

Free course: "Quick start in Python"
Learn more
Infrastructure services developer with experience at Yandex, specializing in managed Databases. In his free time, he enjoys workout, shooting, snowboarding, singing, and playing the guitar. His professional skills and hobbies help him develop a creative approach to solving problems in the field of infrastructure development and optimization.
Links play a key role in the structure and functionality of websites. They provide navigation between different pages and resources on the internet. It is important to use links correctly to improve your site's search engine optimization (SEO). Internal links help search engines index your content, and external links increase the authority and trust of your site.
Quality links can significantly increase traffic, so it is important to ensure their relevance and currency. Use anchor texts that accurately reflect the content of the page you are linking to. This will help both users and search engines better understand what is being linked to.
It is also worth considering that links must be current and work correctly. They should be regularly checked for broken or inaccessible addresses. Proper use of links not only improves the user experience but also contributes to improved search rankings.
I classify development into two main areas: business development and infrastructure development. Infrastructure development includes all aspects that support developers, including tools and platforms. While business development encompasses the creation of services and applications aimed at end users to meet their needs and improve the user experience.
I work at Yandex Cloud, and our team specializes in managed Redis and MongoDB databases. Managed databases allow clients to avoid the need to configure and administer database management systems for their projects. We provide ready-made, deployed, and fully functioning databases on our powerful servers, which significantly simplifies the development and data management process for our users.
Yandex operates several data centers located in Russia, as well as one in Finland. These centers are based on our own servers, which are manufactured in China and Taiwan. Design is carried out entirely in-house, tailored to specific needs. Yandex's key priorities are energy efficiency and user satisfaction.
Large organizations typically have multiple levels of employee interaction with data centers. Software developers typically rarely visit these centers and may not have a clear understanding of the physical devices running their code. My services do not require deep interaction with low-level technologies, so I do not visit the data centers myself.
In communicating with business development professionals, I have identified several key differences from working on infrastructure projects. First, business development is focused on meeting the specific needs of clients and users, while infrastructure projects most often focus on creating and maintaining core systems and technologies. Second, business development emphasizes flexibility and rapid adaptation to changing market conditions, which requires the team to be highly responsive and able to work under uncertainty. Third, business projects emphasize user experience and interface design, requiring a deep understanding of the target audience and their preferences. These differences create a unique approach to project management and require specific skills and knowledge. Domain-driven design, known as DDD, is widely used in business development, although its application in infrastructure development is impractical. DDD helps analyze complex aspects of the real world, allowing for a more accurate description of the system. In business development, requirements can be less formal and more fluid, as they depend on the dynamics of human interactions and processes. In contrast, infrastructure development requires strict and formal requirements, as servers operate predictably, based on the principles of physics and computer science. In this area, there are fewer edge cases and exceptions, making tasks more understandable and manageable. Personally, I prefer infrastructure projects because their complexity lies in algorithms and scientific principles, rather than in attempts to formalize complex human interactions.
Complex and customized knowledge-intensive tasks are encountered much more often in infrastructure development than in business development. In the latter, as programmers joke, the main work comes down to simply transferring data from JSON format to databases and processing it in accordance with the rules established in DDD. Infrastructure projects, however, require deeper technical knowledge and innovative approaches to solving unique problems related to system architecture and integration. This makes infrastructure development more complex and demanding, requiring the application of modern technologies and methods to achieve effective results.
Maintaining the coordinated operation of multiple servers is a standard task in infrastructure development. However, there are many nuances. Developers often perceive the network and hard drives as unreliable components, which can lead to problems in system operation. Furthermore, the processor does not always execute code as originally written: the order of instructions may change or they may be relocated, which can also affect the expected result. Therefore, it is important to consider these factors when designing and developing distributed systems to ensure their stability and reliability.
This requires delving into the details and studying low-level aspects. In business development, programmers are often shielded from such issues by the use of frameworks and multiple layers of abstraction. This allows them to focus on higher-level tasks and speeds up the development process, but knowledge of the fundamentals remains important for efficient work and problem-solving.
Modern IT systems are often built on compromises, as some aspects cannot be implemented with perfect accuracy. For example, synchronizing time across multiple servers down to the nanosecond is an impossible task. Even when using fiber optic cables to connect servers, there will always be a signal transmission delay. Therefore, it's important to consider such nuances in advance when designing and implementing IT systems to minimize potential problems and improve their efficiency.
I fully recognize the importance of the work of programmers developing business services. They have their own unique approach and scope of work. Personally, I'm not ready to transition into business development at this time, as I lack the necessary experience. However, I am extremely interested in learning the internal mechanisms and technologies that underlie these systems.
Working with infrastructure in a large company
Previously, I developed infrastructure services at Red Hat, including CI/CD systems and monitoring systems. Currently, I work in the managed database service. This service is part of Yandex.Cloud and offers users a simple and convenient way to deploy cloud databases, freeing them from the need to deal with technical support and administration. Managed databases allow you to focus on business development, optimizing costs and setup time.
The client requests the installation and configuration of databases such as MongoDB or Redis, specifying the required number of resources. We professionally install and configure the necessary packages, providing the client with a fully operational and functional database.
In small companies, DevOps engineers only need to create a functional system. However, in larger organizations, it's essential to develop scalable solutions that can efficiently run on thousands or even millions of instances.
The basic skills remain the same: installing the packages and dependencies required for an application to function. However, in a small startup, you'll need to deploy the entire infrastructure on two or three dedicated servers or a rented Kubernetes cluster, allowing you to run all application components simultaneously. This approach provides greater scalability and simplifies resource management, which is critical for rapid startup growth.
In larger companies, the process of working with Kubernetes and other orchestrators has its own specifics. First, your colleagues from the infrastructure department must install and configure Kubernetes themselves, and then all the necessary applications and configurations can be added. Because large organizations face many such tasks, they often have in-house specialists who are exclusively dedicated to installing and configuring Kubernetes on a full-time basis. This ensures the stability and efficiency of applications in a cloud environment.
I have extensive experience at the intersection of DevOps and programming. At my previous startup company, I focused on DevOps, which allowed me to develop my skills in automation and infrastructure management. I now apply these skills to building effective infrastructure services for various organizations, improving their performance and reliability. My experience includes implementing CI/CD processes, managing cloud resources, and optimizing the development workflow. Configuration management automation processes vary significantly depending on the tools used. For example, Ansible is more often used for smaller projects and teams, as managing large playbooks and deploying them to thousands of servers can be challenging. In our team, we prefer to use Salt and a number of specialized internal tools. This is not a unique practice—even at Red Hat, the developer of Ansible, many employees choose other tools because Ansible doesn't meet their requirements. What an Infrastructure Engineer's Day Is Like and What Tools They Use A developer's day is similar at different companies. The morning begins with waking up, followed by a shower and a cup of coffee. Then the developer gets to work, reviewing the previous day's events: updating email, analyzing code review status, and identifying potential issues. After that, most of the time is spent writing code, participating in meetings, and discussing any issues that arise. This daily routine helps maintain productivity and effectively address the challenges the development team faces.
In addition to standard meeting formats such as daily standups, our team holds specialized architectural meetings. During these meetings, we discuss the project's architecture in detail and identify priority tasks related to its improvement and development. I also have shifts during which I monitor the state of the infrastructure and promptly resolve any issues that arise. These approaches help us maintain high quality work and respond promptly to challenges, which is an essential aspect of successful project delivery.
At my previous job, I held the position of team lead, which required me to communicate daily with other teams, formulate large goals, plan necessary equipment for the year ahead, and perform many routine tasks in addition to writing code. At Yandex, I work as a developer, which allows me to focus on programming and minimize my involvement in management responsibilities. This allows me to devote more time to developing and improving the quality of code.
In my work, I use a number of tools and resources that significantly improve my productivity and the quality of my work. The most important of these are specialized project management software applications that help organize my workflow and control task deadlines. Also integral to my work are analytical tools, allowing me to track the effectiveness of various strategies and make informed decisions.
Furthermore, I actively use communication tools with colleagues and clients, which facilitate the rapid exchange of information and joint work on projects. An important aspect is the use of platforms for storing and sharing documents, which provides access to the necessary information at any time and from any device.
These tools help me not only optimize my workflow, but also achieve my goals on time.
- Code editor - in my case, it's Visual Studio Code.
- Communication tools - depending on the company, this could be Telegram, Zoom, Slack, email.
- Console - this is where I "live" and perform most of my operations.
- Code storage and code review tools - these could be repositories or specialized tools like Gerrit. It all depends on what the team is used to. For example, at Red Hat, the guys developing the Linux kernel exchange code via email - they send patches directly in emails.
- Docker. It covers the need for all other tools. If you need a database, you can set it up in Docker; if you need any automation tools, it's a lifesaver there too. Sometimes I even set up a compiler or interpreter in Docker if I need to compile code to a specific version. Docker was a breakthrough technology back in the day—I don't even know how anyone could live without it.
- Kubernetes is an orchestrator, a tool for deploying containers on a large fleet of servers in a cluster. It creates a large virtual cluster and helps you manage it conveniently. Nowadays, Kubernetes works with more than just Docker—although Google initially created Kubernetes specifically for it. For example, there's the Open Container initiative, which describes how containers should run and what they should look like—and Kubernetes supports it. And Red Hat's fork of Kubernetes, OpenShift, can work with Red Hat's Docker equivalent, Podman.
- Yandex's own tools. For CI/CD, we use our own tools or publicly available solutions like Jenkins. Custom tools emerge evolutionarily: first, you put together a small script to automate a process. Then you modify it to behave differently depending on the task, and then implement it across other teams. For example, at Yandex, we have a version control system, a build system, and our own code repository. Of course, such solutions are created with an eye on standard tools, and many of the commands are the same, but they still take some getting used to.
Key Knowledge and Skills of a Senior Developer
I'm a senior developer, and for this level, real-world experience is key. Stories about twenty-year-old team leads often seem comical, because if someone didn't start working as a programmer at an early age, they simply won't have enough experience to manage large systems at such a young age. Becoming a senior developer in a corporate environment requires certain knowledge and skills. It's important to have a strong understanding of software architecture, be able to effectively work with various technologies and tools, and have experience collaborating with a team and managing projects. This will allow you to successfully handle the challenges that arise during the development of complex systems.
Algorithms play a key role in programming and computer science. A fundamental understanding of various algorithms and their operating principles is essential. Understanding the asymptotic behavior of algorithms allows one to evaluate the efficiency and performance of solutions depending on the size of the input data. Furthermore, knowledge of the fundamentals of distributed computing aids in the development of scalable and high-performance systems. Studying these topics contributes to the creation of optimized software solutions and improves programming skills.
Architecture and familiarity with various technologies play a key role in assessing a developer's skill level. At my previous job, I conducted interviews focused on architectural aspects, which I call "senior interviews." A deep understanding of architecture allows one to immediately determine a candidate's true skill level. Even if a developer demonstrates excellent skills in solving complex algorithmic problems, a lack of system design skills calls into question their senior status. It's important for specialists not only to understand theory but also to be able to apply it in practice, creating sustainable and scalable solutions.
I've had candidates approach me who worked for ten years at the same company and rose from junior to senior. During this time, they worked exclusively on one project, in which they achieved a high degree of mastery. However, when the question arises of building a new system or using different technologies, they encounter difficulties. This is because their experience is limited to the tools and methods they have used over all these years. As a result, such specialists develop a cargo cult: they follow established processes, even if these solutions are not optimal. This emphasizes the importance of diverse experience and a willingness to learn new technologies in the development field.
Diverse experience is an important aspect for a developer's professional growth. By working for different companies, a specialist can become familiar with a variety of solutions and technologies, which contributes to the development of their expertise. The key is the diversity of technologies used in these companies. This allows developers to easily switch between different technology stacks, master new tools and practices, which in turn increases their competitiveness in the job market. Diversity of experience helps not only deepen knowledge but also broaden horizons, which is critical in the rapidly changing world of IT.
I became interested in ZooKeeper, although I had no experience with it before. In one day, I studied the documentation and familiarized myself with the internal algorithms, and then started using it. In practice, mastering the basics of any technology and creating simple applications usually takes one or two days. After a couple of months of regular practice, you will be able to confidently navigate a new technology and solve more complex problems. The exception is complex systems like Kubernetes, which can take significantly longer to learn.
The Go programming language holds a special place in my heart. I love its simplicity and efficiency, and I thoroughly enjoy working with it. I even taught a Go course to share my knowledge and experience. I'm always happy to recommend Go as a great development tool and encourage others to give it a try.
Go is one of the most suitable programming languages for infrastructure projects. Its efficiency and ease of use make it an ideal choice for creating complex systems. Examples of successful applications such as Kubernetes and Docker confirm the high performance and reliability of Go. These technologies are actively used in cloud computing and containerization, which emphasizes the importance of Go in modern development. Choosing Go for infrastructure solutions opens up opportunities to optimize processes and improve interaction between system components.
Soft skills play an important role in modern programming. In the early 2000s, the emphasis was mainly on technical skills, and brilliant programmers could get by without developed soft skills. However, over time, companies realized that such approaches are not always justified. Programming is a team effort, and if a talented developer leaves the organization, who will continue and maintain their code? Having a strong team with both technical and soft skills significantly reduces risks and ensures project stability. Developing communication, collaboration, and conflict resolution skills is becoming an integral part of successful work in the IT field.

With a promotion As you move up the ladder, soft skills become increasingly important as the need for effective communication increases. While at the entry-level, for example, a junior specialist interacts primarily with their immediate manager, a middle specialist begins to actively discuss tasks and find solutions in collaboration with colleagues. A team lead, performing management functions, devotes significant time to communication, making communication skills key to successfully fulfilling their responsibilities. Developing soft skills not only improves teamwork but also contributes to career advancement and increased productivity.
As a team lead, I found that managing the team took up more time than writing code. I always preferred engineering tasks, and constant communication—writing messages, organizing, and participating in meetings—became exhausting. Ultimately, I decided to return to development, where I can focus on the technical aspects of the work and implement my ideas in code.
How to Pass an Enterprise Interview as a Senior Developer
To receive an offer for a Senior Infrastructure Services Developer position at a large company like Yandex, you need to pass a series of interviews. This process includes an assessment of both technical and soft skills, allowing the employer to verify the candidate's qualifications and ability to work in a team. Preparing for interviews is important, and focusing on key aspects such as experience with modern technologies, the ability to solve complex problems, and communication skills can significantly increase your chances of successful employment.
At the first interview, I introduced myself and solved a standard algorithmic problem. In addition, I was asked about the structure of operating systems, especially UNIX, and my knowledge of computer science was tested. The questions were about SQL, which is also an important part of the basic knowledge. These aspects form the basis necessary for successful work in high positions in IT.

A junior developer can write code in C#, Without always understanding the inner workings of their code, they may send HTTP requests or process them on their web service without delving into details such as connection creation and networking principles. However, understanding these processes can significantly improve their skills and the quality of their development. Understanding how HTTP works, the different request methods available, and how data is processed will enable a developer to create more efficient and reliable applications. Understanding the fundamentals of networking and web service architecture is an important step in a developer's career and contributes to a better understanding of software development and debugging.
As you progress to a more advanced level developer, it's important to understand that HTTP requests represent a multi-layered abstraction, and problems can arise at each of these layers. For example, open file descriptor limits can be exhausted, or network issues can occur, leading to packet loss. These nuances must be considered for developing fault-tolerant systems, not just for writing code. Understanding these aspects ensures the reliability and stability of your applications, which is key in modern web development.
Algorithms play a key role in the technical hiring process at companies like Yandex. At one stage of the interview, candidates are required to demonstrate their skills in solving algorithmic problems. I recommend paying special attention to this aspect and developing your abilities in this area. Personally, this was difficult for me, as I am not an expert in algorithms. However, I prepared for the interview using the LeetCode platform, which significantly increased my chances of success. It is also worth noting that previous experience in programming proved useful during the preparation process. Developing skills in algorithms will not only help you pass the interview, but also become the basis for a successful career in IT.

Architecture. During the interview, I particularly liked the abstract problem they proposed for discussion. I believe this format is exactly what meets the interview standards for a senior specialist. This approach allows us to evaluate not only the candidate's technical skills but also their ability to think analytically and solve complex problems, which is key in software architecture.
In my understanding, a Junior developer is a developer who receives clearly defined tasks and completes them, creating code according to the specified requirements. A Middle developer is already capable of independently developing functionally complete software units, choosing the appropriate methods and tools. A Senior developer faces real-world challenges: they only need to define the problem, after which they independently determine the technologies, stack, architecture, and systems necessary to solve it. This approach allows Senior specialists to more effectively cope with complex tasks and offer optimal solutions.
An example of an abstract problem in architecture is the development of a service for generating and issuing promo codes. This is a relevant task that companies may face in real life. During the interview, it's important to consider these tasks from multiple perspectives, including architecture design, technology selection, and scalability. Security, user management, and integration with existing systems should also be considered. The key is to create a reliable and efficient solution that can meet the needs of the business and users.
For a successful goal analysis, it's important to identify potential pitfalls. To do this, ask clarifying questions: have service metrics been defined, what workloads are planned, who will be using the service, and are there SLOs, SLIs, and SLAs? This will help you better understand requirements and expectations and prevent potential problems during service development and operation.
It's important to conduct a user needs analysis. In this context, it's crucial that the promo code request process always remains functional, requests are not lost, and that identical promo codes are not issued to the same user repeatedly. The basic idea is to first determine user requirements and then develop the system architecture based on these requirements. This approach will ensure the reliability and efficiency of the service.
Experienced users can quickly identify vulnerabilities in the service. For example, if two people submit a request for a promo code within a minimal time difference, a classic data race problem can occur. In this case, the system may select the first available code from the database and send it to both users simultaneously. As a result, one of them may encounter an inactive promo code. To solve this problem, it is necessary to synchronize processes and use special methods, such as transactions or distributed consensus systems, to ensure the correct and consistent execution of requests.
To effectively estimate the required number of servers, it is important to consider several factors. First, you need to analyze the volume of data that will be processed. This includes understanding the average request size and the expected number of users. You should also estimate the load on the servers, taking into account peak activity hours.
Knowledge of data encodings is equally important, as different encodings can affect the size of requests. For example, UTF-8 requires more bytes to store some characters compared to ASCII. Thus, understanding how many characters fit in a request will help you more accurately determine how many servers will be required to handle the expected load.
Ultimately, a competent approach to server evaluation includes data analysis, an understanding of the load, and knowledge of encoding principles. This will allow you to create a stable and productive infrastructure that meets business requirements.
To accurately predict the load and the number of requests the system can handle per second, you must rely on accumulated experience. Analysis of historical data, the use of specialized tools, and load testing will help you form a well-founded estimate. This will allow you to identify potential bottlenecks in advance and optimize system performance. Also, consider the ability to scale resources depending on increased load, which will ensure the stable operation of your platform.
An important step is deploying the application and ensuring its stable operation. Many candidates claim that this requires renting a server and using Docker Compose. However, interviewers often ask, "What if the server or service goes down?" This question assesses the candidate's problem-solving ability and relevant experience. Depending on their skill level, the candidate may offer various solutions, such as hosting an application in Kubernetes, implementing geo-distributed systems, or geo-sharding data. Using AnyCast to route requests to the nearest data center using a specific IP address may also be considered. It's important that the candidate is familiar with various approaches and solutions that can ensure service reliability and availability.
The team interview is the final stage, where you'll introduce yourself, assess your ability to interact with your future colleagues, and determine how you fit into the company's corporate culture. At this stage, you'll likely be asked questions about previous tasks you've completed and how your experience aligns with Yandex's team processes. Be prepared to demonstrate your skills and explain how they can be applied to achieving the team's goals.
Learn also:
- How a C++ developer turned his pet project into a profitable startup
- A hydrogen bomb instead of "Hello, world!": how and why the first computer was invented
- Hotkeys in VS Code

