Wardogs CEO Defends Crunch During Early Access Push, Sparking Debate Over Studio Culture

Wardogs CEO Joe Brammer has offered an unvarnished defense of crunch at Bulkhead, the studio behind the early access FPS, arguing that periods of extended work can be necessary when a game's launch is directly connected to the jobs of the people making it. His remarks arrive amid the games industry's long-running and frequently divisive discussion about overtime, employee wellbeing, hiring standards, and what studios owe the people who work through the most intense phases of development.

In comments to Edge, Brammer described a studio culture that puts a high value on expertise, personal commitment to the genre, and the willingness to work late when the team believes a release requires it. He said Bulkhead's staff do not enjoy the late hours, but acknowledged that the studio does crunch. His argument was not that work should always outrank private life; instead, he drew a distinction between normal circumstances and the period immediately before a release that he believes is essential to keeping the team employed.

That framing will likely be the focal point of the response to Brammer's position. The idea that a launch can determine the future of a studio is familiar to anyone who has followed game development, particularly in an era of closures, layoffs, cancelled projects, and intense pressure on teams to prove that a new game can find an audience. But workers and labor advocates have often challenged the notion that an emergency surrounding a launch makes sustained overtime unavoidable, arguing that crunch can reflect inadequate planning, shifting goals, understaffing, or leadership decisions made much earlier in production.

A blunt case for late work at critical moments

Brammer's comments leave little ambiguity about his view. He said there are times when personal life should take precedence, but maintained that work can become the higher priority when a game is nearing release and the outcome affects everyone's employment. In his view, a team approaching that moment has a shared responsibility to do what is needed to get the project over the line.

For useful background on this topic, read Dragon Age's Defining Moments, From Origins to The Veilguard.

The CEO also made clear that he is skeptical of objections to overtime from highly paid developers. Referring to developers earning $100,000 who do not want to work additional hours, Brammer dismissed that stance in especially forceful language. He contrasted game development pay with the workload he saw from his mother, who worked as a teacher and headteacher. Brammer said he had watched her put in substantial extra work for comparatively little money, and presented that experience as part of the reason he has little patience for complaints about crunch from well-compensated staff.

It is an argument rooted in relative sacrifice: if people in other professions regularly work beyond their nominal hours without comparable pay, then developers on higher salaries should sometimes be prepared to do the same. Yet that comparison is also likely to draw criticism. Long hours in education are widely discussed as a problem rather than a standard to emulate, and the fact that one profession has normalized unpaid or excessive work does not settle whether another should do so. For many critics of crunch, the relevant question is not whether other workers have it worse, but whether a studio can avoid building a business around preventable periods of extreme pressure.

Recruitment philosophy is part of the same message

Brammer connected his stance on overtime to Bulkhead's wider view of hiring. He said the studio favors a talent-driven approach and does not agree with the idea that everybody should be able to secure a job in games. In his telling, the industry previously placed greater emphasis on proven capability before opening its doors more broadly. He believes those "floodgates" have since begun to close and that applicants should be expected to demonstrate that they are exceptionally capable.

One detail of Bulkhead's recruitment process illustrates how narrowly the studio defines fit for its projects. Brammer has previously said the team checks applicants' Steam accounts to see whether they appear to have a genuine enthusiasm for FPS games. The practice is intended to identify people who are not merely qualified on paper, but who have spent time with the genre and understand its appeal from a player's perspective.

For a studio making a competitive shooter, that emphasis has an understandable logic. Familiarity with the games a team is trying to improve upon can inform everything from weapon feel and map flow to progression systems, balance concerns, and the everyday frustrations players notice quickly. At the same time, hiring practices based partly on visible personal game libraries raise broader questions about how studios distinguish passion from professionalism, and whether narrow definitions of genre enthusiasm could exclude skilled candidates with valuable experience in adjacent areas.

Brammer's comments suggest that Bulkhead sees high standards, genre dedication, and willingness to contribute during difficult periods as interlocking expectations. The team the studio wants is not simply one with technical credentials. It is one prepared to take responsibility for a game at the point when the stakes are highest.

Why crunch remains one of gaming's most contentious issues

Crunch is a loaded term because it can describe very different experiences. A short, voluntary push near a milestone is not the same thing as months of mandatory late nights, weekend work, and escalating exhaustion. Studios may use similar language about a temporary final effort while workers experience very different levels of agency, compensation, and health impact. That makes broad statements about whether crunch is "necessary" difficult to evaluate without details about its duration, frequency, expectations, and the support available to employees.

Supporters of Brammer's position may see it as a straightforward recognition of the reality facing smaller and independent teams. Games can be delayed, market conditions can change, and a project that fails to arrive in a viable state may put an entire company at risk. From that perspective, asking a group of people to rally around a decisive moment can be seen as a practical, even collective, response to uncertainty.

Opponents are likely to point out that employment insecurity can make purportedly voluntary overtime hard to refuse. If employees believe that saying no may harm their reputation, affect future opportunities, or jeopardize colleagues' jobs, the line between shared commitment and coercion can become blurred. The person asking for extra hours also matters: when that request comes from leadership, workers may not feel equally free to decide that their health, family obligations, or personal limits must come first.

Neither side of the debate is likely to find much common ground in Brammer's deliberately confrontational phrasing. Still, the comments surface a genuine tension in modern game development. Studios are asked to ship ambitious work reliably, teams want sustainable careers, and players increasingly expect fast updates and polished launches. A leadership philosophy that treats extreme effort as an occasional necessity can resonate with people who have lived through make-or-break projects. It can also alarm those who believe the industry has spent too long treating burnout as proof of dedication.

Bulkhead's break follows Wardogs' early access success

The Wardogs team is not planning to remain in an all-hands launch posture indefinitely. Brammer has told players that Bulkhead intends to take a month-long break in December following the game's early access success. In his typically direct style, he encouraged fans to spend that time playing GTA 6, saying the developers need an opportunity to "detox." He also stressed that players should understand the team will be unavailable for that month.

That planned break adds an important wrinkle to the crunch discussion. It does not erase concerns people may have about extended hours before early access, but it indicates that Bulkhead is pairing its intense launch push with a defined period away from the game. Whether a post-launch pause is enough will depend on individual perspectives and on what the preceding workload looked like in practice. But the decision recognizes that teams need recovery after a major development milestone.

For Wardogs players, the near-term message is simple: expectations for immediate activity should be tempered while the developers step back. The break also means that community feedback, balance requests, and demands for new features may not receive instant responses during that period.

Loadouts are coming, but weapon experimentation remains the goal

Brammer has also confirmed that Wardogs will receive loadouts. However, he said the developers want players to continue experimenting with different weapons rather than locking themselves into a single favored setup. That goal points toward an approach to progression and playstyle flexibility that gives players more structure without necessarily encouraging one permanent, dominant build.

Loadouts can be a major quality-of-life feature in an FPS, allowing players to prepare options for different maps, modes, ranges, and team needs. The challenge for developers is ensuring the system expands tactical choice rather than narrowing it. If one configuration becomes clearly superior, experimentation can disappear quickly. Bulkhead's stated desire to keep players rotating through weapons suggests it is aware of that risk.

Wardogs' early access period will therefore involve two parallel tests. The game itself will be shaped by player behavior, feedback, and upcoming systems such as loadouts. Meanwhile, Bulkhead's unusually candid public discussion of work culture will continue to invite scrutiny. Brammer has made his position clear: he believes exceptional circumstances can demand exceptional effort. The industry-wide question is whether that reality can be managed without turning the pressure of a major release into an accepted cost of making games.