Criteo Software Engineer interview experience

I started with things like flood fill and parentheses balance, but what really stood out was how many follow-ups I got after each answer. As the rounds went on, the questions escalated toward harder territory—hard enough that the later items felt like they’d drift into dynamic programming in the LeetCode sense.

It was less about presenting a single neat solution and more about continuing to reason and refine as the questions evolved. I felt like I had to stay sharp the whole time, because the pace of follow-ups made it easy to lose track unless I was fully grounded in the problem.