The interview process was initiated by submitting a relatively quick exercise about an algorithm which generates numbers with certain probabilities (choise of Java or Python as language), followed by a 3-hour face to face with two different Python-focused teams, and another 3 hours f2f with CIOs. First impressions were great, as I initially thought that their approach of offering candidates a choise of language for exercices was enlightened, but reality and the practicalities came at me fast. To be fair, it's simply not possible interview Java developers with a panel of Python interviewers. They simply don't grasp the intricacies of the two languages (having used only one for the majority of their professional life), so all the pretence of "using both languages" was quickly exposed and it went downhill from there...