Criteo Interview Questions
& Process

It started with an HR screen, followed by a first coding round focusing on random generation (like Leetcode). Then there was a second coding round that involved finding the intersection of two lists. After that, an ML theory round covering logistic regression and deep learning optimization. Finally, an ML system design round where we discussed moderating content and post-production monitoring.

The hiring process was super smooth and organized. After I sent in the design task, there was one chat with a team member, and then a final call with the art director. The whole thing was centered on practical problem-solving for marketing design — stuff like how fast you can iterate, working with creatives that have been A/B tested, and adjusting visuals based on performance data. They weren't really into just looking at portfolios; they wanted to see clear thinking, good visual logic, and a grasp of how design helps marketing funnels. Even though I didn't get the job, the feedback they gave was helpful and polite.

The recruiter initially mentioned that the Senior Analyst position had been filled internally and offered to interview me for the regular Analyst role instead. The interview started with a question about my desired compensation, as the offered salary was lower than what was advertised. I stated a figure about 15% higher than their proposed range, which led the recruiter to try and conclude the call. I clarified that my compensation expectations were negotiable, and we proceeded to discuss the team's structure and my background. A month later, I received another meeting invitation from the same recruiter. It appeared to be set up similarly to the initial interview, prompting me to email and inquire if it was a second-round interview or if they had mistakenly sent another first-round invitation. Despite receiving no response, it turned out to be another first-round interview. The recruiter then informed me on the call that I was not a good fit because the specific SQL dialect I used wasn't compatible with Criteo's systems, as their team utilizes MySQL. Therefore, it's advisable to mention your experience with MySQL.

The interview process was really frustrating. The recruiter was bad at communicating and didn't send the coding take-home assessment for almost 48 hours after saying she would, and I had to email her to follow up. She also forgot to include necessary files, and it took her a week to send them after I pointed it out. After I was told I advanced, they called me 45 minutes before my presentation interview to say they added a surprise live coding portion. This was really difficult for me because I have anxiety and do poorly under pressure in live coding situations, especially with no warning. I was told my take-home and presentation were good, but I failed the unexpected live coding part. It felt like I did well on what I could prepare for but not on the spontaneous part.