Four Software Engineer candidates describe a Ubisoft process that varies by team: an HR or recruiter contact, a technical stage such as a quiz, test or game-style assignment, then team interviews.
$115K
Avg. Base Comp
$130K
Avg. Total Comp
Not reported
Typical Rounds
3-4 weeks
Process Length
Ubisoft's Software Engineer interviews don't follow a single script, so the useful question is which technical stage your team has chosen. Across four candidate reports, the common thread is HR or recruiter contact, a technical stage, and then a conversation with the team, but the middle step changes from report to report.
Two candidates describe hands-on work. One built a small C++ mini game over a couple of days and then walked developers through the code, where questions turned to memory management, including how malloc works. Another extended an existing game engine in which a character moved randomly on screen, and said the assignment alone took about two weeks. A third candidate described a technical test in the easy-to-medium, LeetCode range, with some unexpected 3D math. The fourth mentioned a warm HR coordinator and then a team round covering OOP, their IT background and the state of gaming.
The third candidate's later rounds leaned on explaining your thinking: a manager asked about scalability, authentication versus authorization and CI/CD, and a senior developer wanted a top-down walkthrough of past projects with a defense of the technical choices. The two candidates who gave a total duration reported about three and four weeks. Outcomes were one offer, one offer declined and two with no offer. Some mention unclear timelines or little feedback, so ask the recruiter about deadlines and next steps early.
Synthesized from 9 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 Ubisoft 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 Ubisoft
How do you calculate weekly active paying users (WAPU) by joining gameplay and purchase activity by week?
| Question | |
|---|---|
| Video Game Respawn Model | |
| 2nd Highest Salary | |
| Integer to Roman | |
| P-value to a Layman | |
| Google Maps Improvement | |
| Nearest Common Ancestor | |
| Groups of Anagrams | |
| Hurdles In Data Projects | |
| Centralized Event Ingestion | |
| Tower of Hanoi | |
| Valid Anagram | |
| Find Duplicate Numbers in a List | |
| Spam Classifier | |
| Customer Success vs. Free Trial | |
| Rider Discount | |
| Matrix Rotation | |
| KNN From Scratch | |
| Subscription Retention | |
| Concurrent LLM Serving | |
| Worker Distribution Dilemma | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| User Event Data Pipeline | |
| Moving Window | |
| Confidence Interval Explanation | |
| Loan Model | |
| Cloud-Agnostic Deployments | |
| Deciding Between Solutions | |
| Drink Production Allocation | |
| International e-Commerce Warehouse |
Synthesized from candidate reports. Individual experiences may vary.
Three of the four candidates describe an early HR or recruiter conversation. One was asked what REST APIs are and what pipelines they had worked with, another described it as logistics and culture fit, and a third found the HR coordinator warm before waiting about two weeks for the next round. The fourth applied through the website and went straight to an online quiz.
One candidate took an online quiz on general programming and C++ topics, including when to use references versus pointers. Another took a technical assessment in the easy-to-medium range, similar to LeetCode, that included some 3D math questions. Flexibility was noted too: that candidate said interviewers were open to hearing their reasoning when they got stuck.
Two candidates report project work. One built a small C++ mini game over a couple of days, then presented it in a code review with developers. The other added features to an existing game engine where a character moved randomly on screen, and spent about two weeks on it. Scope and deadlines clearly vary, so ask the recruiter what is expected before you start.
Team conversations covered different ground. One candidate was asked about C++ memory management and malloc in a code review. Another met a manager on scalability, authentication versus authorization and CI/CD, then a senior developer who asked for a top-down walkthrough of past projects. A third had a shorter technical interview on their stack and motivation, and another faced OOP and background questions from the hiring team.
Two candidates describe a closing conversation. One had a straightforward HR interview after the technical rounds, and another had a full hour with the team lead and someone from HR that went deep on background and experience. Candidates note that follow-up could be slow or unclear, so confirm timelines and next steps with your recruiter.
