Free lunch, free drinks, snacks, and fruit. Good colleagues and a convenient location in Amsterdam.
A bunch of smart engineers collaborate together, which results in flaky and bad code. Even to have a simple feature, it needs chatting with previous coders, patience, a waste of time in vain, and luck.
They lag behind the state-of-the-art tech way too much, which, however, is not the focus of tech leads who care too much about networking. When it comes to work, tech leads would rather micromanage everything than trust people to finish their work.
Tech leads don’t have the basic domain knowledge but dictate over how one simple solution is implemented. When it comes to big decisions, they become self-defensive and afraid of making mistakes. You need to try to figure things out, even working overtime while managing your manager.
Inexperienced managers and team leads with bloated egos, arrogance, and hidden personal agendas. You often hear “I am always right” in various situations. If you stand up to them, you don’t get feedback but face consequences of revenge.
“Own your own career” doesn’t mean you have freedom to explore team-wise or tech-solution wise. It is an excuse for bad management and ignorance. In fact, no matter how senior you are, you are stuck in very junior, and most of the time below-junior, monotonous work. You cannot learn anything at work, and your passion drains away, and some colleagues even face chronic depression. It is a dog-eat-dog world.
It was lengthy and a bit disorganized, and it didn't follow the outline they give on their website, but I think that's for the best as it seemed much shorter. It began with a recruiter, then led to a live online assessment with other interviewers. I
The OA is kinda funny for a Java company. They asked two hardish HackerRank questions in a two-hour interview format. The first was simply implementing an in-memory cache (why would you do this in Java?). However, the question was so vague and did no
It starts with a HackerRank coding test as the first round, followed by an in-person interview where you have to describe your approach to solving problems and system design. The third round is system design.
It was lengthy and a bit disorganized, and it didn't follow the outline they give on their website, but I think that's for the best as it seemed much shorter. It began with a recruiter, then led to a live online assessment with other interviewers. I
The OA is kinda funny for a Java company. They asked two hardish HackerRank questions in a two-hour interview format. The first was simply implementing an in-memory cache (why would you do this in Java?). However, the question was so vague and did no
It starts with a HackerRank coding test as the first round, followed by an in-person interview where you have to describe your approach to solving problems and system design. The third round is system design.