I had my coding interview today for the Senior Software Engineer position at Criteo (Ann Arbor branch), and I just want to say—it was a great experience. The interview was conducted via the CoderPad platform. I was invited to a session with two very kind and professional senior engineers. The task involved reviewing a Java code snippet, identifying a couple of bugs, and implementing a missing method. The code was clean, readable, and not overly complex, which made it easy to dive into the logic. That said, I was a bit stressed going into it—this was my first time using CoderPad (I’m more used to working in IntelliJ), and the role itself means a lot to me. At the beginning, I had a bit of a mental block. But the interviewers were incredibly supportive—respectful, patient, and encouraging. Their calm demeanor really helped me settle down and get back on track. Once I got into the flow, I actually had a lot of fun. The task was engaging and did a great job of testing essential skills like debugging, understanding unfamiliar code, and applying fixes effectively. Honestly, if I had known in advance how enjoyable and fair the process would be, I wouldn’t have been nearly as nervous. To sum up: the interview team was fantastic, and the experience exceeded my expectations. If you're preparing for an interview with Criteo—stay calm and trust yourself. You’ll do just fine. Big thanks to the team at Criteo for the opportunity, and best of luck to future candidates!

Interview @ Mabaya (a Criteo company) I've interviewed at Mabaya's office on February 2023, after completing a home assignment. The home assignment itself is average. Nothing difficult and not tricks involved. Several days after submitting my solution, they asked me to come to 1.5 hours interview in which I was told I will be asked about my solution and other technical questions might be asked. First of all, the offices of Mabaya are in a common office space which for me is very small and crowded. Also, no windows there. This was the most disrespectful and annoying interview I had! Below are the reasons: 1. I was barely asked about the home assignment. 2. One of the interviewers was so interfering. Every 5 seconds he had a question. 3. Due to the above, I couldn't finish explaining things I worked on. 4. The same interviewer would jump from Java to Docker to K8s (although I am not a DevOps guy) every 5-10 seconds (not exaggerating). 5. In every question he had a sense of disrespectfulness. If it was sense of humour, then he has a really bad one. I could add more but it is enough to waste time on these guys. Before interviewing there, please consider it several times in order to avoid wasting your time.