Good work-life balance. Work is not too stressed, flexible in working hours and work from home. Good people.
There were outdated technologies and internal tools. It is a large legacy codebase. The team was lacking in quality coding practices such as code reviews and unit tests. There were many boring maintenance tasks compared to not many interesting development tasks. There were not a lot of opportunities to learn, grow, or make an impact. The compensation could be better.
One technological interview on-site. At first with a group leader and after that with a team leader. The questions were quite easy... After this interview I had an interview with the head of the product which wanted to mainly explain about the compan
I was asked a few questions about knowledge in C about char* and char [], and in C++ about constructors and destructors and virtual functions, and then I was asked the trapping rain water question with O(1) space without the need to code it, just to
I was asked to answer one page of C pitfall questions. Afterwards I was given a C LeetCode type question. The interviewer was pleasant and encouraged me to take my time.
One technological interview on-site. At first with a group leader and after that with a team leader. The questions were quite easy... After this interview I had an interview with the head of the product which wanted to mainly explain about the compan
I was asked a few questions about knowledge in C about char* and char [], and in C++ about constructors and destructors and virtual functions, and then I was asked the trapping rain water question with O(1) space without the need to code it, just to
I was asked to answer one page of C pitfall questions. Afterwards I was given a C LeetCode type question. The interviewer was pleasant and encouraged me to take my time.