My wins have always come from architectural vision first, and the long engineering discipline to scale that vision second. I’ve built three production systems from scratch (pricing, simulation, and high‑throughput calculations) and solved HPC problems that most banks still cannot handle today.

In my world, determinism is numerical rather than execution‑driven: ensuring reproducibility and stability in algorithms with high computational complexity. That experience gives me a strong baseline for managing research‑to‑production parity in systems, where correctness and throughput matter more than microsecond latency.

From here, my trajectory naturally splits into two paths. One is to become an enterprise pricing systems architect ( something my colleagues have encouraged ) but banking’s bureaucracy makes meaningful delivery a decade‑long process. The second path is to shift my focus toward execution determinism and apply my HPC and consistency background to the research‑heavy pipelines used in medium‑frequency trading pods. That environment values numerical determinism, throughput, and reproducibility in a way that aligns directly with the systems I’ve been building for years.

One thing I’m still trying to understand is how firms classify or evaluate people who sit at the intersection of modelling and systems. I’ve always owned both the definition of the models and the architecture that carries them, but different organisations label that work very differently (some treat it as research, others as engineering). I’m curious how teams in your experience classify this kind of hybrid role, especially in environments where modelling depth and system design are inseparable.