Criteo·Software Engineer

Criteo Software Engineer interview experience

No offer

Hard

Positive

FrancePosted Dec 2024 · Candidate report, summarized by Dataford

I went through a fairly traditional set of stages: a quick first conversation with HR, then a technical sequence that included an algorithm test focused on optimization rather than just solving.

After that, I moved into deeper architecture discussions and analysis, where the conversation went beyond surface-level design.

The technical parts were hard in the way that makes beginners struggle, especially when they wanted optimization depth. The process was fully remote, and the interviewers themselves were good at keeping the conversation moving.

Even though I didn’t get an offer, I felt the exercises were legitimate and structured, and the hardest part for me was the optimization angle where time matters and the target is more than correctness. Looking back, I appreciated that the

Create a free Dataford account to unlock the full round-by-round breakdown, the questions asked and the outcome.

Read the full report Read the full report

Preparing for this interview?

Criteo Software Engineer interview guideThe full process, round by round, with the question bank Practice Software Engineer interview questionsReal questions from this role across companies All Criteo interview guidesEvery role we cover at this company