Super Russian IT employer
Super Russian IT employer
Yandex is really a modern tech company.
Smart people, interesting projects, flexible working hours, a beautiful office, rather good insurance, and nice business trips to Moscow HQ if needed.
Office could have a better location in St. Petersburg.
Big company - some processes can be not so efficient as they could be.
Salary is less than you can earn with the same skills in other companies.
World conferences (e.g. IO, WWDC) are sometimes not sponsored due to low budget or non-core profile.
Was this helpful?
Yandex Interview Questions
Yandex Interview Experiences
Software Engineer
The process seemed to change around 2014, and is now more reminiscent of the one big companies use. Candidates pass through a phone screen (1 hour) and then 4 or more on-site interviews (1 hour each), depending on the number of teams the candidate i
Software Engineer
Typical interviews include exercises from HackerRank (mostly Cracking the Coding Interview) and usual questions. You can prepare by solving different problems from HackerRank or LeetCode. It's preferable to focus on arrays and strings.
Software Engineer
1 HR call, 2 standard coding DSA rounds, and a 1-hour talk with the team lead about: - My experience - Past projects' architecture (public API maintenance, microservices, etc.) - How the web works (from DNS to sockets)
Software Engineer
Moscow, RussiaJuly 1, 2015The process seemed to change around 2014, and is now more reminiscent of the one big companies use. Candidates pass through a phone screen (1 hour) and then 4 or more on-site interviews (1 hour each), depending on the number of teams the candidate i
Software Engineer
RussiaAugust 23, 2018Typical interviews include exercises from HackerRank (mostly Cracking the Coding Interview) and usual questions. You can prepare by solving different problems from HackerRank or LeetCode. It's preferable to focus on arrays and strings.
Software Engineer
Saint Petersburg, RussiaApril 14, 20251 HR call, 2 standard coding DSA rounds, and a 1-hour talk with the team lead about: - My experience - Past projects' architecture (public API maintenance, microservices, etc.) - How the web works (from DNS to sockets)
