Sub par salary, but not that bad.
If you find a good team, it might be great. You can learn from really top developers.
You can write articles and host conference talks. They hardly ever reject paying a conference, including flights and hotel.
There's an education budget, unlimited PTO, and 2 extra weeks off.
People (the higher in the ladder, the more they do) overpromise and underdeliver consistently.
You can't really trust their word.
This includes your direct manager, sadly.
Career path hardly impossible to progress following good practices.
You depend on how others see you and not on how great you do.
Worst of all, you depend on how your boss is able to defend you in front of others.
Products, as well as teams, are continuously altered, cancelled and rebuilt, leaving an uneasy feeling of volatility.
Everything's dressed up as OKR, but they're impossible to follow (as some projects last no more than two weeks online, cause of volatility).
The motto of the company is to favor equality, kindness and to reject toxicity and hatred, but some of the people working here are following quite the opposite, creating a scene where working for the goal of equality is quite ironic.
Dev public relations is arguably improvable.
Too small of a department for the workload they have.
Last but not least, your teammates might also look for the slot of your promotion (there are limited ones, only offered yearly).
Watch your back, they'll smile at you while they sharpen their knives.
A bit more honesty internally would be so great.
And gosh, the promotion system is completely rigged.
Does anybody deserve a promotion? Just give it already, don't push them to switch jobs in order to progress
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 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
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
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 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
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