Senior Game Developer
Most engineers learn Unity through casual games and stay in that lane. My path has been different — I've shipped gameplay systems across four distinct high-stakes domains: real-money gaming (MPL, where a bug means real financial loss), defence-sector simulation (fighter pilot training, where accuracy is safety-critical), live-service simulation (Star Chef, a 3-year LiveOps cycle), and now cross-engine slot development in Dubai (Cocos Creator — a new engine, tight timelines, no room for error).
Each domain built a different muscle:
RMG (MPL) made me paranoid in the right way — server-authoritative architecture, anti-cheat, tamper-proof state. 100K+ daily matches, sub-150ms matchmaking latency. Defence simulation taught me precision — integrating an ML-trained autonomous AI model where "close enough" isn't acceptable. Live-service (99 Games) taught me patience and systems thinking — three years on one game, building reusable architecture that scales with it. Dubai/Agapi proved I can take on an unfamiliar engine (Cocos Creator + TypeScript) and deliver a production-ready build under aggressive deadlines, from scratch.
What makes me unique: Most senior Unity engineers go deep in one genre. I'm a cross-domain problem-solver — a pattern that works in a casual game can directly inform how I approach a fairness problem in RMG, or a real-time constraint in simulation, because I've lived in both worlds. 9+ shipped titles, 90M+ combined users, and a track record of adapting fast to new engines and stacks whenever the project demanded it (Unity → Cocos, and whatever comes next). That's not generalist dabbling — it's proof I can deliver senior-level output on any stack, fast.