What the final round is
A meeting — or several — after the technical sections, where the question is no longer “can this person program” but “will we work well together.” Technical skills are usually left alone here: the sections have already covered them. Yandex describes the final (in Russian) as an hour-long meeting with the team lead, devoted to the project. An hh.ru employee puts it even more plainly: in the team interview “hard skills aren’t tested, they were already checked at the previous stage” — in other words, technical skills are not looked at here at all.
A separate final exists because of how the earlier stages are set up. T-Bank says so directly: its technical interviews are run by employees “who have no direct connection to the vacancy,” and the company asks candidates to save questions about the team and its work for the next stage. The sections test skill in isolation from the team, and the final remains the only place where the team appears at all.
Team matching: the candidate chooses the team
The most underrated feature of the final is that the choice is mutual. At Yandex this is literally built into the process: the candidate tells the recruiter in advance which services and technologies interest them, the recruiter sets up meetings with those teams — “as a rule, one to three” — and only after all the finals does the company say who is ready to extend an invitation. The offer is issued “when you choose a team.”
T-Bank follows the same logic: after the technical sections the recruiter selects projects and arranges introductions, and if several teams are interested, offers to talk to them separately or on a joint call. The company publishes neither the length of these meetings nor a limit on their number. At VK, according to a candidate’s account from February 2026, an unsuccessful final with one team was followed by an offer to talk to another project rather than a rejection.
Yandex’s stated goal, which the company wrote about in October 2025, is to get the process to a point where a candidate passes all the technical sections within a week and spends another week choosing a team. It is a goal, not a rule, but it shows how the company sees the role of the final.
Why candidates are turned down at the final
A rejection at the final usually doesn’t mean the candidate failed something. Published candidate accounts show three reasons, and failing a test is not one of them.
The first is a mismatch between the candidate’s interests and the nature of the team. In an account from March 2026 (in Russian), a candidate passed the concurrency section with a high score and the algorithms section, then heard from the manager at the final: “I get the feeling you’re more interested in technical problems, and mine is a product team.” No offer followed.
The second is competition for the same slot on a team. In another account from the same month (in Russian), a candidate passed three sections with good feedback and went to three finals — and at each one “the choice was made in favor of another candidate.” The company’s final wording: “unfortunately, at the moment we have no other vacancies we could offer you.”
The third reason is the one the stage exists for. In its hiring playbook, Avito lists what it assesses at the final: “how comfortable the candidate is with potential colleagues, whether the unit’s tasks interest them, whether their views match our values and culture” (the company calls its divisions units). None of the three reasons was a failed test, which is why preparing for the final differs from preparing for an exam: it consists entirely of a conversation about what the candidate wants from the job.
What they ask
The questions are behavioral: not “what do you know” but “what have you done.” The hh.ru team interview, as described by a company employee, has five blocks — introductions and work experience, teamwork, cases and products, priorities and growth, and finally a reverse interview in which the candidate asks the questions.
| Question | What is being assessed |
|---|---|
| “Tell us about a difficult project” | The ability to describe the context, your role and the result clearly. An answer with no personal contribution (“we decided”) devalues the whole story. |
| “Have you had a conflict in your team?” | Not an absence of conflict but the ability to talk about your own mistakes. “There were no conflicts” closes the topic worse than an honest account. |
| “What would you do if a new feature didn’t move the metrics?” | Product thinking: whether the candidate understands why their code exists. |
| “Why this team in particular?” | A match of interests — the very reason candidates are most often turned down at the final. |
| “What questions do you have for us?” | Interest in the division’s work — at Avito this is written directly into the final-round criteria. |
The STAR method
A framework worth using for any story about past experience. Amazon recommends it to candidates outright: on its hiring process page the company asks for answers to behavioral questions in STAR format — situation, task, action, result.
Answers usually break down at the third element. “We decided,” “the team did it” — and the personal contribution becomes indistinguishable; the interviewer cannot assess what they didn’t hear. The fourth element, the result, only works when it is measurable: “build time dropped from twelve minutes to four” carries more weight than “things got better.” Four or five prepared stories — a difficult project, a conflict, a failure, a decision you defended, a mistake you fixed — cover practically any behavioral question.
Questions for the team
The candidate’s questions are built into the meeting’s script: in the hh.ru team interview, the reverse interview is the fifth of five blocks. They do not appear to be scored separately — no sources could be found in which the candidate’s questions count toward the assessment. But Avito includes interest in the division’s work directly in its final-round criteria, and that interest shows precisely through questions.
Yandex presents them as the candidate’s own tool: “don’t hesitate to ask questions — it will help you learn more about the project and choose the one that interests you.” Both framings lead to the same place: questions are worth preparing in advance — about the team’s tasks for the next six months, on-call duty, code review and deployment, the reason the position is open, and how the company revisits grade and salary.
The final round by company
| Company | Who is in the meeting | What is discussed | Notable detail |
|---|---|---|---|
| Yandex | Team lead, one hour | The project, the team’s tasks, mutual interest | As a rule, one to three meetings. Who is ready to extend an invitation is announced after all the finals; the offer is issued once the candidate chooses a team |
| T-Bank | Teams from the selected projects | Projects, experience, work that interests the candidate | Technical sections are deliberately run by employees from outside the hiring team — the company asks candidates to bring their questions about the team here |
| Avito | Hiring manager and recruiter, 1 hour on Zoom | What the team does, day-to-day tasks, processes, values | The final decision is made by the hiring manager and HR |
| hh.ru | Team lead, technical head of the area, product or project manager | Experience, teamwork, cases and products, priorities, reverse interview | Technical skills are not tested at all: “they were already checked at the previous stage” |
| VK | Specific teams — in the candidate’s account, VK Video and VK Music | Experience and projects; at one of the finals the candidate was asked to design a chat for streamers | After an unsuccessful final with one team, the candidate was offered a different project instead of a rejection |
Does culture fit work?
No data could be found showing that culture-fit interviews predict job performance — neither confirming it nor systematically refuting it. There is, however, serious academic criticism of the approach itself.
Sociologist Lauren Rivera, after analyzing 120 interviews with people who make hiring decisions, found that employers systematically choose candidates who are culturally similar to themselves — in leisure pursuits, self-presentation and background — and that considerations of shared culture often outweigh considerations of productivity. In a popular summary she puts the conclusion more bluntly: “you’ll get a replica of your current employees; in many cases it’s a form of discrimination.” The study was conducted at elite US professional firms — banks, law and consulting firms — and its conclusions cannot be transferred directly to the Russian IT market. But it explains why the phrase “not a cultural fit” so often remains opaque to the candidate: behind it may lie a genuine difference in values or simply dissimilar backgrounds.
FAQ
Are technical skills tested at the final?
As a rule, no — the technical sections have already covered them. Yandex describes the final as an hour-long meeting with the team lead to discuss the project. At hh.ru, according to a company employee, the team interview doesn’t test technical skills at all: “they were already checked at the previous stage.” There are exceptions: at VK, a candidate was asked at a team final to design a chat for streamers, so it is worth confirming the format with the recruiter.
How many final rounds are there?
At Yandex, “as a rule, one to three” meetings, and this is built into the process: each interested team holds its own final. At T-Bank, if several teams are interested, you can talk to them separately or on a joint call — the recruiter will suggest the format. The point is not extra rounds of screening but the chance to compare.
Can I turn down a team I didn’t like?
Yes, that is the whole point of team matching. Turning down one team does not mean turning down the company: at Yandex the offer is issued “when you choose a team,” and in a candidate’s account of VK, after an unsuccessful final with one team he was offered a different project. Agreeing to a team whose work doesn’t interest you and leaving six months later is the worse outcome.
What is a Bar Raiser, and do Russian companies have one?
A Bar Raiser is an independent interviewer from another team at Amazon: they are not filling the vacancy and so have no stake in hiring at any cost; their job is to make sure the candidate raises the company’s overall bar. According to AWS, there are more than ten thousand such interviewers and trainees. Former Amazon executives describe them in “Working Backwards” as having veto power over the hiring manager — and in the same book note that a good Bar Raiser never explicitly exercises the veto but leads the discussion instead. No Russian company with a publicly confirmed Bar Raiser program could be found: the claim does circulate, but without primary sources.
How should I answer “tell me about a difficult conflict in your team”?
Using STAR, and without heroics. Describe the situation and your task in it, say what you personally did rather than “we decided,” and how it ended — ideally with a measurable result. “I’ve never had conflicts” sounds worse than an honest account: the interviewer is checking not whether you avoid conflict but whether you can talk about your own mistakes. In the hh.ru team interview, working through mistakes is a separate block of the meeting.
What should I ask the team at the final?
Whatever will define your work for the year ahead: what the team does and what its tasks are for the next six months; what a typical week looks like; whether there is on-call duty and how it works; how code review and deployment are done; how the company revisits grade and salary and what that depends on; why this position is open — is the team growing or did someone leave. The last question is usually the most informative.
Sources
- T-Bank: how the interview works (in Russian) — meeting the team, and why technical sections are run by people from outside the hiring team.
- Avito hiring playbook (in Russian) — the final interview: who attends, assessment criteria, who makes the final decision.
- How the team interview works at hh.ru (in Russian) — March 2024, an employee’s view: the five blocks of the meeting, who takes part, “hard skills aren’t tested.”
- Amazon: how the interview loop works — the STAR method as the recommended format for answering behavioral questions.
- The problem with hiring for cultural fit — Lauren Rivera, Kellogg: why cultural fit often turns into hiring people like yourself.
The other stages of the funnel are covered in the overview of developer interview stages. Before the final: screening, live coding, the algorithms section and System Design. The salary calculator works out how much of the offer amount is left after tax.