Criteo·Software Engineer

Criteo Software Engineer interview experience

No offer

Medium

Negative

Ann Arbor, MIPosted Oct 2024 · Candidate report, summarized by Dataford

I started with a couple of basic phone screens, then ended up in a long in-person day that lasted about four hours.

The early parts felt fairly easy, but there were two questions that threw me off in different ways: one prompt involved solving recursively in a way that didn’t feel to me like it aligned with the situation, and another system-design question centered on building an RSS feed.

When I asked clarifying questions about what they wanted, I kept getting answers that basically told me it was obvious and that I should already know the site and the concept. It wasn’t that I couldn’t answer—it was more that the feedback loop for understanding requirements was unhelpful.

I thanked them after 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