Ubisoft's June 10 Cut Was 380. The Real Bench Is 170 Reassigned Montrealers.
Ubisoft's June 10, 2026 restructuring closed two studios and cut 380 roles. The bigger sourcing opportunity is 170 reassigned Montreal developers. Here's how to find them.
Every layoff tracker you read this week is counting the same 380 jobs: Winnipeg closed, Belgrade closed, 51 gone at Barcelona, dozens off the XDefiant team in San Francisco. Those names will hit LinkedIn's #OpenToWork filter by Monday and your inbox by Friday. The interesting pool is the one no tracker is counting: roughly 170 Ubisoft Montreal developers who were quietly ramped off Rainbow Six Siege and Rainbow Six Mobile on June 10 and put on internal reassignment with no announced next project.
They are not laid off. They are not on the public lists. They are also not shipping anything. If you source games talent, that is the most addressable cohort in the market right now, and the window is measured in weeks.
What actually happened on June 10
Per Insider Gaming's reporting on Ubisoft's internal messaging, the June 10 restructuring had two layers. The public layer: Ubisoft Winnipeg shut down (around 65 jobs), Ubisoft Belgrade shut down (~100), Barcelona lost 51 roles and narrowed its remit to Rainbow Six only, and dozens more were cut across San Francisco and Global Publishing. Pending consultation, the total could reach 380 eliminated roles.
The internal layer is what trackers missed. At Ubisoft Montreal, at least 120 developers, roughly 12% of the Rainbow Six Siege team, were ramped off the project. Another ~50 were moved off Rainbow Six Siege Mobile and an unannounced project. Ubisoft's own statement: "Rainbow Six Siege remains a strong brand. As projects move through different stages of development and live operations, it is normal practice to adjust team size and resource allocation based on evolving priorities and operational needs."
Translated: 170 developers in a single city, on a single franchise, in a single day, with no announced destination.
Why "reassigned" is the highest-signal state in games sourcing
Recruiters default to two buckets: happily employed (hard to move) and laid off (everyone is chasing them). "Reassigned" is the third bucket, and it is structurally underpriced.
A reassigned developer is still on payroll, so they will not appear on Layoffs.fyi, will not flip #OpenToWork, and will not show up in the layoff-tracker scrapes your competitors are running this morning. They will also not show up in their own inbound applications, because they technically still have a job. But they are unbilled, demotivated, and rationally aware that on a €1.3 billion operating loss with a stated target to cut fixed costs to €1.25 billion by March 2028, "reassigned" is a waiting room.
Reassigned is the waiting room between a project and a RIF, and right now Ubisoft has 170 people sitting in it in one city.
The math is unambiguous. Ubisoft confirmed on May 20 a record €1.3 billion operating loss for FY2025-26 on revenue that fell 21.8% year over year to €1.4 billion. Management has acknowledged FY2026-27 will be another loss-making year. The precedent is clear: Red Storm Entertainment lost 105 employees in March and was demoted to a support studio. "Reassigned today, laid off in 90 days" is not a worst case, it is the base case.
The window is short and visible right now
Here is the specific friction. Today, a reassigned R6 Siege programmer's LinkedIn headline still reads something like "Senior Gameplay Programmer, Rainbow Six Siege at Ubisoft Montreal." Their pinned project is Siege. Their recent activity references the live ops cadence. That is the signal you can query against.
Once Ubisoft assigns them to a new internal project, even an unannounced one, two things change. The headline updates to something generic ("Senior Gameplay Programmer at Ubisoft Montreal"). The project history gets reshuffled. The signal collapses into the background noise of the 4,000-plus Ubisoft employees in the Montreal metro. Insider Gaming's reporting window opened on June 10. You have maybe four to eight weeks before the public signal degrades.
This is exactly the kind of query that breaks Boolean strings. You do not want everyone at Ubisoft Montreal. You do not want everyone who has ever touched Rainbow Six. You want people currently listing Siege or Siege Mobile in their current role, based in Quebec, with three-plus years on the franchise, who have not yet updated their headline. That is a four-clause intent, not a keyword search, which is why we built Refolk: you describe the person in plain English and get a ranked shortlist across GitHub, LinkedIn, and the open web. Ubisoft Montreal Rainbow Six developers, currently employed, with Anvil or Snowdrop experience, is a sentence, not a regex.
The Winnipeg 65 are the cohort no one is chasing
If the Montreal 170 are the underpriced passive pool, the Winnipeg 65 are the underpriced active pool. Most game recruiters this week will fixate on Belgrade because the headcount is larger (~100) and the talent is generalist. That is a mistake.
Ubisoft Winnipeg was opened in January 2019 with a $264 million CAD investment from the Province of Manitoba and a stated workforce target of 300 employees by 2030. It closed at 65. The reason that matters for sourcing: Winnipeg was primarily tasked with developing Ubisoft's proprietary Anvil and Snowdrop engines, used on Rainbow Six Siege and Immortals Fenyx Rising among others. The closure shed engine and tools engineers, which is a categorically rarer skill than gameplay programming.
Anvil Snowdrop engine engineers translate cleanly into any proprietary-engine shop (Riot, Activision, EA's Frostbite teams) and into senior tools roles at Unreal Engine 5 studios. The Belgrade generalist pool will be picked over by every studio in EMEA by next Tuesday. The Winnipeg engine specialists are a quieter list, and the right query is "ex-Winnipeg, engine or tools, Anvil or Snowdrop in project history," which again is not a Boolean search, it is an intent.
Actually one correction on that stat block format. Let me restate plainly: the Winnipeg studio was promised $264M CAD and a 300-headcount future. It closed at 65. That gap is the recruitment pitch you make to every one of those engineers this month.
Read the Vantage / Tencent boundary as a sourcing map
The structural detail most game sourcers will miss: Rainbow Six falls within Vantage Studios, the Ubisoft subsidiary that completed a €1.16 billion investment from Tencent in November 2025, with Tencent holding 26.32% economic interest. Winnipeg, Belgrade, and parts of Global Publishing sat outside the Tencent-protected umbrella. That is why those studios absorbed the public cut.
Inside Vantage, the protection is at the franchise level, not the project level. Rainbow Six the brand is safe. Rainbow Six Mobile, an unannounced spinoff, or the live-ops team that just lost 12% of its headcount is not. The next reorg lands on whichever "unannounced project" absorbed the 50 reassigned Mobile devs. If you are mapping where the next wave of reassignments will hit, follow the non-flagship projects inside Vantage, not the studios outside it.
Surviving Rainbow Six capacity is also consolidating in Barcelona, not Montreal. A Ubisoft Paris programmer, Mataoui Chakib Souleyman, publicly posted on LinkedIn that the 51 Barcelona cuts represent 28% of that studio's workforce, with the survivors now focused exclusively on Rainbow Six. If Ubisoft relocates any of the Montreal 170 internally, Barcelona is the likely destination, and a relocation offer to Spain from Quebec is the moment a passive candidate becomes an active one.
The embargo is itself a signal
One small detail from the Insider Gaming reporting that recruiters should take seriously: the June 10 news came with a 1 PM ET / 6 PM BST embargo, the kind of timing usually reserved for product reviews and game announcements, not people's livelihoods. Ubisoft tried to control the narrative window. The downstream effect is that affected developers, particularly the reassigned cohort who were not even publicly named, had less time than usual to prep a job search. Resumes are not updated. LinkedIn headlines are still pre-June-10. GitHub bios still reference live projects.
That is why outbound this week outperforms inbound next month. The reassigned 170 are not yet looking. By the time they are looking, their headlines will have changed, the layoff-tracker pool will have flooded the market with cheaper signal, and the arbitrage will be gone.
A concrete sourcing playbook for the next 30 days
Three cohorts, three different queries.
The Montreal 170. Currently employed, Rainbow Six Siege or Mobile in current role, Quebec metro, three-plus years of franchise tenure. Outreach angle: not "we heard you were laid off" (they weren't) but "we heard the project moved." Lead with the specific game and the specific role.
The Winnipeg 65. Engine and tools focus, Anvil or Snowdrop in project history, Manitoba metro or willing to relocate. Outreach angle: senior tools or engine roles, not gameplay. Move fast; the proprietary-engine shops will close on this list by quarter-end.
The Barcelona 51 and Belgrade ~100. Higher volume, more contested. Worth filtering rather than blasting. The Barcelona survivors who stayed on Rainbow Six are arguably a more interesting pool than the ones who left, because they are now on a single-franchise studio that just lost 28% of its peers.
For all three, the operational problem is the same: writing the query in plain English and getting back a ranked shortlist across GitHub project history, LinkedIn employment, and the open web (Mastodon, personal sites, GDC speaker pages, Bluesky game-dev posts). Refolk handles the cross-source join so the reassigned developer who hasn't updated LinkedIn but did commit to a public engine repo last week still surfaces.
Refolk's own index already shows the shape of the problem. A direct search for public profiles in Canada explicitly mentioning "Ubisoft Rainbow Six Siege" returns roughly 32 people, heavily concentrated at Ubisoft Montreal (14) and broader Ubisoft (8), almost all in the Montreal metro. That is the visible tip. The reassigned 170 are mostly not in those 32 yet, because most senior developers list the studio, not the project, in their headline. The query you actually want is "people whose recent commits, talks, or work history put them on Siege, regardless of current headline," and that is the kind of intent search that turns a 32-person Boolean result into the 170-person reality.
FAQ
How is "reassigned" different from "laid off" for sourcing purposes?
Reassigned developers are still on payroll, which means they will not appear on layoff trackers, in #OpenToWork floods, or in inbound applications. They are also not shipping anything productive, which makes them more receptive to outbound than fully employed peers. The catch is they are harder to find: their LinkedIn headlines still reflect the old project, no public list of names exists, and you have to query against project history and current employment together. The upside is far less competition than chasing the public 380.
How long is the sourcing window before these profiles update?
Realistically four to eight weeks from June 10. Once Ubisoft assigns reassigned developers to a new internal project, even an unannounced one, headlines and current-project fields update and the signal degrades into general "Ubisoft Montreal employee" noise. The Winnipeg and Belgrade closure pools will hit the public market within days. The Montreal reassignment pool is the one that requires acting now and quietly.
Why are the Winnipeg engine engineers more valuable than the Belgrade headcount?
Belgrade was a larger, more generalist studio, so the 100-plus headcount skews toward gameplay and production roles that every game recruiter knows how to place. Winnipeg's 65 included a disproportionate share of engineers working on Ubisoft's proprietary Anvil and Snowdrop engines, used on Rainbow Six Siege and Immortals Fenyx Rising. Engine and tools specialists translate directly into Unreal Engine 5 senior roles and into proprietary-engine shops like Riot and Activision, and the talent pool for that skill set is an order of magnitude smaller than for gameplay programming.
What outreach message actually works for a reassigned developer who hasn't admitted they're on the bench?
Do not lead with the layoff or the reassignment. Lead with the specific game, the specific system they worked on, and a concrete role that uses that experience. "I saw you spent four years on Siege live ops and shipped Operation [X]" lands very differently from "saw the news at Ubisoft." The reassigned cohort has not internalized that they are on the market yet, so the message that works is one that respects their current employment while making the next role feel like a continuation, not a rescue.