Bulkhead CEO Joe Brammer has made an unusually direct case for a studio culture built around periodic crunch: the Wardogs developer expects intense work at certain points, tries to make that expectation clear before hiring, and believes employees who cannot accept it are not a fit for the company.
That position is not simply a claim that long hours are unavoidable. Brammer’s comments describe a specific bargain as he sees it: a team may push hard for months, then ease back without punishment; some employees receive bonuses and company shares for their contribution; and outside pressure to accelerate the console edition of Wardogs will not override the need to give the team breathing room. Bulkhead says the console release remains set for 2028.
It is a frank philosophy, but it also leaves difficult questions. The central issue is not whether developers care about their work—Brammer plainly wants people who do—but whether compensation, delayed milestones and permission to “tap out” can make an employment model that openly relies on crunch equitable for every employee affected by it.
What Bulkhead means by balance
Crunch is the industry term generally used for a sustained period of unusually intense work, often connected to looming releases, major updates or other deadlines. The supplied account does not specify individual schedules, total hours, overtime arrangements or how frequently these periods occur at Bulkhead. What it does establish is that Brammer does not present the traditional, steady workweek as his preferred model for Wardogs’ development.
Instead, he describes balance over a longer cycle. Wardogs had, by his account, taken precedence over much of the team’s family time during the preceding three months. Bulkhead’s responsibility afterward, he argues, is to let that equation reverse: staff should be able to slow down or stop pushing without worrying that doing so puts their job at risk.
That is an important distinction in the company’s stated approach. A recovery period is different from saying a team will never be asked for an extraordinary push. Brammer is explicitly not making the latter promise. The studio’s message is that crunch may happen, it should not be concealed from recruits, and people need an avenue to say they have reached their limit.
“This is a place you come to work hard,” Brammer said, while also arguing that employees should be able to say they are tapping out without fearing dismissal.
On its face, the decision not to move Wardogs’ console version forward is the clearest practical example of that boundary. Brammer said there is pressure for an earlier console launch, but Bulkhead will not ask the team to push further to meet it. The announced target remains 2028.
Related coverage includes Wardogs Studio CEO Defends Crunch Policy, Says Bulkhead Hires for a 'Work Hard' Culture.
That does not erase the preceding high-pressure period. It does show that a release window can function as a labor decision, not merely a marketing or platform decision. When a studio declines to accelerate a project, it is choosing not to turn demand into another immediate workload escalation. For players waiting on consoles, that means patience. For the development team, the stated intent is time to decelerate after an intense stretch.
An openly selective hiring philosophy
The sharper part of Brammer’s position concerns hiring. He said Bulkhead avoids bringing in people who are publicly opposed to crunch in the games industry, because he expects that disagreement to signal a poor match with the studio’s operating culture.
There is a meaningful difference between informing a candidate that a role can involve crunch and treating opposition to crunch as a disqualifying trait. The former gives applicants information to assess the job. The latter makes willingness to accept the model part of the studio’s filter. Bulkhead’s stance is therefore more than an acknowledgement that deadline pressure exists; it is a declaration that the company is deliberately assembling a team comfortable with it.
Brammer’s own language recognizes the split that can follow. He suggested that people invested in the work and its outcomes will feel valued, while people who are not may experience the environment as exploitative. That contrast is revealing because it places a lot of weight on personal identification with the project. A worker may care deeply about a game and still have limits imposed by health, childcare, relationships or simple exhaustion. Commitment and capacity are not the same thing.
For prospective developers, the practical implication is straightforward: the work culture is not being framed as a surprise. Candidates should understand that “work hard” here includes the possibility of concentrated, demanding periods. They should also ask concrete questions rather than relying on broad labels. How long has the current push lasted? Who decides when it ends? What does “tapping out” look like in practice? Does the recovery time apply to everyone, including staff whose tasks arrive late in a production cycle? The available information does not answer those questions, but they matter more than a slogan.
Bonuses and equity: recognition, but not a universal guarantee
Bulkhead’s justification also includes financial incentives. Brammer said the company offers a meaningful level of bonuses and shares to selected staff, describing the potential return as life-changing. His argument is simple: if a company acknowledges that crunch happens, it should also ensure that those who work especially hard receive something in return.
Equity means an ownership interest in a company. A bonus is a payment in addition to regular wages. Both can be meaningful forms of recognition, but they do different things and can be distributed differently. In this case, the important limitation is already clear: not every Bulkhead employee is eligible for the bonus-and-shares arrangement described by Brammer.
That caveat is crucial when evaluating the policy. A reward structure aimed at select employees may incentivize exceptional effort, but it does not automatically compensate every person whose work supports a crunch period. The source material does not identify the eligibility rules, the size of any payments or grants, the roles covered, or whether people who opt out of an intensive stretch can still participate. Without those details, it is not possible to determine how broadly the rewards are shared.
Nor should strong commercial performance be treated as proof that compensation is fair. Wardogs reportedly sold 2 million copies in under a week and sits near the top of Steam’s most-played chart. Those are substantial signs of early market momentum. They may make bonuses or equity more valuable for eligible recipients, but sales numbers alone do not reveal what any individual employee received, who qualified, or how that return compares with the burden of the work.
For readers interested in the player side of how games are made and experienced, it is worth separating commercial success from production conditions. A popular game can be admired for its design and still prompt valid questions about the labor structure behind it. Likewise, criticism of crunch is not criticism of the people who made the game or of players who enjoy it. That distinction is useful in every gaming conversation, including more player-focused discussions such as choosing which GameCube Metroid Prime to start with.
Family time is where the policy becomes most tangible
Brammer linked the difficulty of crunch to an aging team and employees starting families. He described a change in Bulkhead’s paternity policy that is notable both for its intent and its result. The studio initially offered 10 weeks of paternity leave, then moved to two weeks plus half-days after concluding that employees’ partners were struggling with the return-to-work transition.
The information provided does not spell out the details of those half-days: how long they continue, whether they are paid, or how they interact with project demands. It also does not explain why shortening a leave from 10 weeks to two weeks was viewed as the appropriate response to the problem described. That makes it difficult to assess the policy’s real effect on families.
Still, the comments underscore a tension in Bulkhead’s broader argument. Brammer frames the ability to pull back after a push as a protection for workers with family responsibilities. Yet he also acknowledges that Wardogs had recently displaced family life for a substantial period. Recovery time may help, but it is not interchangeable with time that was already unavailable during an intense phase. A policy can recognize the need for rest while leaving unresolved whether the preceding workload was sustainable.
Why the 2028 console date matters
Wardogs’ strong early sales and Steam presence will likely increase interest in a console release. Brammer says that interest will not pull the date forward. For Bulkhead, that decision is being presented as the point at which its stated balance becomes measurable: the company is declining to extract more work from a team that has already been under pressure.
It also puts a clear expectation in front of players. Wardogs is planned for consoles in 2028, not on an accelerated schedule. There is no supplied evidence of specific console platforms, technical features, ports in development, or a more precise release date, so those details should not be assumed.
Technically, a console launch is not just a button press after a PC release, but the available information offers no specifics about Bulkhead’s work or the reasons for the timeline. The significant fact here is the management choice, not an unverified explanation of the development process. Bulkhead is saying the team will not be pushed harder simply because demand exists.
The claim Bulkhead will now have to live up to
Brammer’s comments are unusually clear in one respect: Bulkhead is not trying to market itself as a studio where crunch can never happen. It is instead asking employees and candidates to accept a culture of intense periods, with compensation for some workers, a supposed ability to step back, and later recovery built into the deal.
That clarity has value. People can judge the offer with their eyes open rather than discovering the expectation after joining. But transparency is not the same as resolution. The durability of Bulkhead’s argument will depend on the parts that remain unspecified: whether staff can genuinely refuse additional pressure without career consequences, whether rest is available when it is needed rather than only when a project permits it, and whether the financial upside reaches everyone materially affected by the workload.
Wardogs’ early success gives Bulkhead a chance to demonstrate that its version of balance has substance. Holding the console release to 2028 is the first visible test. The harder test is whether the studio can make intense work periods genuinely exceptional, give people meaningful power to set limits, and ensure that the rewards it describes are not limited to a fortunate few.
