The process started out great. I enjoyed the discussion with the recruiter and it was helpful. That was followed by the technical screen which was, IMO, amateurish. As described by someone else, it was a multiple choice python quiz. Be careful to press the right button, as the [BIG RED BUTTON] is equivalent to "I don't know". (I hit the wrong button several times by mistake.) I was actually surprised when I learned that I was going to the next steps as Python isn't my strongest language and I thought I'd flunked it for sure. The next interview with a team member was technical, uneventful and went well. The third interview was to be with a technical leader. We had a difficult time communicating over the link to meet.google.com unfortunately. The audio was terrible, video was impossible. I finally called in via telephone and we made arrangements to meet another time. (I later found with traceroute that a router upstream was dropping a significant number of packets.) About ten minutes into the time scheduled for our next meeting, I sent an email asking where he was and received an email from them saying "I had an emergency and I am not able to attend our talk. I'll will contact you shortly." I did NOT hear from them "shortly". I sent several emails over several days, finally CC'ing the recruiter. The recruiter apologized and set up the next appointment for about a week later. The time for the next appointment came and went with nobody showing up. No email this time explaining why. I sent off an email after about 15 minutes of waiting (roughly 3:15pm their time in Paris). The recruiter sent me an email the next day; apparently another "emergency" happened and the interviewer couldn't make it (or even communicate that fact). The recruiter apologized saying "We will put on hold our recruitment process as we need to improve our process here." Indeed. I did hear back from the interviewer with an apology several days later (interview on Tuesday, apology on Friday), but then suggesting that it was my fault. "..your internet connection was horrible and we weren't really able to communicate." I think the failure to communicate originated at their end.. I can certainly understand "emergencies", but not their failure to communicate -- and then to try to blame it on me? Come on.. It's a shame. It looks like an interesting company otherwise, but communication is an important part of a remote first company and it appears that they don't understand that..