I've interviewed for Booking.com and even the girl on the phone couldn't make their process appealing (tons of Perl; no plans to migrate to anything not perl, very few tests, very little code review, developers can push straight to production .. seems like a hell shop).
Most of your code will be deployed as an experiment, so you are more likely to throw away that code instead of refactoring it.
Developers can push to production, and are expected to be responsible for the results of that push. It works quite well.
(I used to work in the travel space, at TripAdvisor, but that was about eight years ago; no other affiliations.)
One of their mantra was indeed "we are not an IT company", which I came to understand as "we don't want to hear about how things ought to be done. We do not bow to best practices. We rely on measurements not culture".
After a few years in a big corporation where you couldn't change more than 3 lines of code without 2 code reviews and approval from 2 managers, without ever considering the customers or the final product, moving there was such a relief!
Usage of a runtime typed, interpreted language for so many loc in production was of course concerning (esp. Perl which syntax and semantic are sometime surprising), but the attitude considering of caring more about measuring and controlling every possible effect than following the best practices of the day is invaluable.
This is definitively a place I would recommend to any engineer willing to learn.
Edit: it's quite possible that I'm mixing up memories of a company other than booking.com