Simulation Systems Architect (Mathematical Modeling) at DeepSense
We are not looking for a game designer or feature-level contributor.
We are looking for someone who has built and owned the system that defines how production outputs are generated, validated, and controlled at scale.
If your experience is limited to designing individual features, games, or tuning outputs — this role is not a fit.
This role is about architecture — not individual game design.
You will define and own a simulation and mathematical production system used across multiple releases, ensuring all outputs follow unified, deterministic standards.
What you will do:
Take full ownership of the system that defines how all production outputs are generated and validated
Make architectural decisions that directly impact all releases, not individual implementations
Own and define the simulation and mathematical production architecture across all releases
Build systems that generate, control, and validate outputs under unified standards (not manual or per-title production)
Define deterministic validation logic between models, simulations, and production systems
Create reusable, configuration-driven systems instead of one-off implementations
Ensure all production outputs are governed by system-level rules, not manual decisions
Set and enforce standards for RTP, volatility, exposure, and statistical correctness
Work closely with engineering to ensure systems are scalable, testable, and production-grade
Who you are:
You have taken full ownership of a system that defines how production outputs are generated, validated, and controlled
You have designed and owned reusable systems used across multiple releases — not just contributed to them
You think in terms of systems and architecture, not individual features or games
You have experience building or working with simulation pipelines and validation frameworks in production
You are comfortable defining standards and enforcing them across teams
You have strong hands-on ability in mathematical modeling, simulation, or quantitative systems design
You have made architectural decisions that were used across multiple releases or systems — not just contributed to them
Nice to have:
Experience with Monte Carlo methods, probabilistic modeling, or statistical validation at scale
Experience designing internal tools, DSLs, or configuration-driven systems
Background in gaming, quantitative finance, or scientific computing
Experience with Python, C++, or similar languages used in simulation systems
This role is not focused on designing individual games or tuning features.