Criteo Software Engineer candidates report a recruiter call, an online assessment or take-home, and live algorithm coding, with system design in some cases. The format and timeline vary widely from candidate to candidate.
$125K
Avg. Base Comp
$170K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates describe different paths through Criteo's Software Engineer process, so prepare for a coding core and then ask your recruiter which format applies to you. The common thread is algorithmic coding. One candidate who received an offer described easy-to-medium LeetCode-style data structures and algorithms questions, followed by a final session that combined live coding, system design and a behavioral conversation. Another, rejected after a proctored C++ assessment, was asked to explain each solution, optimize it, and discuss edge cases and complexity trade-offs.
The early stages are less consistent. One candidate had a recruiter call and a technical screen before the final session. Another began with a Spring Boot REST API home assignment about products and campaigns and then had a short phone screen, but the role was filled before the planned technical interviews. A third completed a take-home, then learned about an added live coding portion 45 minutes before presenting to two Solutions Engineers, and was asked to find common elements between two lists.
One candidate for an algorithms role counted seven stages over roughly three months, with prep topics that changed between rounds and a team-specific interview before a rejection. That is one report, not a norm, but it is a reason to ask about the schedule early.
Practice talking through a first solution and then improving it, and keep a simple array problem ready in case a live portion appears. If you get a take-home, be ready to explain your design choices. Have a clear answer to why Criteo, which came up in screening conversations.
Synthesized from 11 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Criteo process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Criteo
How would you improve Google Maps?
| Question | |
|---|---|
| Target Value Search | |
| Moving Window | |
| String Palindromes | |
| Client Solution Pushback | |
| Why Do You Want to Work With Us | |
| Statistically Significant Test | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Employee Salaries | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Top Three Salaries | |
| String Shift | |
| Top 3 Users | |
| Comments Histogram | |
| Raining in Seattle | |
| Like Tracker | |
| Random SQL Sample | |
| P-value to a Layman | |
| Weighted Keys | |
| Flight Records | |
| Largest Salary by Department | |
| First Touch Attribution | |
| Find the First Non-Repeating Character in a String | |
| Job Recommendation | |
| Minimum Change | |
| Find the Missing Number | |
| Recurring Character | |
| Scrambled Tickets |
Synthesized from candidate reports. Individual experiences may vary.
Candidates describe an opening recruiter or HR conversation. One was asked about their background and why they were interested in Criteo, and another said the recruiter explained what to expect from the remaining rounds. Prepare a short career summary and a specific reason for choosing Criteo.
Reports differ. One candidate faced a proctored 55-minute assessment with 16 questions, four requiring code, and no copy-paste or external IDEs. Another built a Spring Boot REST API for products and campaigns, and a third received a take-home they later presented. Ask which format applies and what tooling is allowed.
Candidates report easy-to-medium LeetCode-style problems. One was asked to explain the approach, optimize the solution and discuss edge cases and complexity. Another was asked to find common elements between two lists in a live portion added shortly before the interview. Practice explaining a first pass and then improving it.
One offer report describes a final session combining live coding, system design and a behavioral conversation. A candidate for an algorithms role described a system design round followed by a cultural-fit conversation. Be ready to explain architectural trade-offs aloud and give a clear story about a challenge you solved.
The algorithms-role candidate described a domain-specific team interview and a later team conversation, then a rejection after about three months. Another candidate's process ended early because the position had been filled. Ask your recruiter about the remaining stages and the expected timeline, and confirm work arrangements in writing.
