About
I build the systems behind interactive products.
Hands-on engineering, system architecture and product ownership across games, XR, multiplayer, mobile and real-time 3D.
- 10+
- Years in game and real-time engineering
- Unity + Unreal
- Core production engines
- Engineering + Product
- Hands-on technical leadership
- Games / XR / Real-Time 3D
- Primary product domain
How I operate
- System implementation
- Gameplay engineering
- Runtime debugging
- Profiling
- Integration
- Technical problem solving
- Production code
Staying close enough to implementation that architecture decisions stay grounded in what production actually does.
- System design
- Modular architecture
- Technical boundaries
- Data and runtime flow
- Reusability
- Maintainability
- Production pipelines
Structuring systems so they stay understandable, extensible and practical for the team building on top of them.
- Technical prioritization
- Scope
- Delivery risk
- Product tradeoffs
- Cross-discipline decisions
- Release readiness
- Team enablement
Engineering decisions have to serve the product, the production constraints and the people responsible for shipping it.
The strongest technical work happens where implementation, architecture and product judgement meet.
Working principles
01
Own the system
Understand the complete technical path instead of treating every feature as an isolated implementation task.
02
Stay hands-on
Leadership does not replace engineering. The decisions that matter stay connected to implementation, debugging, profiling and production constraints.
03
Design for production
Maintainability, iteration speed, tooling, performance and release reliability matter alongside finishing the feature.
04
Connect disciplines
Engineering decisions should work for design, art, backend and product, and for whoever maintains the system after delivery.
Where I work best
A range of responsibility rather than a rating. Most projects have needed several of these at once.
- Complex products where engineering decisions reach gameplay, architecture, production pipelines, platform constraints and delivery at the same time.
- Teams where technical leadership stays close to implementation.
- Products that need systems to survive iteration, not just work once.
- Cross-disciplinary environments where engineering has to communicate clearly with design, art, backend and product.
I have spent most of my career moving between implementation, architecture and product responsibility rather than treating them as separate disciplines. I still like getting close to the actual system, understanding why it behaves the way it does, and turning that into something the wider team can build on.