The team is diverse and accepting. Colleagues are genuine and generally good people. Work-life balance is good, as the workload is not too high.
Direction may not always be clear from management.
This isn’t really on the Waterloo office, as these decisions come from other teams in Germany, US, or India, but you might experience some team restructuring and product shuffling/deprecation.
The interview was held on-site. Nothing too technical was asked. The interviewer asked a few data structure related questions, but did not actually request coding. They focused heavily on questions about the projects I had completed and the past e
Easy/medium LeetCode problems. The interview process was smooth. The focus is more on how you approach the problem rather than a specific language. There were a total of 3 rounds: * Two coding rounds * One managerial round
It was good. I was asked OOP in depth. I had two rounds of technical interviews before rejection. As I was working on a Java-based project, I was asked Java in depth.
The interview was held on-site. Nothing too technical was asked. The interviewer asked a few data structure related questions, but did not actually request coding. They focused heavily on questions about the projects I had completed and the past e
Easy/medium LeetCode problems. The interview process was smooth. The focus is more on how you approach the problem rather than a specific language. There were a total of 3 rounds: * Two coding rounds * One managerial round
It was good. I was asked OOP in depth. I had two rounds of technical interviews before rejection. As I was working on a Java-based project, I was asked Java in depth.