I like the people, the opportunities, the workplace, and the equipment. Everything from above is on point.
Old codebase without any documentation and people who know how some parts work.
Sometimes it's hard to show performance and get a salary increase because of the tasks you are assigned to. For example, an easy at first glance task can contain bugs which slow you down for months of hardcore debugging.
For me, because of the reasons I mentioned above, work-life balance is 80 to 20, which is actually sad.
- HR call - Tech call - Team lead call HR asked mostly about soft skills and previous experience. Tech lead asked questions about data structures and algorithms. Team lead shared details about the role and future responsibilities.
Several interviews (3-5) are typically conducted. Most of them focus solely on algorithms. Sometimes, if there is enough time left, they may ask about language specifics or topics related to concurrency.
The interview process is quite lengthy and can take up to two months. There are three technical sections in the interview process: * A screening interview to assess knowledge of the programming language and technical stack. * A coding interview
- HR call - Tech call - Team lead call HR asked mostly about soft skills and previous experience. Tech lead asked questions about data structures and algorithms. Team lead shared details about the role and future responsibilities.
Several interviews (3-5) are typically conducted. Most of them focus solely on algorithms. Sometimes, if there is enough time left, they may ask about language specifics or topics related to concurrency.
The interview process is quite lengthy and can take up to two months. There are three technical sections in the interview process: * A screening interview to assess knowledge of the programming language and technical stack. * A coding interview