Hiring practices · Hiring principles · November 2026

Hiring principles: Anton Makarenko

How Uzum Nasiya's CTO selects team leads for his teams

"Hiring principles" is a series in which hiring managers talk about how they select people for their teams.

The hero of this issue is Anton Makarenko, CTO of the credit department at Uzum Fintech.

Anton hires team leads for cross-functional development teams and runs the management interview for all of Uzum's fintech. For him, a team lead is an engineering manager, not a tech lead: they manage people and processes, work in tandem with product and business, and still stay close to technology.

At interviews Anton particularly values case questions, because they make it possible to check the candidate's story about their experience. A plausible story about one's experience can be prepared in advance, including with AI. But a case shows how a person really thinks.

Anton has 17 years in development and 10+ years in management. He went from senior .NET developer to head of development at Bright Box. At Ozon he led development of the mobile app for sellers: in two years the app's share of DAU grew from 27% to 79%. At Playrix he grew the server platform teams from 7 to 29 engineers and moved a monolithic API to microservices. He has been working at Uzum Nasiya since 2026.

"In the 2010s, smart people in Russia were building Tinkoff, then Alfa — creating fintech. I was still at university back then. And in Uzbekistan fintech is now actively developing. Here there's a chance to take part in it yourself, adjusted for modern technologies and realities. And to make something great that people all over the country will use — and Uzbekistan is a huge country, 40 million people."

The main risks in hiring team leads, according to Anton Makarenko

A team lead who will break the team or accept the status quo

Most often a team lead at Uzum Nasiya has to join an already established team. One team needs calm development, another has to be pulled out of a crisis, a third has to be restructured. Anton wants the candidate not to start with the idea of "firing everyone and hiring new people", but also not to accept everything as it is.

"Many people understand how to lead a calm team where nothing changes: I'll come in, do code reviews, plan sprints, write development plans. But carrying out management changes without breaking everything can turn out to be hard for many."

To check this risk, Anton gives a case about a team that needs to be restructured and looks at where the candidate will start and in what order they will change things.

A tech lead instead of a manager

If in the CV and in the story about themselves the candidate talks only about technical wins — for example, how they cut a service's response time — and says nothing about people, product and stakeholders, for Anton this is the profile of a tech lead or principal engineer, but not a team lead. This isn't a flaw, just a completely different profile.

At the interview this most often becomes clear when discussing work with the team.

"I try to run through questions about whom the candidate manages, how the team is structured, a bit about people, processes, stakeholders. It often turns out that working with people looks like this: once every six months the team lead meets an employee, asks what they want, hears 'to learn Kafka' and then picks Kafka tasks for them. But it's important to me that a person understands how to evaluate employees and how to develop them — both technically and in terms of soft skills: ownership, communication, independence."

A manager who has moved away from hands-on work

The opposite bias is also a risk. A team lead must review technical decisions, set the team's technical vision and understand basic engineering practices. A manager used to working at the level of processes for a whole department will find this hard. In that case there should be a clear strategy for who will cover this area in the team.

How much a team lead under Anton codes themselves depends on the team: some write a lot of code, others, especially in large teams, mostly review other people's code. Anton sets the top level of the technical strategy, but every quarter the team lead proposes two or three initiatives that will best move the team along that strategy.

An example question Anton uses to check whether a candidate understands engineering practices:

"The team doesn't write unit tests or writes them badly. What do you do about it?"

❌ Weak answer: "I'll tell them to write tests. For example, I'll set an 80% coverage threshold in CI, and that's it."

✅ Strong answer: "If there are no tests, I'll first figure out why: no time, no infrastructure or no habit. I'll agree with the product manager that tests are part of the Definition of Done for every task. We can start with tests for the scenarios that bring in the most money and add them to the acceptance criteria. And in a quarter we'll see how many incidents there are."

A team lead who doesn't take responsibility

There are fewer and fewer adjacent roles around a team lead: architects, project managers, analysts. This is a feature of the modern world with AI in development. So the "that's not my job" stance doesn't work for Anton.

"If a team lead says 'this should be done by an architect, this by the product manager, this by the project manager, this by one kind of analyst, that by another kind of analyst, and I'd like everything as pre-digested as possible' — we won't work well together."

Stages of selection for Anton's team

  1. 1HR screening
  2. 2System design
  3. 3Management interview
  4. 4Final interview
  5. 5Offer

The management interview is shared across all of Uzum's fintech: several interviewers can run it, including Anton. The final interview is run by the hiring manager of the specific team — they decide whether the candidate is right for them.

What guides Anton in hiring

First contact

You can and should write to Anton directly: he posts about vacancies on LinkedIn himself. The main thing is that the message makes it immediately clear which role it's about and what experience the person has. Sometimes Anton even writes first to people he has noticed in his feed. According to him, such messages have already led to hires.

By the end of this year LinkedIn is the third-largest source of hires in Uzum's fintech, after job sites and referrals.

CV

In a team lead's CV Anton looks for two sides: managerial (people, processes, product, stakeholders) and technical. At the same time, interview results always take priority for him.

A candidate's education is not a key factor in Anton's decision.

Engineering thinking matters more than a specific language.

"I know that, say, in a banking business unit it's sometimes more important that a candidate has experience with a specific language. But for me system design matters more here. It's about thinking, about the ability to understand what a system looks like at all, how to fit into it and how to change it."

Team size isn't that important, but within certain limits.

If a candidate had a great many people reporting to them, Anton will look into whether such a person is ready for a team lead role. But if a person calls themselves a team lead and their team is one person, they are de facto not a team lead.

Career gaps and holding several jobs are a reason for a conversation.

This isn't a red flag, but Anton will ask about it. As for career gaps, he says that, for example, around 2022 it's an understandable story for him. Holding several jobs isn't necessarily bad either, but there will be a separate conversation about it.

"I periodically say: 'Look, we have a high pace and a fairly steep onboarding curve, how are you planning to combine jobs? Do you have a strategy, an understanding of how to fit it all in?' Because a person's cognitive capacity is limited."

Domain expertise matters, but doesn't play a key role in selection.

Lack of domain experience isn't a blocker for hiring. How important it is depends on the specific team.

"If I limit myself to candidates from fintech, there'll be tears: it cuts the funnel far too much. Much more important to me are strong management skills and good technical ones — at least at the system design level. A person who is good both as an engineer and as a manager will be able to figure out our product. But the chance that our approaches will match how, say, scoring is done at some large bank is pretty low.

It happens the other way around too, of course: a person comes with valuable domain expertise, but something else isn't top-notch. In that case the other skills can be built up. But if all of a candidate's strengths are limited to the domain, they won't be a fit for us. In 80% of cases skills outweigh the name of the previous company on a CV."

Red flags in a CV

Frequent job changes throughout the career

If a person worked everywhere for a year or six months, for a team lead that's a red flag. Why: in this case a person, as a rule, didn't see the results of the decisions they made. In management this isn't visible instantly. And, consequently, they didn't gain valuable experience they could reflect on.

Anton understands short tenures around 2022. But if the whole career looks like that, the person most likely didn't learn from their decisions and their consequences.

Not red, but a yellow flag: functional leadership without your own area of responsibility

Anton looks especially closely at matrix reporting. A functional QA or development lead often writes standards and explains how things should be done, but doesn't develop the product together with their team. For Anton this is different work and a big risk. Anton is still ready to interview such candidates, but pays close attention to the risks.

"Setting standards is one thing, but being responsible for your whole 'patch' — for the people, for the product together with the product manager, for the technology — is completely different work."

The interview with Anton

Anton's management interview usually lasts an hour and a half.

In the story about experience, Anton compares the candidate's past work with what awaits them: a cross-functional team with engineers of different specialties. So he asks in detail about the structure: who was on the team; who was responsible for what. In short, he runs through 5 blocks: people, processes, technology, stakeholders, product/business.

Then Anton checks this story with a case. If a person thinks the right way but will be doing such work for the first time, it's still a big risk. Anton will flag it to the hiring manager so they can look into it at the final interview and make an informed decision.

What Anton looks at in the management interview

Balance of management and technology
The story about experience includes people, processes, product and stakeholders, and at the same time the person isn't cut off from technology. This is usually visible in the first part of the interview: what they manage, what the structure is, who's around.
Working with an existing team
Checked with a case. The main thing Anton looks at is whether the person will break the team or accept things as they are.
Systematic people management
Does the candidate have a system for working with people: 1:1s, evaluation, development, feedback. Visible in the story about experience and in the people part of the case.
Technical leadership
Can the candidate validate technical decisions, set the team's technical vision and fix engineering practices. Visible from questions like "the team doesn't write tests — what do you do".
Predictability and planning
How the candidate commits to a large project and how they make sure the team delivers on time. Checked with case questions.
Product, stakeholders, independence
How the candidate works with product and business and whether they are ready to figure out a task themselves rather than wait for an analyst, architect or product manager to spell everything out. Visible both in the story about experience and in the case.
Consistency between experience and case
Does the way the candidate talks about their experience match the way they reason in the case.

Red flags at the interview

Ivory tower

A stance in which techies wall themselves off from the business and see no point in transparency and interaction. A yellow flag is the stance of an executor who does what they're told and doesn't dig into why.

"A candidate with the stance 'we want to sit in a high castle, while some nasty business outside the walls wants something' won't be a fit for me."

Unsystematic people management

Anton wants to see that the candidate doesn't just react to situations but has a clear system for working with people, where everyone has a clear plan. Someone who isn't coping has an improvement plan with milestones and metrics. A strong specialist has a development plan, also with milestones and achievable results.

"It should be proactive and managed. For example, here's Ivanov: we openly discuss the mismatch in expectations with him, maybe we start a PIP, and it has a scope, milestones, metrics. And here's Petrov, a high performer: he has a PIP with a plus sign, that is, an individual development plan."

Processes by the textbook

Anton doesn't need a retelling of theory. He wants the candidate to have common sense and to understand how to plan, how to commit to a large project on short and long horizons and how to ensure predictability.

"I'm not a big fan of the 'let's now recite all of Kanban in alphabetical order' approach."

Inability to work in a distributed team

A specific feature of Uzum Nasiya is many remote and hybrid teams: some people go to the office in Tashkent, some work from other places. And across Uzum as a whole there are many hybrid teams. If at the interview a candidate says you can only work effectively in the office, that's a minus.

"If I were the candidate, I wouldn't declare that remote work is hard and everyone should be in the office. We still live in a reality with a lot of remote work — otherwise hiring takes many times longer. A team lead must understand how to build an effective hybrid team."

"We don't need this AI"

Anton doesn't yet ask in detail about pipelines, harnesses and models, but always looks at what the person has done with AI and whether there's outright denial.

"For now I just assess what the person has done and whether there's some obvious dysfunction like 'we don't need this AI'."

Green flags at the interview

Business metrics the candidate really understands

According to Anton, team leads who manage a team through business and product metrics are a great rarity. Lack of such experience isn't a red flag, but having it is a big plus.

Important: interest in business metrics is a socially approved answer, so Anton will check whether the candidate really understands what they're talking about.

"Everyone is used to this being the 'right' answer and says business metrics are very important and interesting to them. But sometimes it turns out that team management and business metrics don't intersect, that is, in reality the candidate didn't make management decisions based on business metrics."

QA as partners

If testers were in another department, Anton wants to hear that the team under the candidate was still responsible for the product working, not just for shipping code.

"It's a warning sign if the interview gives the impression that the interests of the development lead and QA are different. In fact they should be the same: a team lead is responsible not just for shipping something to production, but for making it work well."

Developing people beyond technology

Giving your people interesting tasks isn't enough. Anton cares how a team lead develops independence in people and the ability to own a feature end to end. According to him, as an engineer grows to senior, this becomes almost inevitable.

Experience with a team of seniors and with letting people go

Many people know how to grow interns and juniors. If the team has many strong seniors, Anton looks at whether the candidate understands how to keep them interested and give them a transparent growth track. For some teams experience with dismissals matters too.

"It's always a painful, difficult process, and the first time you go through it, it's hard. It's better with experience than without it."

Cases at the interview

At interviews Anton usually gives a case that brings together all the typical problems.

"With a case like this you can talk about both people and processes. And also see whether the person understands a subtle thing: changes can't always be pushed through. In a crisis you can. But in a team whose status is 'sustaining success', you can't."

An example management case from Anton Makarenko

Anton's full case is longer. For the article we shortened it slightly and left out some details, but kept everything that matters for the breakdown.

Case

There is a bank's technology division of 150 people. It's distributed, with people from all over the CIS. Each area has 2–4 cross-functional teams. Teams choose their internal process themselves but must follow a common task intake interface and be able to set stakeholders' expectations. Engineering culture has grown over the past year, but quality is still a problem: testing is largely manual, and most backend developers don't understand the nuances of working with databases and can't design architecture. Team leads are mostly still green: the role appeared relatively recently.

You're joining the "Client Chat" team as team lead. The team has 12 people: backend (4), frontend (2), mobile (3), QA (2), analyst (1). The previous team lead didn't cope and went back to development in the same team (a 50/50 decision, half voluntary, half forced). He himself wants to work in an expert staff engineer role and lead cross-team projects. Some individuals on the team show toxic behavior in code reviews and technical arguments.

The team gets a lot of small tasks from all its neighbors, and they push out the priority ones. The team takes on too much and puts some tasks on the back burner, so stakeholders think it can't be relied on. The product owner has taken over planning, estimation and external communication, but is overloaded and doesn't have time to get into the team's context. The team feels under-managed, and relations are tense.

Meanwhile the company is growing, and your domain is expected to start delivering stable results on AI-based contact center automation within 4–6 months. What will you do?

How Anton evaluates the answer

First Anton asks for a rough plan: what to tackle first and what later. Then he digs into each problem and complicates the inputs as he goes. For example, he says there are no processes in the team at all or that there's no architect role in the company.

A stream of small tasks and a big project. Anton asks how to fit a big strategic project and the constant stream of routine work into one set of priorities. He called separating the streams a good move. For example, a rotating on-duty person handles small requests while the rest of the team works on the project.

The project doesn't fit the deadline. Say the estimate comes out at 8–9 months instead of 4–6. Anton expects a set of tools. Build an MVP and then add functionality. Simplify the solution, understanding what you'll have to pay for it later. Cut scope. Ask other teams for help or hand them part of the project. The mistake is closing the gap with overtime.

"Overtime works for a week or two, but a team can't work overtime every day for six months."

A product owner used to standing in for the team lead. Barging in and taking everything is a bad move. Anton expects the candidate to build trust through transparency and take over areas of responsibility gradually.

"Trust won't grow by itself; it grows through more transparency. You have to go step by step: 'Let's start doing it together, then you'll see that everything is fine, and you'll be able to hand over areas of responsibility one by one.'"

The former team lead on the team. Anton expects the candidate to see the risk. It's important to understand how to earn the trust of such an employee and what growth track to offer him.

Engineers outside your background. If a team lead has never worked with certain technologies, they don't need to assess engineers' skills alone: it's better to bring in experts from the company.

The offer

Discussing terms at the offer stage is normal in Anton's opinion, as long as the negotiations are constructive. "Just asking for twice as much" is a bad move. A good one is looking for a configuration in which both sides win.

"An example: when hiring team leads, we very much want the person to come for the whole onboarding and spend longer in Tashkent to work with the team in the office. But sometimes a super-strong candidate can't come for all four months. And that's where negotiations begin: what if we do it like this? What about this configuration? The main thing is that we hear each other and can reach an agreement."

This is a piece from the "Hiring principles" series, in which hiring managers talk about how they select people for their teams. Read other pieces in the series

Have a role nobody can fill? Let's talk.

contact@new.hr