Amin Hydar Ali

A technical starting point

I am a Nigerian software engineer and co-founder of Quant Research Desk. My background is in software development, including work with Python, Django, APIs, PostgreSQL, Redis, real-time systems and cloud infrastructure.

The way I approach a difficult problem is shaped by engineering: break it into parts, make the assumptions clear, build something that can be examined and test whether it works. That way of thinking is what first drew me toward quantitative finance.

Turning an idea into a test

I did not come to markets through a traditional financial career. I was interested in how an investment idea could be translated into rules, implemented in code and tested against historical data. That led me toward systematic and quantitative research.

I am continuing to develop my knowledge of quantitative finance, especially systematic strategies, portfolio construction, risk management, transaction costs, statistical validation and walk-forward testing.

I work on research and backtesting tools, strategy implementation in Python, data workflows and systems for testing, validating and documenting research. I also develop the QRD platform itself, including the tools used to organize and publish our work.

I see this technical work as part of the research process. Poor data handling, implementation errors or unrealistic assumptions can make a weak strategy look convincing. Reliable tools help us inspect how a result was produced and make it easier to challenge.

Alongside software engineering, I have studied International Relations, with a background in Defence and Strategic Studies. This has contributed to my interest in uncertainty, incentives, changing environments and the economic and geopolitical forces that can affect market behaviour.

I do not treat a political or economic explanation as a substitute for quantitative evidence. It may help generate a research question, but the idea still has to be tested against data and realistic assumptions.

Questions I want the research to answer

Why might this work? What assumptions are we making? What happens if those assumptions are wrong? What evidence would make us reject the idea?

I want a strategy to be examined across different periods, market conditions and assumptions, with realistic costs and implementation constraints considered. If results depend on a narrow setting or disappear under more realistic conditions, that should be visible in the research.

My focus is not only on individual strategies. I also want to help build a research process that is reproducible and easier to challenge, with clear data workflows, documented assumptions and tools that make tests easier to inspect.

Good engineering cannot make an idea sound. It can help us identify where a result came from, test whether it survives changes in assumptions and avoid mistaking implementation mistakes for evidence.

A strategy should not earn our confidence simply because the backtest looks good. We should understand why it might work, where it can fail, and whether it survives serious testing.

I want to help develop QRD into a serious quantitative research organization, with infrastructure covering the process from an initial hypothesis through data, modelling, portfolio construction, risk and validation, and eventually implementation.

The goal is not to produce as many strategies as possible. It is to get better at separating ideas that deserve further attention from those that only look convincing at first.