Good financial compensation Work-life balance programmes
Somewhat hectic environment Poor internal communication
A clear, transparent, reasonable and collaborative road-map for a stable team with clear boundaries goes a long way towards feeling ownership towards one's work and preventing disillusionment.
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
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