I Reported Microsoft for Wrongful Dismissals. Then Someone Wrote a Hit Piece About Me Claiming I was in DOGE.

Last year, I was employed at Microsoft as a senior engineer. What happened to me there, and what I've since learned is happening to hundreds of others, should alarm everyone working in tech.

The Problem with Microsoft

https://substack.com/home/post/p-192472108

Microsoft has been systematically gaslighting, scapegoating, and wrongfully terminating employees while publicly claiming its layoffs are about "flattening management." Public data tells a different story: only 17% of impacted roles in Redmond were classified as managerial. The rest? Engineers and workers quietly pushed out through manufactured performance failures, denied ADA accommodations, firing of employees on family medical leave, and a culture of concealment designed to give executives plausible deniability.

I know this because it happened to me. I've also spent months collecting stories from other recently fired or laid off from Microsoft which is the primary reason for posting my story - people experiencing the same pattern of isolation, gaslighting, and retaliation and a collective recognition of the issue is now required. That reporting triggered an investigation, which is currently pending.

Shortly after, a hit piece appeared about me on Substack. It went viral.

What the hit piece actually says

The piece ties me to DOGE, Elon Musk, and an alleged insider threat to national security, based on one fact: I had registered an LLC with "Department of Government Efficiency" in the name.

Here is the full explanation, in one paragraph:

The LLC was created to organize residents (particularly in my hometown of Simi Valley, California) against illegal housing moratoriums that were blocking affordable housing development. The name, borrowing DOGE's branding, was deliberate political satire aimed at the conservative local government responsible for those moratoriums. I never intended to formally register it as a business, and when I discovered it had been filed, I was the one who proactively reported it to Microsoft HR and had it dissolved. The hit piece frames this as something that had to be uncovered. I reported it myself. I have never had any contact with DOGE and while I was sponsored for a TS/SCI w/FSP I never actually used it on any program. I have spent years publicly criticizing Elon Musk and Jordan Peterson. I advocate for Medicare for All and affordable housing. Of course, the ultimate irony is that I was wrongfully accused of DOGE membership while simultaneously reporting on the mass layoffs and wrongful firings at major tech companies.

I was also accused of “harassing Boulder PD” to distract from SA victims, having affiliations to Dr. Peterson, and even spreading rumors of “Jewish space lasers.” Here's the reality: CU Boulder has systemically been covering up rape in fraternities and I complained to CU Boulder PD about a wrongful campus exclusion order after reporting declines of mental health of students, cocaine sales near campus, and inconsistent covid restrictions - shortly before a mass shooting and riot in the city where students were found flipping police cars. When it comes to Dr. Peterson during a time of unemployment I did interview him but was critical of his ideological framing - rather than insisting on a purely cultural or psychological origin of despondency I pushed Peterson that a part of the reason that the gender roles are no longer feasible is socioeconomic precarity. The comment about “Jewish space lasers” was sarcastic.

The piece then padded this with seven-year-old social media posts, out-of-context tweets, and ideological profiling to paint a picture of someone it could attach to a villain narrative. It worked. It got 200 restacks. My response did not.

Why this matters beyond me:

This is not just about a hit piece. This is a playbook.

When someone triggers accountability for a powerful institution, the response is rarely a direct rebuttal. Instead, the person is discredited through character attacks, placed in a political box, their history stripped of context, their motivations reframed as sinister. Political polarization is a clever tool of dividing the public to avoid institutional accountability: no matter what complaint is presented - half of the population can be easily mobilized against a target. The goal is not to refute the claims. The goal is to make the messenger radioactive.

It worked on me temporarily. But the investigations are still open.

What I documented at Microsoft is real: wrongful terminations, denied disability accommodations, coordinated H-1B lobbying while conducting mass layoffs of American workers as well as visa holders, and a deliberate culture of concealment enforced through AI surveillance and performance manipulation. I have corroborating accounts from multiple former employees.

The broader picture:

Microsoft submitted $2.35 million in federal lobbying disclosures in April 2025, directed at the Department of Labor and DHS, focused on H-1B visa expansion, immediately before announcing 9,000 layoffs. From 2021 to 2024, Microsoft submitted H-1B requests at a rate of 5.17 for every one net new job created in the U.S.

This is not a labor shortage. This is wage suppression.

Meanwhile, AI tools that Microsoft sold publicly as productivity breakthroughs were, internally, producing garbled outputs on security processes they hadn't been trained on; employees were being performance-managed for failures caused by missing documentation, nonfunctional tooling, and withheld information. When I raised this, I was told to "self-unblock", which would have required violating security policy.

I was then placed on a PIP with timelines that a colleague with five or more years at Microsoft confirmed were not reasonable. I was given the option between a 45 day PIP or to take severance - then only 4 days into the 45 day period, I was wrongfully fired without severance. The stated reason for my firing was delays on a feature item, delays caused by the exact environment I've described: missing documentation, nonfunctional tooling, withheld information, and denied ADA accommodations. The firing had nothing to do with the LLC. Microsoft HR already knew about the LLC because I told them.

For the entire duration of my PIP I did not have any functional hardware that could even at minimum turn on to access repositories due to the elimination of Microsoft's on site IT department where employees are plagued with months of delays for issues like yubikey shortages and SAW failures. This is an issue that many Microsoft users are painfully aware of - the issues with Microsoft support. AI is sold as a panacea to rationalize gutting critical support staff but when there are inevitable failures as a direct result of this individuals are scapegoated.

Microsoft's own internal research shows that employees are more likely to use AI tools due to fear of judgment from other coworkers - while established peer reviewed research in the field of psychology shows psychological safety in teams promotes team success. When AI tools replace workplace coordination, unintended bottlenecks arise especially with evolving security measures that are not captured by AI models. This is particularly problematic when deployed as a replacement for teachers in classrooms or a replacement for doctors and nurses in medical settings:

What I'm asking:

I'm not asking you to take my side. I'm asking you to consider the pattern: a worker reports institutional wrongdoing, a state and/or federal investigation opens, and within months a viral hit piece appears tying that worker to the most politically toxic figures of the moment, with no meaningful evidence.

One of the Microsoft leadership principles is that you must first identify issues before you can take action.

What I’m saying here is that the largest, most wealthy corporation on the planet in history by market cap should have been able to do the bare minimum of provide their engineer functional laptops that could at minimum turn on and access repositories in a reasonable amount of time rather than resort to scapegoating and gaslighting of their engineers when bottlenecks are identified, and provide proper accommodations requested directly from a doctor.

That pattern should concern you regardless of your politics. This is no longer a matter of just “moving on” continuing to allow these violations of worker protections will only continue to embolden this misconduct from tech giants.

The investigations are ongoing, and I spoke just today with WSHRC on the case assignment. I will continue to publish what I find.

Trevor Nestor is an independent researcher and former Microsoft senior engineer. His full account of the Microsoft situation is at [The Problem with Microsoft]. The state and federal investigations referenced in this piece are active as of the date of publication.