Why Technical Gameplay Design?
What Drives My Work
Game design is a wide field, but I don’t just want to do anything. The areas I’ve found myself most passionate about—and most skilled in—are:
Combat Design – crafting responsive, meaningful systems that make every encounter feel alive.
Narrative Integration – weaving story into gameplay so that mechanics and emotion work hand-in-hand.
Tooling – building the systems, editors, and workflows that empower not only myself but the entire team.
These three pillars overlap in a space I think of as Technical Gameplay.
What “Technical Gameplay” Means
Technical: Because my work often extends beyond pure design. I create tools, improve workflows, and develop capabilities that didn’t exist before—whether that’s a bespoke branching dialogue system, custom spline-based movement, or lightweight importers to speed up iteration.
Gameplay: Because I’m always focused on the player’s experience first. Systems and tools only matter if they serve gameplay. My goal is to cultivate memorable, innovative, and engaging experiences that keep players invested.
Why the Change Now?
The shift to calling myself a Technical Gameplay Designer comes down to visibility and alignment.
Yes, I can do level design, systems design, and plenty of other work. But the jobs I actively seek out—and the ones I’m best suited for—are those in combat and gameplay design, with a technical edge.
So when someone clicks into my site, I want it to be immediately clear: