In short
Google DeepMind’s first London meeting with employees seeking union recognition quickly became contentious, with staff accusing the company of sidestepping meaningful engagement. The dispute is unfolding alongside deeper concerns about AI ethics, internal communication and military uses of the technology.
- DeepMind employees say the first union recognition meeting lacked senior leadership and felt non-serious.
- Google DeepMind says the meeting was an expected early step focused on defining representation.
- The dispute is linked to broader employee concerns over dropped ethics pledges and military AI use.
- If talks fail, organizers may seek arbitration to force formal union recognition.
Google DeepMind’s first formal meeting with London employees seeking union recognition began with friction this week, exposing a widening dispute over how one of the world’s most influential AI labs handles worker concerns, internal communication and the military uses of artificial intelligence.
The talks, which followed a request from staff in May for Google to recognize the Communication Workers Union and Unite the Union as joint representatives, were supposed to be an early step toward a negotiated process. Instead, union supporters and employees backing the campaign left the meeting feeling that the company had sent the wrong message: that the people making the case for representation were not being met by senior decision-makers, but were instead being routed through a process dominated by HR.
Google DeepMind disputes the suggestion that the process has gone off track. The company says the first meeting was only meant to establish who the unions are seeking to represent and that the right people were present for that stage. Still, the disagreement points to a larger conflict now playing out inside AI companies: as their models become more powerful and more closely tied to government and defense contracts, employees are pressing for a louder voice over the direction of the technology.
At DeepMind, the immediate dispute is about union recognition. Underneath it sits a broader argument about workplace culture, ethics, and whether staff can still challenge leadership when the company’s public values shift.
What happened in the first DeepMind meeting
The initial session took place on Wednesday in London and included union officers, DeepMind staff involved in the organizing effort, an independent arbitrator, and HR representatives from the company. According to people familiar with the meeting, the absence of senior leadership was a major source of frustration among employees supporting unionization.
Union representatives saw that absence as a sign the company was not treating the process as a serious negotiation. Google DeepMind, by contrast, says the meeting was simply the opening step in a staged procedure and that the appropriate representatives attended.
“Recognition talks not being attended by senior management at the opening stage is a leading indicator that a company isn’t engaging in good faith,” said John Chadfield, a Communication Workers Union officer who attended the session. He described the exchange as an early sign that the process could bog down.
DeepMind rejected that characterization. Al Verney, a spokesperson for the company, said the meeting’s purpose was to define the group of employees the unions want to represent and that the participants were the correct ones for that phase of the talks.
Even before the substantive issues could be aired, the meeting became a dispute over process, signaling how delicate and adversarial union recognition can be in the tech sector, where companies often maintain flatter structures and resist traditional labor frameworks.
A carefully staged process turns contentious
The London talks were not spontaneous. They were set in motion after employees asked Google in May to recognize the CWU and Unite as joint bargaining representatives. Google declined the request but agreed to enter into negotiations overseen by a third-party body.
That arrangement was meant to create a structured pathway toward recognition. Instead, employees say the first session made them feel sidelined. One DeepMind worker read aloud a prepared statement on behalf of colleagues who support unionization, and the text reportedly criticized the company’s handling of internal dissent and communication channels.
According to multiple sources with knowledge of the meeting, HR representatives interrupted the worker twice while the statement was being read. The incident added to the impression among organizers that management was focused on controlling the process rather than listening to concerns.
The employee letter, reviewed by WIRED, argued that staff had been treated less like professionals with concerns and more like a problem to be managed by HR. The statement also accused the company of narrowing opportunities for open discussion and limiting how employees could respond to internal announcements about the union drive.
For organizers, the encounter raised doubts about whether the company was prepared to bargain in a meaningful way or whether the talks were being used to slow momentum among employees.
Allegations of communication crackdowns
Beyond the room where the talks took place, the union supporters’ complaints center on how DeepMind and its parent company have handled internal communications in recent months. The letter read during the meeting alleged that Google had shut down or altered internal chat spaces and restricted employee responses to company-wide messages discussing the union campaign.
Employees who tried to work around those limits were allegedly reprimanded by HR. Supporters of the campaign describe those actions as a textbook effort to suppress organizing activity, while the company says it still provides multiple channels for employees to raise concerns and discuss their views.
An employee involved in drafting the statement, who asked not to be named because they are not authorized to speak publicly, said the aim was to create fear rather than dialogue. They described the company’s actions as familiar anti-union tactics meant to discourage open organizing.
Google DeepMind has denied that characterization. Verney said the company intends to keep engaging constructively and emphasized that employees still have access to other forums for discussion.
The dispute over communications matters because control of internal platforms has become a key pressure point in tech labor organizing. In highly distributed, digitally connected companies, messaging tools often function as the modern equivalent of notice boards, town halls and corridor conversations. When those channels are narrowed, workers can feel cut off from one another just as campaigns gather momentum.
Why the ethics changes still loom over the dispute
The labor push at DeepMind did not begin in a vacuum. Employees involved in the campaign trace part of their frustration to a major policy change earlier in 2025, when Alphabet removed a pledge from its ethics guidelines that had barred use of AI for certain harmful applications, including weapons development and surveillance.
For some staff, that change was more than a policy edit. It represented a shift in the company’s identity and in the assumptions that had drawn them to the lab in the first place.
“Those principles were a big part of why I joined DeepMind,” said one employee who asked to remain anonymous. “We basically just got rid of them all.”
That reaction reflects a wider anxiety across the AI sector, where employees increasingly worry that systems they helped build could be deployed in ways that conflict with earlier ethical commitments. At companies developing foundation models, the distance between research lab and national security contractor has narrowed dramatically in recent years, and workers have taken note.
In that environment, unionization is not only about wages or hours. At DeepMind, it is also about influence over what kind of company the lab becomes, how it responds to government customers, and whether workers can help shape policy when the stakes extend beyond ordinary commercial product development.
The military-use debate is now central to AI labor activism
DeepMind’s labor dispute is part of a broader wave of employee activism around military and surveillance applications of AI. In recent months, staff across the industry have expressed alarm about government contracts and defense partnerships that could place advanced models in sensitive operational settings.
That concern was on display in late February, when employees at DeepMind and OpenAI signed an open letter supporting Anthropic after the US Department of Defense reportedly moved to label the company a supply chain risk. The point of contention was Anthropic’s refusal to allow its technology to be used in autonomous weapons and mass surveillance.
Then, in April, reporting by The New York Times described a Google agreement that would allow the Pentagon to use its AI for “any lawful government purpose.” The terms prompted an internal backlash, with roughly 600 US-based Google employees reportedly signing a protest letter.
Later, the Defense Department confirmed that it had reached arrangements with seven major AI companies, including Google, SpaceX, OpenAI and Microsoft, to use their models on classified networks. The disclosure underscored how quickly the sector’s commercial and defense relationships are deepening.
Google has defended these arrangements. In comments reported earlier this year, the company said it was proud to be part of a broad coalition of AI and cloud providers supporting national security work, while also maintaining that AI should not be used for domestic mass surveillance or autonomous weapons without human oversight.
That position reflects the balancing act now faced by many AI companies: they want government business and the credibility that comes with it, but they also want to preserve public trust and avoid appearing indifferent to the social consequences of deployment.
Why DeepMind employees are organizing now
DeepMind has long occupied a special place in the AI ecosystem. Known for breakthrough research and a reputation for technical excellence, the lab has attracted employees who often see their work as mission-driven. That culture can make internal disputes especially fraught, because the company’s public image and its employees’ personal ethics are often intertwined.
The union drive appears to be drawing energy from that sense of mission. Workers who came to DeepMind because of its stated principles say they want a formal structure that gives them a say when those principles change. They also want a stronger mechanism for raising concerns when strategic decisions appear to move the company in a direction that staff believe is inconsistent with its values.
Union organizers in tech often argue that worker representation is not an attempt to disrupt innovation, but to create predictable channels for accountability. In a field marked by secrecy, rapid hiring, and intense competition for talent, employees may see collective bargaining as one of the few tools available to ensure that corporate strategy does not outpace ethical reflection.
That argument has particular force at AI labs, where the consequences of deployment can be hard to foresee and where internal dissent may be especially difficult to voice once government or defense relationships become involved.
How Google’s union history shapes the current fight
The DeepMind dispute also sits within Google’s longer and often complicated labor history. In the United States, Alphabet employees formed the Alphabet Workers Union in 2021. Although the union is not formally recognized for collective bargaining, it has helped workers organize and has secured agreements for contractors in some instances.
That history matters because it shows both the limits and the possibilities of labor organizing inside one of the world’s most powerful technology companies. While Alphabet has not embraced a classic union model, employees have still used collective pressure to influence some company decisions.
DeepMind’s London staff now appear to be testing whether a similar strategy can work in the UK context. If the company continues to resist recognition, organizers have indicated they may ask an arbitration committee to compel Google to recognize the unions.
Chadfield said the workers’ hope is that the company will eventually come to the table in good faith and reach a voluntary agreement. But he also argued that any real negotiation requires some willingness to compromise.
The CWU officer said the company appeared to be entering the talks without offering concessions, while employees were prepared to engage if management met them halfway. In his view, the current approach risks turning the process into a formality rather than a genuine negotiation.
What union recognition would mean for DeepMind
If successful, union recognition would likely give London-based DeepMind employees a formal voice in discussions about workplace conditions, internal processes and potentially broader policy issues affecting the lab. In practical terms, recognition would mark a significant shift in how one of AI’s marquee research organizations manages employee relations.
For management, that could mean slower decision-making and more structured consultation. For employees, it could mean leverage in disputes that otherwise might be handled privately or through informal channels. In a company where much of the work is technically complex and strategically sensitive, a recognized union could become a mechanism for turning isolated dissatisfaction into organized input.
It would also be symbolically important. DeepMind has often been seen as a bellwether for the AI industry. If workers there succeed in winning recognition, other labs may face greater pressure to follow suit, especially if their own employees are uneasy about defense contracts, surveillance-related use cases or shrinking internal transparency.
That is one reason the first meeting matters so much. A procedural stumble in London is not just a local labor issue. It is a sign of how AI companies may respond when the people building frontier systems insist on a more formal say in how those systems are governed.
A growing test for the AI industry
The tensions at DeepMind mirror a larger transition underway across the industry. AI labs are no longer simply research organizations or consumer software businesses. They are increasingly entangled with national security, public policy, infrastructure and workplace politics.
As those ties deepen, employees are asking whether the old model of benevolent leadership and internal culture suffices. Many no longer believe that ethical concerns can be resolved through company statements or ad hoc feedback channels alone. They want binding mechanisms that survive leadership changes and commercial pressure.
That shift helps explain why labor organizing has become more visible in AI than it once was in Silicon Valley at large. Workers are not just reacting to pay or hours. They are reacting to the speed at which their creations are moving into government use, and to the feeling that core ethical promises can disappear overnight.
For Google DeepMind, the question now is whether the company will treat the London talks as the start of a serious bargain or as a procedural requirement to be managed. The answer could shape both the outcome of this union drive and the tone of employee relations across the AI sector.
Key developments at a glance
| Issue | Details |
|---|---|
| Union request | DeepMind employees asked Google in May to recognize the Communication Workers Union and Unite the Union as joint representatives. |
| Company response | Google declined recognition but agreed to third-party arbitrated negotiations. |
| First meeting | Held Wednesday in London with union officials, organizing employees, an arbitrator and HR representatives. |
| Main complaint | Union supporters said senior management did not attend and that the company handled the session as a formality. |
| Company position | DeepMind said the meeting was only to define representation and that the appropriate representatives were present. |
| Broader context | Employees link the campaign to Alphabet’s removal of an ethics pledge limiting harmful AI uses. |
| Industry backdrop | AI workers are increasingly challenging military and surveillance applications of their models. |
Timeline: how the dispute escalated
| Date | Event |
|---|---|
| February 2025 | Alphabet removes a key ethics pledge restricting certain military and surveillance uses of AI. |
| Late February 2025 | DeepMind and OpenAI staff sign an open letter supporting Anthropic over its resistance to military and mass surveillance applications. |
| April 2025 | Reports emerge of a Google Pentagon agreement, sparking backlash among employees. |
| May 2025 | DeepMind workers ask Google to recognize CWU and Unite as joint representatives. |
| This week | The first arbitrated recognition meeting takes place in London and becomes a flashpoint. |
What comes next
For now, both sides say the process will continue. But the tone of the first meeting suggests the road ahead may be difficult. Union supporters are already prepared to escalate if Google does not engage more directly, while the company insists the negotiations are proceeding as designed.
Much will depend on whether the next phase addresses the core issue or remains trapped in procedural arguments. If the parties can agree on representation and set a more substantive agenda, the talks may still produce a framework both sides can live with. If not, the matter could move to arbitration and become a more public test of Google’s approach to labor rights in one of its most strategically important AI labs.
Either way, the dispute has already exposed a central tension in the AI industry: companies want to project confidence, mission and control, while employees increasingly want formal power to question where the technology is headed and who it serves.
At DeepMind, that struggle is now playing out in the language of union recognition, but the underlying question is larger. As AI systems become more embedded in government, security and everyday life, how much say will the people building them actually have?









