Criteo logo

Criteo Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 111 interview experiences · FREE TO READ

3.7 Rounds average
Average Typical difficulty
69.1% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Criteo.

Showing 3 of 111
Criteo logo
Criteo

Software Engineer

Engineering · a year ago

Senior Average Positive experience No offer 1 round
Interview process
Technical screen
Interview formats
Coding Technical

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!

Confirmed questions1 question
  • One of the questions was to find a bug in an exiting method implementation (it was not working as expected).
Criteo logo
Criteo

Software Engineer

Engineering · a year ago

Mid Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Technical screen Onsite Panel Background check Offer
Interview formats
Coding Technical System Design Behavioral

The process for this Full-stack software engineer role starts with a call from talent acquisition. After that, there's a tech screen where you'll do a short live coding problem. If you're more front-end focused, you'll build a simple front-end app with whatever framework you like (or vanilla JS). For back-end, it's an algo problem (like Leet code, medium). If you pass the tech screen, you move on to two more technical interviews: a full-stack coding interview where you gotta interact with an API and process stuff to show on the web, and a system design interview which is pretty standard. The very last step is a behavioural interview with your potential manager.

Confirmed questions2 questions
  • For the tech screen, could you implement the front-end logic for Tic-tac-toe?
  • Design a chat application.
Criteo logo
Criteo

Software Engineer

Engineering · more than a year ago

Mid Average Negative experience No offer 3 rounds
Interview process
Technical screen Technical screen Technical screen
Interview formats
Technical Coding System Design

It was a bad interview experience, I can feel the interviewers didn't respect the candidate too much, and they might even laugh at your answer! First interview was Tech Screen, the interviewer will ask you questions as many as possible. Second interview was Live Coding, the interviewer will ask you finish a algo question (hard level Leetcode question) in 40 minutes, and complete all tests. He will degrade you if you can't find best solution. He will judge you impolitely! Third interview was Design, the interviewer will a question and criticize you if you make any mistake. No respect, and No seriously at all!

Confirmed questions1 question
  • Regarding this business and product, why is your knowledge limited?

Criteo Software Engineer Interview Questions

Quoted word for word from Criteo interview reports.

Implement the functionality of an old phone's SMS keyboard, where each number corresponds to multiple letters, given a constrained word list.

Read reports

Find the intersection of two given integer arrays, meaning create an array containing elements common to both.

Read reports

Could you filter a given list of words to include only those that are palindromes within the original list?

Read reports

Could you compute the maximum sum of elements in a given (non-binary) tree containing numbers?

Read reports

Could you write a function that takes two sorted lists of lengths m and n and returns a list of their combined values, sorted? Please ensure the function is optimized for O(m+n) time complexity!

Read report

For a given array of integers, can you create a new array with the average of values within a specified window size from the original array?

Read report

T9 problem: How would you implement an algorithm that returns the words corresponding to a given digit sequence and its prefixes? Time and space complexity?

Read report

How would you find an element within an array that is sorted but has been shifted?

Read report

Binary search: What's the approach to find a given element in a sorted array? And how to handle a sorted array that's been pivoted (split and rearranged)? Time and space complexity?

Read report

Formats, difficulty and experience

Across all 111 Criteo interview reports.

Interview formats

Coding 31.3%
Technical 27.2%
Behavioral 21.4%
System Design 17.6%
Presentation 1.9%

Interview difficulty

Easy 4.5%
Average 68.5%
Difficult 27%

Candidate experience

Positive 69.1%
Neutral 11.8%
Negative 19.1%