Me postulé a través de un reclutador. El proceso tomó 1 semana. Acudí a una entrevista en Avito (San Petersburgo, ) en oct 2021
Entrevista
Everything was smooth and very professional, it was very similar to the Yandex interview but easier. And I didn't really like the HR.
It consisted out of 2 coding interviews, 1 systems design. After that was 1 final interview where I met my possible future team lead.
Preguntas de entrevista [2]
Pregunta 1
I don't remember all the coding questions from coding interviews, but these i do remember:
1. Tell me about multiple data structures, sort algorithms time and space complexities
2. We have a map of dependencies, print dependencies in such way that it is printed if it's dependencies are resolved
// deps = { "mylib": ["tensorflow", "linux"],
// "tensorflow": ["cuda", "nvcc"],
// "cuda": ["linux"],
// "linux": ["core"],
// "mylib2": ["linux"] }
//
// out: core linux mylib2 cuda nvcc tensorflow mylib
Systems design interview:
Design avito.ru: a website that has a list of ads (every user shares the same one), users can register and upload ads if they are registered
Me postulé a través de un reclutador. El proceso tomó 2 semanas. Acudí a una entrevista en Avito
Entrevista
There were several steps: - Short HR interview (30 min) - Live coding interview with several algorithmic problems (1 hour) - System design interview (1 hour) The live coding wasn't so difficult. There were no compilers or autotest, so it was just like writing code in a notepad, the interviewees were kind and attentive. The system design was harder for me but I didn't have that much experience. I didn't pass it but got valuable feedback.
Preguntas de entrevista [1]
Pregunta 1
The main task of the system design section was to design Twitter-killer architecture.
Me postulé a través de una recomendación de un empleado. El proceso tomó 2 semanas. Acudí a una entrevista en Avito en feb 2023
Entrevista
Firstly, and most importantly (in my opinion at least) - BOTH tasks were solved, and in about half the time (the remaining time I optimized the algorithm of the first task + discussed O-notation, corner cases and work in Avito in general ). Moreover, the guys in their feedback clearly talk about this themselves, I quote: "The tasks were solved optimally" Secondly, we discussed those corner cases that I didn’t think about at the beginning, I myself found the problem and fixed it myself. In my opinion, this is a completely working situation. And I have never encountered in interviews that the candidate did not have "the right to make a mistake." Especially in a situation where we do not use an IDE, we cannot run and debug the code Thirdly, both interviewers were extremely tense and unfriendly during all the interviews. One of them had his camera turned off throughout our interview. Communication for me personally was the most uncomfortable. Fourthly, it is extremely strange for me to hear about some "gaps" while one of the interviewers is a BE developer, and the second one tells me that there is no break construct in JS 🤷♂️ The only thing I'm 100% ready to admit is the gap in memory evaluation in terms of O-notation. BUT: 1) I called the estimate by TIME immediately and accurately 2) I still eventually correctly determined the complexity (not immediately, but nevertheless)
