Update — 1 October 2026: recruitment pages closed
Blizzard Careers pages for the 15 StarCraft roles referenced in a 29 September recruitment push returned a “job has been filled” notice when checked on 1 October. Some syndicated and employer-feed listings still showed the same requisitions as active or recent.
That discrepancy establishes the state of the application pages, not 15 confirmed hires, hiring dates or a production milestone. The earlier role descriptions below remain historical evidence of development work; they should not be read as a list of current vacancies.
Blizzplanet’s 29 September report preserved the reported Blizzard Facebook push and the requisition links; the original social post was not directly captured. First-party application pages included Player Systems, R028142.
Old Blizzard job listings make the new StarCraft much easier to picture
Blizzard has already described its new StarCraft as a third-person, story-driven open-world shooter. A set of older job listings now gives us a better idea of what that could actually look like.
Dedicated boss encounters. Cinematic story missions. Mission designs that can include puzzles. Bespoke enemy behaviours. Large-scale environment production. And a world Blizzard once described as "large and content rich", containing "interesting missions and challenges."
Those details come from vacancies that originally belonged only to an "Unannounced Project".
Several of the same jobs have now been relabelled StarCraft while keeping their original requisition IDs, giving us a much stronger way to connect the older development descriptions to the game Blizzard has since announced.
Blizzard was already building for a large, content-rich world
The strongest example is R028070, Associate Tech Director, World Systems.
Before the reveal, Blizzard said the anonymous project needed systems capable of supporting a "large and content rich world" with "interesting missions and challenges", while helping the team create high-quality content at scale.
R028070 is now explicitly a StarCraft role.
The newer version still focuses on creating an "interesting, complex, and challenging world", although some of the more specific wording has disappeared.
That doesn't imply Blizzard has cut anything. Job descriptions change. What matters is that the unchanged requisition number now identifies the project behind the older language.
It fits closely with Blizzard's post-reveal description of the game: tightly authored story missions alongside side quests, activities, challenges and exploration, with players able to leave a difficult mission, improve elsewhere and return better prepared.
The listing doesn't tell us the size or exact structure of the map. It does show that the open world was already a substantial technical and content-production problem long before the game was publicly named.
Bosses and bespoke enemies are getting dedicated attention
R027917, Senior Boss Designer II, originally belonged to the Unannounced Project.
The role covers boss encounters, mechanics, attack patterns, behaviours and combat pacing. The same requisition is now tied to StarCraft.
Another role, R028114, focuses on enemy NPCs, bespoke behaviours, attacks, abilities, perception and encounter construction. Its current listing now identifies the StarCraft team even though parts of the old "Unannounced Game" wording remain.
Together, those roles suggest Blizzard isn't treating enemies simply as targets placed into an open map. Encounter construction and enemy behaviour have dedicated development attention.
Sourceborne hypothesis: faction asymmetry may matter at ground level
Blizzard has already said preserving the differences between Terran, Zerg and Protoss matters.
Combine that with dedicated work on enemy behaviours, abilities and perception, and one plausible direction is that each faction will require meaningfully different approaches rather than functioning as visually distinct versions of the same shooter enemies.
That's our interpretation of the development evidence, not a confirmed gameplay system.
The campaign looks broader than moving between firefights
The mission roles are just as revealing.
R028111, Senior Mission Designer, covers dialogue, mission layouts, combat, gameplay challenges and puzzles. The same requisition moved from an Unannounced Game to StarCraft.
R028116, Gameplay Engineer, Missions, describes AAA mission content and systems supporting cinematic experiences that drive storytelling and gameplay. That role is now also explicitly attached to StarCraft.
This doesn't confirm a formal puzzle system or tell us how much of the game is cinematic. It does reinforce Blizzard's description of a campaign-driven experience built around authored missions rather than simply filling an open world with interchangeable activities.
Sourceborne hypothesis: the open world may support the campaign rather than replace it
The hiring pattern points towards a structure where the wider world feeds into handcrafted missions rather than becoming the main attraction by itself.
Dedicated mission design, cinematic mission engineering, boss design and World Systems work all sit comfortably alongside Blizzard's description of players exploring, improving their position and returning to tougher authored missions.
If that reading is right, StarCraft may feel less like a campaign occasionally interrupting an open world and more like an authored campaign embedded inside one.
That distinction has not been confirmed, but the pieces increasingly fit that model.
Blizzard is using procedural tools to build the world
R027921 gives us a glimpse behind the scenes.
The technical-art role covers large-scale environment creation including terrain, vegetation, modular kits, materials and world assembly, with procedural and semi-procedural workflows using tools such as Houdini, Blueprint and PCG.
The same requisition is now attached to StarCraft.
This is evidence about how Blizzard is producing the world, not how the world behaves for the player.
It does not mean StarCraft has a procedurally generated map. These tools can help artists build and populate large authored environments much more efficiently.
Combined with the dedicated mission and encounter roles, the stronger reading is that procedural technology is helping Blizzard produce a world that still contains substantial handcrafted content.
StarCraft's scale could translate naturally into boss encounters
A dedicated Boss Designer is especially interesting in this franchise.
StarCraft has always contained creatures and machines that look manageable from an RTS camera but become enormous when imagined from the perspective of a single Marine.
Sourceborne hypothesis: familiar StarCraft units could become major encounters
An Ultralisk or Colossus can be one battlefield unit among many in an RTS. From ground level, something of that scale could support an entire encounter.
That doesn't mean either unit is confirmed as a boss, and Blizzard hasn't identified any boss characters or creatures.
But the combination of a third-person perspective, a dedicated boss-design role and StarCraft's existing sense of scale gives Blizzard an obvious opportunity to reinterpret familiar battlefield threats as much more personal encounters.
The wider pattern matters more than any single listing
One job advert is easy to overread. The collection is more informative.
Blizzard is building around:
- large-scale World Systems;
- environment-production technology;
- dedicated boss encounters;
- bespoke enemy behaviour;
- authored mission design;
- dialogue and gameplay challenges;
- possible puzzle elements;
- cinematic mission engineering.
Most of that work was already visible before Blizzard announced StarCraft. What changed after the reveal was our ability to connect those descriptions to this specific game with much greater confidence.
The listings are not a final 2030 feature sheet. Development will change, and individual responsibilities do not guarantee that every idea ships.
What they do provide is a clearer picture of Blizzard's ambition: not simply an open map with StarCraft enemies dropped into it, but a game being built around authored missions, specialised encounters and a world large enough to require its own substantial technology and production pipeline.
The next useful evidence will be public gameplay — because that is where we will finally see whether these development signals translate into the kind of StarCraft experience they currently suggest.