I was three minutes into a clip when the room changed tone: a CEO talking about hiring and crunch, and a thousand replies igniting. You could feel the thread split—defense on one side, alarm on the other. I sat back, because the way this turned into a story mattered more than the hot takes.
At the game’s launch party people were whispering about work schedules. What Joe Brammer actually said, and how it turned into a headline
I listened to the interview clip with you in mind: short, clear, and full of traps for a headline. Joe Brammer, CEO of BULKHEAD (the studio behind the new FPS WARDOGS), spoke to The Game Business Show about hiring, staff attitudes toward crunch, and how the studio runs development.
PC Gamer ran a piece that framed his comments as endorsing mandatory crunch. Brammer pushed back on X (formerly Twitter), writing that the “mandatory” line was “made up.” He added concrete details: 80% of BULKHEAD’s shares are owned by 50% of the staff, and roughly half of WARDOGS’ development ran on a four-day work week. He also announced the studio gave everyone the entire month of December off.
The difference between implication and a direct policy matters here. Words that sit ambiguously inside an interview can be read as instruction or explanation; reporters and readers both lean toward the dramatic read. If you follow PC Gamer’s piece, you’ll see how a phrase can be lifted and turned into a framing that feeds outrage faster than nuance.
Did Joe Brammer say he supports mandatory crunch?
Short answer: not in the explicit way the headline suggested. Brammer’s public reply on X stated, “No information says mandatory, they made this up.” That’s his denial. He also pointed to profit-sharing-like ownership and scheduling choices as evidence the studio doesn’t run a single, draconian rulebook for overtime.
On my feed, replies exploded into two camps: defensive allies and worried developers. Why the reaction isn’t surprising
Every timeline I track shows this pattern after a crunch story: supporters leaning on studio culture claims, critics pointing to industry history. You know the examples—CD Projekt Red, Rockstar—stories that turned into cautionary tales for developers and managers alike.
Crunch is a real pressure; I’ve watched teams become like a pressure cooker when deadlines tighten. Brammer’s defense—that a large portion of the studio holds shares and that December is entirely off—reads as an attempt to reframe BULKHEAD as more equitable and transparent than the companies that made headlines for enforced overtime.
That doesn’t erase the worry. Many studios promise better practices and still hit weeks of intense work when scope grows beyond resourcing. You should want both transparency and enforceable protections: public statements are helpful, but contract terms, overtime pay or bonuses, and explicit scheduling rules are what protect people day-to-day.
What did BULKHEAD actually say about hiring and crunch?
Brammer suggested that candidates who are categorically opposed to crunch often don’t make it in the door—an observation about hiring fit, not a job posting demanding compulsory overtime. He clarified that a large share of the company is employee-owned and highlighted a four-day work rhythm for much of development, plus the month-long break in December.
At my last GDC panel a dev asked whether transparency helps or hurts studios. Here’s the practical fallout
Transparency can be a lighthouse in fog when it’s honest; it becomes a target when it’s incomplete. BULKHEAD’s public posture—open interviews, staff equity—gives them credibility, but the moment a phrase gets stretched, that credibility is tested.
Platforms and outlets matter here. PC Gamer, The Game Business Show, X, Steam community posts, and developer forums all amplify snippets. A single ambiguous line in an interview will be quoted, reshared, and packaged with a headline that favors conflict. That’s the way attention economics work in gaming media right now.
If you care about how teams actually work, watch for these signals: share ownership, overtime policies, explicit pay for extra hours, and a history of honoring time-off promises. BULKHEAD’s public month off and the claim of broad staff ownership tick several of those boxes, but they don’t replace clear contracts or union-style protections advocated by groups like Game Workers Unite.
Will BULKHEAD developers get paid for crunch?
Brammer didn’t outline a specific bonus scheme in that interview. He said staff “will be rewarded accordingly,” which is a promise rather than a proof point. For you—if you’re evaluating a studio—that’s the moment to ask: how are overtime and exceptional delivery compensated in writing? Ask for examples from past projects or HR policies showing overtime pay, bonus structures, or time-off-in-lieu.
I’ll say this plainly: words on X and interviews matter, but so do contracts and payroll records. Studios like BULKHEAD can offer novel approaches—employee shares, four-day weeks, a December month off—and those can shift incentives away from exploitative crunch. At worst, ambiguous phrasing invites distrust; at best, the studio’s structure could model a different way to build games.
PC Gamer and The Game Business Show are part of this ecosystem; they surface statements, sometimes in ways that favor a sharp headline. You should read the original interview when possible, track the CEO’s replies, and watch how company policies translate into pay and schedule practices at scale. Unity and Unreal are the engines; Steam and Epic are the marketplaces; but people’s working lives are defined by contracts and culture, not storefronts.
I want BULKHEAD to be an example that shifts expectations for the industry. I also want you to ask the hard questions when a headline feels too tidy. Do you think a CEO’s clarification and a declared month off are enough to move the needle on crunch, or is this still a PR bandage on a systemic problem?