Bungie QA Dev Allegedly Let Go After Profile Update Following Accusations of Leaking Destiny 2 Raid Mechanics During Desert Perpetual Epic Race

Image: Bungie via fresigfx

We’re an independent games outlet, and your support keeps us going. Follow us on Google News and set us as your preferred source.

After Destiny 2’s Desert Perpetual Epic raid race, accusations surfaced against a Bungie QA tester allegedly leaking mechanics. A recent profile update has fans speculating he may have been let go.

Destiny 2’s Desert Perpetual Epic raid race happened this past weekend, with the Contest Mode running for 48 hours. After over nine hours, Bungie confirmed that Clan Elysium had officially claimed the World First completion.

But the following day, several players who took part in the raid race accused a Bungie QA tester, known online as Bravo (brav_oh), of privately sharing Desert Perpetual mechanics with his own clan during the Epic race, and shortly after the World First completion.

Destiny 2 Veteran Player and World First Winner Drops Out of Desert Perpetual Epic Raid Race, Calls the Game "Bland" and "A Chore": "The Only Thing That Will Save This Franchise Is a New Game"
Image: Bungie

Screenshots of Discord chats and in-game text began circulating, claiming Bravo had been “coaching” mid‑Contest. None of this has been confirmed by Bungie, but it’s been a hot topic among the community in the last three days.

Destiny 2 QA Tester Allegedly Let Go After Accusations of Leaking Raid Details

The tester in question is known publicly as Bravo (Aidan, per his X profile). According to public posts earlier this year, he joined Bungie in March 2025 as a contract tester and stepped back from competing.

Posts allege that he may have given his clan, Team Parabellum, who were also competing in the Epic raid race, insight that others had to figure out the hard way.

In a series of posts, he insisted that Bravo hadn’t been in their voice chat until after Clan Elysium had already claimed World First. Fede argued that Bravo only joined about an hour later, which would technically line up with NDA rules that expire once the first clear is confirmed.

But his own wording ended up raising eyebrows, he admitted Bravo joined the voice chat after the clear, which many players pointed out was closer to 30 minutes, not an hour. What was meant as a defense instead came across to some as an accidental confirmation that Bravo had been involved, even if not during the actual race window.

“I was literally scouting for Parabellum, so I had access to all their channels and was in VC throughout the entire race, and Bravo was not there until well after the race was finished; therefore, he did not break any NDA as it only covers the race,” Fede said.

“He joined VC like an hour after [Saltagreppo] cleared, but the NDA expires the second WF is confirmed, so if playtesters want to go get 2nd, 3rd, 4th, 5th place, they can.”

Destiny 2 Desert Perpetual Epic Raid
Image: Bungie via fresigfx

Fast forward to yesterday: fans noticed that Bravo quietly removed “QA at Bungie” from his public profile on X (formerly Twitter). That small update was enough for many to believe he had been let go by the studio in the wake of the accusations.

What we do know is that Bravo was working as a contract Generalist Tester at Bungie. Contract roles in QA are usually short-term, and when the contract ends, there’s no guarantee of renewal. Whether this was just the natural end of his deal or a decision tied to the controversy is unclear.

Adding fuel to the speculation, we found a LinkedIn profile under the same name that lists a Generalist Tester contract at Bungie from March to September 2025. That matches the same timeframe Bravo first announced joining Bungie and the moment his public bio changed. While we can’t confirm with absolute certainty it’s the same person, the details line up. (We’re not publishing the full name for privacy reasons)

Bungie QA Dev Allegedly Let Go After Profile Update Following Accusations of Leaking Destiny 2 Raid Mechanics During Desert Perpetual Race
Image: LinkedIn

Bungie has not commented on any of this, nor confirmed if the person left on schedule or was removed.

What do you think? Should Bungie staff and playtesters not be allowed to participate in the raid race until after the Contest mode ends? Let us know your thoughts below.

Share This Article