What a quant trader actually does

The word "quant" tends to bring up pictures of physicists, banks of screens and programs that trade faster than anyone can watch. That world exists, but it is a small corner of systematic trading and not what this course is about.

For an individual trader, the job is quieter. You take something you believe about a market, write it down precisely enough that a computer can check it, test it on data, and then decide, with evidence rather than memory, whether it deserves real money. Everything else in this course is a way of doing those steps carefully.

A rule a computer can check

Here is the smallest possible example. Suppose a trader says: "I buy when today's close is above the average of the previous five closes." That sentence is already a rule, because every part of it can be measured. Written in Python, it looks like this:

# A rule a computer can check: is today's close above the average of the previous five closes?
closes = [101.2, 102.5, 101.8, 103.1, 104.0, 103.6]
 
previous_five = closes[-6:-1]
average = sum(previous_five) / len(previous_five)
today = closes[-1]
 
print(f"Average of the previous five closes: {average:.2f}")
print(f"Today's close: {today:.2f}")
print("Rule fires: buy" if today > average else "Rule does not fire: stay flat")

Average of the previous five closes: 102.52
Today's close: 103.60
Rule fires: buy

You do not need to understand the code yet; Module 01 starts Python from zero. What matters is the shape: a list of prices goes in, a yes or no comes out, and anyone running the same code on the same numbers gets the same answer.

Compare that with "I buy when price looks strong." Nothing in it can be measured. Two traders would disagree about the same chart, and the same trader might disagree with themselves on a different day. Before any testing can happen, words like "strong", "extended" or "near support" have to become numbers.

Where the time actually goes

Watching positions and placing orders is a small part of a systematic trader's week. Most of the time goes to work that happens before and after a trade:

• Ideas. Reading, observing markets, and turning a vague observation into a specific question. "Do pullbacks in an uptrend tend to recover?" is a question you can test. "Markets are emotional" is not.
• Data. Getting price history, checking it for gaps and errors, and understanding how it was built. Bad data produces confident, wrong answers. Module 02 is entirely about this.
• Code. Writing the rules, the test, and the reports, then checking that the code does what you think it does.
• Testing. Running the rules over history to see what they would have done, including costs and the trades you would rather forget.
• Validation. Asking whether a good test result is real or an accident of the particular data you used. This is where most ideas fail, and that is the process working.
• Running and review. Monitoring a live system, comparing it with what testing suggested, and deciding when a difference is noise and when it is a problem.

None of these steps needs to be glamorous. They need to be done in order, and written down.

Five myths to drop

"The computer finds the edge." A computer is fast and literal. It checks the ideas you give it. If you ask it to search thousands of rule variations until one looks good, it will find one, and that result will usually be noise. This is called overfitting, and avoiding it is a large part of the craft.

"More indicators means more edge." Each extra condition gives the test another way to fit the past. A rule with ten finely tuned parameters can describe history perfectly and still have nothing to say about tomorrow.

"A good backtest predicts the future." A backtest shows what a fixed set of rules would have done on one stretch of history, under the assumptions you built in. It is evidence, not a forecast.

"Automation removes emotion." It moves emotion somewhere else. You stop agonising over each entry, but the pressure returns during a drawdown, when switching the system off or changing a rule "just this once" feels urgent. A systematic trader needs rules for those moments too.

"You need a mathematics degree." The tools in this course are arithmetic, some statistics, and careful thinking about what could go wrong. Discipline and scepticism matter more than advanced mathematics.

What stays the same

Systematic trading changes how decisions are made. It does not change the market. You will still lose trades. Spreads, slippage and gaps still cost money. Risk still has to be sized before the story, and a run of losses still feels like a run of losses. If you already think in terms of risk per trade, a written plan and an honest journal, you have the foundations. The next lesson looks at exactly which of those habits transfer and which have to be rebuilt.

How this course works

The course has eleven modules, from this introduction to a capstone project. Each lesson lists what you will learn at the top, ends with key takeaways, a short self-check and a Lab exercise, and links to related glossary terms and Academy articles.

All code examples use synthetic data, generated with a fixed random seed so that you get exactly the output shown. No lesson uses real tickers, and nothing here is a strategy to trade. When the SCUTA Quant Lab opens, the exercises will run there. Until then, every exercise can be done on your own computer once Module 01 is set up.