Over my three years in the company, there have been a lot of changes in leadership and management. Two different chiefs of HR, two CEOs, and three or possibly four product chiefs have come and gone. Each new leader brings new ideas which typically results in big changes every year or so, accompanied by a payout for their predecessor.
Unfortunately, we recently lost 30% of our workforce, and the previous CEO received a large bonus despite this loss. The company is lacking a clear product direction, and priorities seem to change every 3-6 months. There is currently no growth path, and evaluations have been pushed down in order to avoid raises and promotions. To make matters worse, all the great benefits we had when I first joined are slowly being removed or reduced.
The way layoffs were conducted were completely random, people with a lot of responsibilities were let go on day one without a proper strategy. "Tricky questions" are silenced during all-hands to try to raise morale.
The ship is sinking.
It is important to stop changing leadership every six months and instead, stick to a well-defined strategy that encompasses all aspects of the organization including product, engineering, marketing, and human resources.
Stop trying to increase morale with fake smiles during all-hands, give us raises.
Very old-fashioned interview process. There was a theoretical and a practical part. In the theoretical there were boring questions about equals/hashCode and sealed classes. The stack they are using is very old (no compose/coroutines), they use RxJava
First a recruiter gets in touch with you to talk about the role and the company and you introduce yourself and talk a bit about your professional experience. Then there are 2 technical interviews where the first is just 1 or 2 random Android questio
First talk to a recruiter, on a relaxed conversation, and then they will schedule a technical interview with 2 engineers. They get into a set of platform questions, and then an algorithmic exercise
Very old-fashioned interview process. There was a theoretical and a practical part. In the theoretical there were boring questions about equals/hashCode and sealed classes. The stack they are using is very old (no compose/coroutines), they use RxJava
First a recruiter gets in touch with you to talk about the role and the company and you introduce yourself and talk a bit about your professional experience. Then there are 2 technical interviews where the first is just 1 or 2 random Android questio
First talk to a recruiter, on a relaxed conversation, and then they will schedule a technical interview with 2 engineers. They get into a set of platform questions, and then an algorithmic exercise