DECK 13 Interactive GmbH has been building worlds since 2001. Based in Frankfurt am Main, this studio has earned a reputation for ambitious, technically demanding games that push hardware and storytelling in equal measure. The Principal Game Programmer (f/m/x) role sits at the very top of the individual contributor track, and understanding what daily life looks like in that seat matters before you apply.
Who DECK 13 Interactive GmbH Is
DECK 13 started as a small Frankfurt studio with big ambitions. Over two decades, it grew into a team of roughly 100 professionals known for titles like Lords of the Fallen, The Surge series, and Atlas Fallen. These are not casual projects. Each one demanded serious engineering work across PC and console platforms.
The studio is now part of the PulluP Entertainment group, which brought additional resources and publishing support. That backing has not diluted the studio's creative identity. DECK 13 still operates as a focused, independent-minded team within a larger structure.
Frankfurt itself is a major European city with a strong tech and finance sector. The location means access to a diverse international talent pool, which shows up in the studio's makeup. The team describes itself as a diverse, passionate community of creators, and that language reflects how the studio positions its culture publicly.
The Culture Inside the Studio
Game studios built around action RPGs tend to attract people who care deeply about craft. DECK 13 is no exception. The studio's public messaging emphasizes collaboration, mentorship, and technical excellence rather than crunch culture or rapid release cycles.
The Principal Game Programmer role itself reveals something about the culture. Mentoring is described as a core, formal part of the role, not an optional extra. Studios that treat mentorship as a structural responsibility usually have flatter ego cultures where knowledge-sharing is valued over individual credit.
The studio believes, in their own words, that the best games are still ahead of them. That forward-looking mindset shapes how teams approach their work. Engineers are expected to prototype new tools, evaluate workflows, and actively improve how the team operates, not just execute tasks assigned from above.
The Work Environment Day to Day
The Frankfurt am Main office is the home base for this role. Working in a 100-person studio means you know most colleagues by name. Decisions move faster than at larger publishers, and individual contributions are more visible. That visibility cuts both ways. Strong work gets noticed quickly, and so do gaps.
The engineering team works primarily with Unreal Engine, which is the industry's dominant AAA game engine. For a Principal programmer, this means deep work inside complex engine systems, not surface-level blueprint scripting. Expect to spend time in low-level engine code, optimization pipelines, and cross-system architecture discussions.
The role also requires direct collaboration with the Technical Director. That relationship is central to how technical strategy gets set. As the most senior individual contributor, the Principal Programmer serves as the Technical Director's closest technical partner on execution and architecture.
Team Structure and Your Place in It
DECK 13's programming team has a clear hierarchy, and the Principal Game Programmer sits at the top of the individual contributor side. Below this role are senior programmers, mid-level programmers, and junior programmers, all of whom the Principal is formally expected to mentor.
The structure means this is not a purely heads-down coding job. A significant portion of the role involves:
- Conducting code reviews and pairing sessions with programmers at all levels
- Running technical interviews as part of the hiring process
- Writing and maintaining documentation for complex systems
- Unblocking engineers who hit hard technical walls
- Contributing to onboarding new team members
This is a role for someone who genuinely wants to make other engineers better, not someone looking to escape people interaction through individual excellence alone.
The Technical Challenges You Will Own
The job posting is direct about what hard work looks like here. The Principal Programmer owns the most technically demanding work on the team. That includes deep optimization, large-scale cross-system refactors, and the highest-risk areas of the codebase.
Driving architecture decisions across major systems is a core expectation. This means understanding not just how to write excellent C++ but how systems interact at scale, how changes ripple across a large codebase, and how to sequence refactors without destabilizing active development.
The role also involves identifying and prototyping new tools and workflows. DECK 13 wants someone who looks at the team's current processes and asks how they can be improved, then does the work to validate those improvements through prototypes.
What the Required Experience Looks Like
The minimum bar is 10 or more years of professional game development experience. That number matters. This is not an aspirational title for a fast-rising mid-career engineer. The studio expects someone who has already shipped multiple games, navigated real production crises, and built systems that survived years of iteration.
Key technical requirements include:
- Expert-level C++ with deep knowledge of programming principles
- Experience with system design and large-scale architecture
- Proven work inside Unreal Engine at a deep, engine-level capacity
- Demonstrated ability to lead technical decisions across a team
- A track record of mentoring and developing other engineers
Candidates who check these boxes are rare. DECK 13 knows that, which is why the role carries the weight of the studio's most complex technical ownership.
Growth Opportunities at DECK 13
Growth at the Principal level looks different than it does earlier in a career. The upward path from here typically leads toward Technical Director or CTO-level roles. At DECK 13, the proximity to the Technical Director means that trajectory is realistic for someone who performs well and develops leadership instincts over time.
The PulluP Entertainment group structure also creates lateral growth possibilities. A senior technical mind with a strong track record at DECK 13 has visibility across the broader group, which opens doors that a purely standalone studio could not offer.
For engineers who want to stay deep in technical work rather than move into management, the Principal role itself is the destination. Studios like DECK 13 increasingly recognize that keeping elite engineers in technical seats, rather than pushing them into management they may not want, produces better outcomes for everyone.
Work-Life Balance at a 100-Person Studio
DECK 13 does not publish explicit policies about overtime or crunch in this job posting. That is common across the industry. However, the studio's size and structure offer some signals worth reading carefully.
A 100-person studio with a long institutional history and publisher backing tends to operate with more stability than a scrappy startup racing toward a first release. The formalized mentorship expectations and documentation requirements suggest a team that plans carefully rather than sprinting chaotically.
Frankfurt's labor laws also matter. Germany has some of Europe's strongest employee protections, including limits on working hours and strong cultural norms around separating work from personal life. Working in Germany as an employee provides a legal framework that many other game development markets do not offer.
If sustainable engineering work in a technically ambitious studio matters to you, DECK 13's Frankfurt base and its structured team culture suggest a more considered environment than the industry average. Experienced candidates who want to do serious work without burning out will find the setting worth exploring. You can apply for the Principal Game Programmer (f/m/x) position directly at this link.
