Nice people, pleasant atmosphere, nice office, good lunch, great work-life balance, good salary (compared to most other Dutch companies).
For back-end developers, Booking.com has absolutely nothing to offer. The quality of code is just horrific, and building on top of a house of cards is the norm.
OO? Tests? TDD? DDD? Any design at all? Forget about it.
2000-line Perl functions with 1000-line if-else statements are perfectly normal and not even frowned upon, even by principal engineers. Perl is still the language you will work in (despite what they say in interviews), and Perl is simply unfit for building quality back-end systems.
There are a few teams doing cool stuff, but you have to wait 8-20 (!) months before you can pick a team you like.
Run away from this company if you want to learn anything useful as a back-end developer. You'll be a worse programmer when you come out compared to when you came in. Do join, though, if you want to go back 15 years in time.
Stop relocating talented back-end developers and wasting their intelligence. It's just morally wrong.
The interview process will begin with an HR call, followed by a technician interview, then a team call, and finally a manager call. HR will reach out to you. If selected for the role, these interviews will follow.
The technical test was challenging. It included two multiple-choice questions and two longer questions. The phone call was good; the person calling was really nice. They asked about my experience. I am now trying to prepare for the in-person assess
1. The first round was a coding round with a third party where they asked a dynamic programming question. This wasn't an elimination round, though. 2. The second round was a coding round where they had their own problem statement. It wasn't very dif
The interview process will begin with an HR call, followed by a technician interview, then a team call, and finally a manager call. HR will reach out to you. If selected for the role, these interviews will follow.
The technical test was challenging. It included two multiple-choice questions and two longer questions. The phone call was good; the person calling was really nice. They asked about my experience. I am now trying to prepare for the in-person assess
1. The first round was a coding round with a third party where they asked a dynamic programming question. This wasn't an elimination round, though. 2. The second round was a coding round where they had their own problem statement. It wasn't very dif