Pinball Xperience
Rick Naegele

Rick Naegele

Biography

RICK NAEGELE

From Video Games to the Keith Elwin Era, the Programmer Behind Some of Modern Stern’s Major Rulesets

Iron Maiden: Legacy of the Beast, Jurassic Park, Avengers: Infinity Quest, Godzilla, Jaws, King Kong, and then Fallout form a remarkably coherent line through contemporary Stern Pinball. Behind Keith Elwin and the physical architectures that have profoundly shaped this period, Rick Naegele holds an essential position in transforming those playfields into complete game systems. A Lead Software Engineer who joined Stern in 2017 after a long career in video games and gaming, he worked alongside Elwin from Iron Maiden, the designer’s first commercial machine, and continued that collaboration across several of his most ambitious creations. His work directly involves ruleset implementation, software architecture, mechanical behavior, scoring, and the vast network of invisible interactions that ultimately determines what a machine allows the player to build ball after ball.

His career extends well beyond that association. Before Stern, Naegele spent nearly two decades in software development, including positions at Midway, Electronic Arts, and WMS Gaming, with extensive experience in C++, object-oriented architecture, and complex systems development. When he entered pinball, he therefore brought with him a culture formed in environments where states, events, reproducibility, and code organization were already daily concerns. Stern quickly placed him in software leadership roles on Iron Maiden, Jurassic Park, and Avengers: Infinity Quest. Godzilla and Jaws continued that trajectory, King Kong again gave him a central responsibility in code and rules, while Fallout brought him back in 2026 as part of the software team assembled around Keith Elwin’s latest project.

Profile

First Name

Rick

Last Name

Naegele

Profession

Lead Software Engineer | Pinball Programmer

Specialties

Game Software | Rules Implementation | Software Architecture | C++ | Scoring Systems

Manufacturer

Stern Pinball

Joined Stern

2017

Role

Lead Software Engineer

First Documented Machine

Iron Maiden: Legacy of the Beast

First Documented Pinball Credit

2018

Previous Experience

Video Games | Gaming

Documented Languages

C++ | C# | Java | Python

Documented Pinball Period

2018 to present

Before Stern | Midway, Electronic Arts, and WMS

Pinball arrived relatively late in Rick Naegele’s professional career. His software background had already been built over nearly two decades in video games and gaming, including positions at Midway Games, Electronic Arts, and WMS Gaming. At WMS, where he worked from 2010 to 2017 as a Principal Software Engineer, he operated in an environment where state reliability and mathematical reproducibility were fundamental. His technical background includes C++, C#, Java, Python, object-oriented architectures, design patterns, Agile methodologies, and various graphics and cross-platform technologies. This history helps explain part of his approach at Stern: Naegele did not enter pinball to learn how to program, but to apply an already extensive software development background to a physical machine in which every event now depends on the interaction between code, electronics, mechanics, and the real behavior of a ball.

2017 | Joining Stern as Software Changes Scale

Rick Naegele joined Stern Pinball in July 2017 as a Lead Software Engineer. A few months later, the company publicly introduced him while highlighting nearly twenty years of software experience. The timing was significant for Stern. SPIKE 2 was becoming established, LCD displays had replaced the DMD on new productions, rulesets were growing substantially, and the company was strengthening a team responsible for simultaneously developing future games, correcting existing titles, and supporting a catalog whose code continued to evolve after release. Naegele’s role quickly extended beyond writing individual features. His documented responsibilities include leading teams of several software engineers, implementing rulesets from designer specifications, developing technical tools, and supporting other programmers. He therefore entered Stern at a point when programming a pinball machine was increasingly becoming an exercise in collective software architecture.

Iron Maiden: Legacy of the Beast | Keith Elwin and Rick Naegele Begin Together

Iron Maiden: Legacy of the Beast became Rick Naegele’s first documented pinball credit in 2018 and Keith Elwin’s first commercial pinball design. Their association immediately became significant. Elwin brought an exceptional understanding of play and an architecture built around highly distinctive trajectories, while Naegele led the software effort, with Tim Sexton also credited in programming. Iron Maiden developed a ruleset in which Legacy of the Beast modes, Eddie Battles, Soul Shards, multiballs, and progression objectives could be approached through several routes. Its depth does not rely on simply accumulating content, but on the way different branches allow players to prepare a game and shape their scoring strategy. From this first project, the code therefore had to translate a designer’s already highly systemic thinking, where the order of decisions and interactions between objectives mattered as much as simply completing them.

Jurassic Park | Turning Survival into a Progression System

Jurassic Park pushed this approach considerably further in 2019. Naegele again served as Lead Software Engineer on a Keith Elwin machine whose ruleset creates a genuine expedition across Isla Nublar. Paddocks, dinosaurs, rescues, Chaos Multiball, the T-Rex, and different progression stages give the game an almost virtual geography layered over the physical playfield. The software must remember the player’s position within that progression, determine which objectives are available, manage the consequences of earlier decisions, and maintain sufficient clarity despite the density of the system. Jurassic Park became an excellent example of the relationship between physical and software architecture in Elwin’s work: the shots remain concrete, but their meaning changes according to where the player currently stands within the journey. For Naegele, the challenge is to make that depth function without allowing the machine to become an abstract interface disconnected from the ball.

The Munsters | Stepping Outside the Elwin Language

Between Iron Maiden and Jurassic Park, Rick Naegele also contributed to the software of The Munsters in 2019 alongside Dwight Sullivan and Waison Cheng. John Borg’s machine follows a much more immediate philosophy, with a deliberately more accessible ruleset and a structure less concerned with constructing a long strategic journey than with making its objectives quickly identifiable. Its presence in Naegele’s career is important because it demonstrates that his work at Stern is not limited to Keith Elwin. The same developer must be able to serve very different game design intentions without imposing the same software architecture on every machine. The code must remain in service of the game, whether it is organizing a deep strategic system or supporting a more direct experience.

Avengers: Infinity Quest | When Interactions Become the Heart of the Ruleset

Avengers: Infinity Quest marked one of the peaks of the first Elwin/Naegele period in 2020. Rick Naegele led the software effort with a team that included Raymond Davidson, Brett Z Rubin, and Mike Kyzivat around a ruleset in which Infinity Gems, Gem Quests, Avengers, multipliers, and stacking possibilities create considerable strategic density. A successful game is no longer simply about advancing through several parallel objectives. The player prepares resources, chooses when to use them, and searches for intersections capable of multiplying the value of a sequence. For the software, this design multiplies dependencies: every system must remain aware of the state of others without generating contradictory behavior when they intersect. Avengers demonstrates how closely modern pinball programming has moved toward complex systems architecture. Much of the elegance of the final result depends on something the player never directly sees, the code’s ability to maintain dozens of simultaneous states coherently.

Godzilla | Making Code Communicate with a Playfield That Changes Shape

Godzilla pushed the relationship even further in 2021. Naegele contributed to the software alongside Brett Z Rubin, Corey Stup, Dean Grover, and Mike Kyzivat on a machine where deep rules meet an especially ambitious mechanical architecture. On the Premium and Limited Edition models, the motorized building physically descends into the playfield, changes certain trajectories, and becomes directly involved in Godzilla Multiball, while the destructible bridge adds another physical transformation. The code cannot merely know that an objective is active: it must track the actual state of moving mechanisms and coordinate their behavior with lighting, sound, display content, rules, and scoring. Layered over that mechanical complexity is an enormous progression structure built around cities, Kaiju Battles, allies, multiballs, and the objectives required to reach Planet X and ultimately King of the Monsters. Godzilla crystallizes much of the work developed since Iron Maiden: software depth is not separated from the playfield, it changes the meaning of its trajectories according to the state of the game.

Jaws | A Collaboration Reaching Maturity

Jaws returned in 2024 to a production structure that had become familiar around Keith Elwin, with Harrison Drake handling mechanical engineering, Rick Naegele serving as Lead Software Engineer, Jerry Thompson on sound design, and Elizabeth Gieske also contributing to software. After the almost sprawling density of Godzilla, Jaws presents a more contained initial reading but gradually builds its depth around sharks, beaches, hunts, multiballs, and a progression structure that turns the game into a pursuit. The software must support a machine whose effectiveness relies heavily on pacing and its ability to increase tension without constantly interrupting the player. The shark, the boat, and the different game states need to respond coherently to what is physically happening on the playfield. Several years after Iron Maiden, the Elwin/Naegele collaboration is no longer an early experiment: it rests on an accumulated understanding of how architecture, rules, and code can be developed together.

King Kong: Myth of Terror Island | Code and Rules Move to the Foreground

King Kong: Myth of Terror Island continued this association in 2025 and placed Rick Naegele at the center of software development alongside Josh Henderson. Keith Elwin’s machine uses a highly active physical architecture with four flippers, hidden trajectories, a spiral ramp, and an animatronic Kong directly integrated into gameplay sequences. The software must orchestrate those mechanics while supporting progression built around the exploration of Terror Island and its various encounters. Naegele contributes to both code and rules here, making the proximity between implementation and game structure particularly visible. After several collaborations with Elwin, his work is no longer simply a matter of translating a list of behaviors into software: the game system and its technical implementation advance through a much closer dialogue.

Fallout | Reuniting with Elwin in the SPIKE 3 Era

In 2026, Rick Naegele joined Andrew Wilkening, Brett Z Rubin, and Raymond Davidson on the software team for Fallout, Keith Elwin’s new machine developed on SPIKE 3. The project brings together several figures associated with major Elwin productions while placing them within a renewed technological environment. Fallout draws directly from the language of RPGs, using the Pip-Boy, S.P.E.C.I.A.L. stats, characters, exploration, and different forms of progression integrated into the structure of a game. For the software, the challenge is to preserve that richness without shifting the experience toward constant display reading. Information has to live through machine feedback, the playfield, lighting, callouts, and audiovisual sequences so that progression remains understandable during active play. Eight years after Iron Maiden, Naegele therefore reunites with Elwin on a machine that almost naturally measures the distance traveled: the foundations remain those of physical pinball, but the number of systems the software must now coordinate has moved to an entirely different scale.

Building the Code Before Building the Modes

Rick Naegele’s work is not limited to programming a succession of modes, multiballs, and jackpots. His professional experience documents a broader responsibility for development architecture: leading teams of three to six software engineers, mentoring, creating software for test fixtures, and implementing complete rulesets in C++. This dimension becomes essential on modern machines whose development can continue for years. A feature added late in the process must be able to communicate with dozens of existing systems without destabilizing the whole. Poor architecture early in development gradually turns every new rule into a potential regression. The role of a Lead Software Engineer therefore also involves building an environment in which complexity can continue to grow without making the game impossible to maintain.

Keith Elwin | A Defining Collaboration

The repeated collaborations between Rick Naegele and Keith Elwin form one of the defining threads of modern Stern. Iron Maiden, Jurassic Park, Avengers: Infinity Quest, Godzilla, Jaws, King Kong, and Fallout cover almost the entirety of Elwin’s career with the manufacturer and reveal a steady increase in complexity. The early games establish an already deep strategic approach, Avengers radically increases the density of interactions, Godzilla connects that architecture to spectacular mechanical transformations, Jaws explores a more focused form of progression, King Kong returns to an especially elaborate physical architecture, and Fallout introduces a structure informed by RPG systems. Naegele accompanies that evolution through software. His role should not be confused with that of the game designer: Elwin designs the machine and carries its gameplay vision. But that vision only becomes a playable experience once translated into states, conditions, priorities, scoring, and behaviors capable of functioning together during a real game.

The Programmer Facing the Player

A machine can contain thousands of lines of perfectly functional code and still produce an unbalanced, confusing, or flat ruleset. Pinball programming therefore cannot be reduced to making requested features work. Software must respect the hierarchy of objectives, allow strategies to coexist, provide the player with sufficiently clear information, and remain coherent when several systems are active simultaneously. The machines Naegele has worked on make this challenge especially visible because they often encourage preparation, stacking, and score construction across several stages. Avengers can reward a combination prepared far in advance, Jurassic Park transforms previous decisions into progression states, Godzilla allows extraordinarily powerful stacks, and King Kong continues this tradition of interconnected systems. Code becomes the invisible infrastructure of strategy.

Major Machines and Credits

Year

Machine

Manufacturer

Documented Role

2018

Iron Maiden: Legacy of the Beast

Stern Pinball

Lead Software Engineer | Software

2019

The Munsters

Stern Pinball

Software

2019

Jurassic Park

Stern Pinball

Lead Software Engineer

2020

Avengers: Infinity Quest

Stern Pinball

Lead Software Engineer

2021

Godzilla

Stern Pinball

Software

2024

Godzilla 70th Anniversary Edition

Stern Pinball

Software

2024

Jaws

Stern Pinball

Lead Software Engineer

2025

King Kong: Myth of Terror Island

Stern Pinball

Software | Rules

2026

Fallout

Stern Pinball

Software

Skills & Roles

Lead Software Engineering | Pinball Programming | Rules Implementation | C++ | Software Architecture | Scoring Systems | Team Leadership | Software Testing | Development Tools | Mentoring

Rick Naegele works at a level where programming and development organization are closely connected. His earlier career gave him extensive experience with complex software architectures before he ever entered pinball, while Stern placed him in positions involving team leadership, complete ruleset implementation, and the creation of tools supporting production and testing. That combination becomes especially important when machines continue receiving content after release: the code must not only work today, but remain structured enough to accept the systems that will be added tomorrow.

Highlights

A substantial part of Keith Elwin’s body of work at Stern can also be read through Rick Naegele’s software career. Iron Maiden begins their collaboration with a machine that immediately establishes a strong strategic dimension. Jurassic Park transforms progression into a structured journey. Avengers: Infinity Quest pushes preparation and interaction to exceptional levels of density. Godzilla connects that depth to a playfield capable of physically changing state. Jaws refines the relationship between progression and pacing, King Kong continues the exploration of complex systems, and Fallout carries the collaboration into the SPIKE 3 environment with an architecture informed by the language of RPGs.

Naegele brings to that history an experience that long predates his entry into pinball. Midway, Electronic Arts, and WMS gave him a software development background well before Stern, and the manufacturer subsequently placed him in charge of teams and machines where complexity could no longer be managed as a simple succession of independent functions. His work lives within the layer that players almost never see but constantly experience through its consequences: the way a machine remembers, cross-references, prioritizes, and transforms its events into gameplay.

From Iron Maiden in 2018 through Fallout in 2026, Rick Naegele has accompanied one of the periods in which software became increasingly central to the identity of Stern pinball itself. The playfield provides the trajectories and the ball provides the uncertainty. Between them, his code builds the system that gives both meaning.

Highlights

  • Lead Software Engineering
  • Pinball Programming
  • Rules Implementation
  • C++
  • Software Architecture
  • Scoring Systems
  • Team Leadership
  • Software Testing
  • Development Tools
  • Mentoring

Key dates

  1. Joins WMS Gaming as a Principal Software Engineer.

  2. Joins Stern Pinball as a Lead Software Engineer.

  3. Iron Maiden: Legacy of the Beast becomes his first documented pinball credit and begins his long collaboration with Keith Elwin.

  4. Leads software development on Jurassic Park.

  5. Leads the software effort on Avengers: Infinity Quest.

  6. Contributes to the software of Godzilla.

  7. Reunites with Keith Elwin as Lead Software Engineer on Jaws.

  8. Works with Josh Henderson on the code and rules for King Kong: Myth of Terror Island.

  9. Joins Andrew Wilkening, Brett Z Rubin, and Raymond Davidson on the software team for Fallout.

Associated machines

8 machines