There are mountains and oceans of data and challenges, along with lots of very smart people.
Your experience depends very much on which group you'll be and under what team leader. While there are excellent group heads and good and decent team leaders who are also a genuine pleasure to work with, they are not the norm nor the median. More often than not, you'll face a very competitive and at times hostile environment.
In addition, there is a huge mess in code management and versioning. The same goes for the database, which can be changed during the night without any prior notice. All your code will fail, and you'll spend the day finding out who moved your training data and to where.
Many times, entry-level engineers will be left to their own devices with little oversight and later fired for "lack of results" (not my case) - just because there are "a ton" of possible replacements outside the door.
Abrupt decisions and multiple project switching are abundant, and basically there is no atmosphere of collaboration between teams and groups.
Basically, the company leans more towards inner competitiveness and secretiveness rather than collaboration and knowledge sharing.
Two technical interviews, I was summoned to their office for the interview, the process wasn't well organized and the results weren't communicated well. At the end we parted ways, the interview had emphasis on fundamental understanding of probability
Interviewer was pleasant and helpful. Interview was about 2.5 hours long. First part was usual "getting to know you" type stuff, and I was asked to talk about a project I had done. The rest was 3 technical questions in ascending order of complexity.
First interview on site. Second interview homework. On site I was asked about how to estimate a line from point, they wanted algebric solution and statistical solution. Homework was composed of 2 questions, one is a classic LeetCode question. Secon
Two technical interviews, I was summoned to their office for the interview, the process wasn't well organized and the results weren't communicated well. At the end we parted ways, the interview had emphasis on fundamental understanding of probability
Interviewer was pleasant and helpful. Interview was about 2.5 hours long. First part was usual "getting to know you" type stuff, and I was asked to talk about a project I had done. The rest was 3 technical questions in ascending order of complexity.
First interview on site. Second interview homework. On site I was asked about how to estimate a line from point, they wanted algebric solution and statistical solution. Homework was composed of 2 questions, one is a classic LeetCode question. Secon