Expertise
Engineering interactive systems from runtime to release
Game engineering across gameplay, architecture, multiplayer, XR, mobile, production systems and real-time 3D.
- 150M+
- Cumulative Ferro portfolio downloads
- 10+
- Years in game and real-time development
- Unity + Unreal
- Core production engines
- Gameplay to platform
- Full product engineering scope
Build
Connect
Scale
Ship
Lead
Build
Gameplay Systems
Design and implement the runtime systems a game is actually made of: gameplay architecture, movement, progression, abilities and the game-state logic that holds them together.
Core technology
- Unity
- C#
- Unreal Engine
- C++
- Blueprints
Systems and responsibilities
- Gameplay architecture
- Movement and controls
- Ability systems
- Progression
- Game modes
- Game-state logic
- Runtime systems
Evidence
- Ferro Entertainment
- Darkstar Games
- ZHouse Studios
- Relymer Studio
Connect
Scale
Ship
Lead
Gameplay Systems capability selected
Technology index
Tools in service of the capabilities above. Hover or focus an entry to see which capabilities use it.
Engines
Languages
Multiplayer / Online
Backend / Data
XR
Web / Real-Time 3D
Production
Design / Supporting
- Adobe Illustrator
How I engineer
Systems before patches
Reusable architecture beats solving the same problem once per feature. It is also what makes a codebase survive a second year.
Measure before optimizing
Performance work follows profiling, not intuition. The budget is set by the hardware the product actually runs on.
Own the delivery path
Engineering responsibility does not end at a working build. Integration, platform constraints, release and what happens after launch are part of the job.
Build for the team
Tools, documentation and technical standards decide how fast everyone else can ship. That is worth engineering time.