YANDEX logo

YANDEX Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 13 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
92.3% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at YANDEX.

Showing 3 of 13
YANDEX logo
YANDEX

Software Engineer

Engineering · nearly a year ago

Mid Difficult Positive experience No offer 5 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen Onsite
Interview formats
Coding Technical Behavioral

It started with an intro call, then a coding round, an advanced C++ round, a TDD round (which is behavioral with extra steps, I was okay with it, but many might not endure it), and finally the usual Yandex finals. It was a lot of interviews.

Confirmed questions1 question
  • Could you implement an LRU cache in C++?
YANDEX logo
YANDEX

Software Engineer

Engineering · a year ago

Senior Difficult Positive experience No offer 5 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen Technical screen Group
Interview formats
Technical Coding System Design Behavioral

The process for this iOS Engineer role starts with a recruiter call, then moves to a dev screening, followed by an architecture discussion, an algorithms round, and finally a cultural fit interview. It was a pretty good experience overall, though the heavy emphasis on algorithms felt a bit much.

Confirmed questions4 questions
  • Could you present solutions for several iOS-related tasks?
  • How would you resolve a technical issue within the architecture module using interfaces and implementation?
  • Describe your approach to system design.
YANDEX logo
YANDEX

Software Engineer Intern

Engineering · a year ago

Intern Average Neutral experience Decline offer 2 rounds
Interview process
Technical screen Technical screen
Interview formats
Technical Coding

The interview process involved two technical rounds. The first technical round focused on JavaScript understanding with four small problems. The second technical round consisted of Leetcode-style JavaScript questions. The interviewers were friendly. The process did not proceed to the team match phase because they only offer positions in Russia and do not have remote options.

Confirmed questions1 question
  • Can you explain closures, timer, bind, and apply in JavaScript?

YANDEX Software Engineer Interview Questions

Quoted word for word from YANDEX interview reports.

What is the solution for Leetcode 161: One distance apart?

Read reports

Write the classifier algorithm for their data, which was solved by Yandex CatBoost.

Read reports

Can you explain closures, timer, bind, and apply in JavaScript?

Read report

Formats, difficulty and experience

Across all 13 YANDEX interview reports.

Interview formats

Coding 40%
Technical 33.3%
Behavioral 16.7%
System Design 10%

Interview difficulty

Easy 7.7%
Average 69.2%
Difficult 23.1%

Candidate experience

Positive 92.3%
Neutral 7.7%