The process will be described as it’s practiced at Avito. Other companies may differ, as they shape internal processes based on their own experiences. Read the full TDR process description in the company playbook. Maturity Model of Project Solutions Let’s look at a simplified model of “maturity” in project solutions, broken down into 5 levels: Level 1 We write code Level 2 We write code -> Get approval Level 3➤ Read more...

Hope you’re all familiar with this problem, but if not, you can read this article for context and try it yourself on LeetCode (it’s an easy-level problem). Back in February, I created a repository called fizz-buzz-world, making it easy for others to contribute. I added a few of my own solutions, basic logic tests, and a well-organized README encouraging people to submit their own versions of this classic problem. The goal was simple: gather creative, out-of-the-box Fizz Buzz solutions written in Go.➤ Read more...

Many developers, when transitioning to Go, start looking for an easy and convenient way to work with databases. It’s normal – developers get used to tools that make their lives easier. When I was writing in C#, I used Entity Framework Core – the ORM for the .NET platform. Since it was my first language, I thought this was the natural way to work, and I never really considered alternatives (maybe there weren’t any on .➤ Read more...

In mature cross-functional teams, there’s a concept known as a feature lead. This role involves taking responsibility for the outcome of a specific feature, and it becomes especially valuable when a product team is working on multiple initiatives, each potentially comprising many features. It’s generally expected that senior engineers or higher take on this role regularly. However, it’s also a great practice for mid-level engineers to show initiative and step up into these responsibilities.➤ Read more...

The brain is the most energy-consuming part of our body. It often deceives us, but why? The answer is simple: to save us by conserving resources for its complex work. Clearly, this doesn’t sit well with us, especially since software development is a complex and creative task that demands maximum engagement from everyone involved. I’m sure many of you are familiar with the concept of asking questions. There’s a saying: “A well-asked question is half the answer.➤ Read more...

Yesterday marked exactly two years since I started working at Avito. During this time, I’ve significantly grown as a professional. I have an excellent team that supports one another, helps achieve results, and is always ready to share leisure time. Of course, there’s a sense that not everyone is as fortunate with their colleagues, and situations can vary. But this is precisely why the final interview (or fit interview) exists; I had three of them when I was hired.➤ Read more...

My answer: no. And it’s not about the mistakes we make accidentally due to carelessness or lack of knowledge, but rather about more complex matters. For the past month, I’ve been working on a feature that’s crucial for our team. During this time, we focused solely on the backend, while the frontend lagged behind. To close my tasks without waiting for the frontend and move on to others, I thoroughly tested everything: I wrote unit tests for the new logic, checked the correctness of the responses using Postman, merged my changes into master, and deployed the service to production.➤ Read more...

Throughout my career, I can’t recall a single moment when I didn’t think about creating my own website or blog. Even when I was a junior engineer, I envisioned having a personal portfolio page where I could showcase the projects I had worked on. This year, one of my goals was to set up my own blog on a separate domain. Time passed, but nothing progressed because I realized that it required resources: time and money for infrastructure.➤ Read more...

One of the key competencies looked at during potential grade reviews is “engineering culture.” At Avito, the signs of reaching level E5 (Senior) are defined as: Improving the overall engineering tools of the company. Testing complex corner cases. Designing testable systems and fixing those that are hard to test. Identifying inefficiencies in code/architecture/test models and adding to the team’s technical backlog. Establishing and testing non-functional requirements or engaging experts for this purpose.➤ Read more...

Yesterday, I was installing an extension for VS Code, which is maintained by colleagues for internal development convenience. It was a simple plugin that colorizes brief files (a corporate standard for describing contracts similar to protobuf; you can read more about it here), but it presented me with a challenge. In large companies, it’s customary to write documentation. Having documentation is good, but it’s even more important for it to be kept up to date; otherwise, no one will use it.➤ Read more...