What Derivatives Trading Taught Me About Building AI Systems
11 Apr 2026
I spent six years trading derivatives before becoming an AI engineer. Most people see those as unrelated careers. They’re not. The mental models from trading are the same ones that make you effective at building AI systems — and the ones most AI engineers are missing.
1. Thinking in Probabilities, Not Certainties
On the trading floor, every decision is a probability-weighted bet. You never know the stock will go up. You estimate the probability, size the position accordingly, and manage the risk.
AI systems work the same way. An LLM doesn’t know the answer — it produces a probability distribution over tokens. When you build a RAG pipeline, you’re not guaranteed to retrieve the right document. When you deploy an agent, you can’t be certain it will call the right tools.
The trading instinct: Think about confidence intervals, not binary outcomes. Build systems that handle the case where the model is wrong — because it will be, and more often than you expect.
Most AI engineers I work with treat model output as ground truth. Traders never make that mistake with their positions.
2. Position Sizing = Resource Allocation
In trading, the best idea in the world is worthless if you size the position wrong. Too small and it doesn’t move the needle. Too large and one bad tick wipes you out.
In AI engineering, the equivalent is token budgets, model selection, and context allocation. Do you burn 100K tokens on a single research query, or split it across four focused sub-queries? Do you use Opus for everything, or route simple tasks to Haiku and save Opus for synthesis?
The trading instinct: The size of the bet matters as much as the direction. In AI, the cost, latency, and context allocation of each model call matters as much as the prompt.
I built my finance agent with this in mind: the main agent uses Sonnet for orchestration, delegates simple web searches to a Haiku-powered subagent, and reserves context for the final synthesis. That’s position sizing applied to LLM architecture.
3. Risk Management > Return Optimization
New traders obsess over finding the perfect entry. Experienced traders obsess over managing the downside. The entry is maybe 20% of the outcome. The exit rules, stop losses, and hedges are the other 80%.
In AI systems, the equivalent is guardrails, error handling, and fallback behavior. The prompt engineering is maybe 20%. The other 80% is: What happens when the API times out? What happens when the model hallucinates a function name? What happens when the retrieval returns irrelevant chunks?
The trading instinct: Plan for failure modes, not just success paths. Every tool in my agent returns error messages as text content blocks — so the agent can reason about the failure and adapt, rather than crashing. That’s a stop loss for AI.
4. Paper Trading vs. Live Execution
Every trader knows the gap between backtesting and live execution. Your model works perfectly on historical data, then falls apart in production because of slippage, latency, and market impact that didn’t exist in the backtest.
In AI, this is the gap between notebooks and production. Your RAG pipeline works great on 10 test queries in Jupyter, then fails in production because of edge cases in document formatting, embedding drift, or retrieval under load.
The trading instinct: Don’t trust the backtest. Deploy it, measure it in production, and iterate. I evaluate my agent’s research briefs by reading them — not by running automated metrics on synthetic test cases. The real test is: would I trust this brief enough to act on it?
5. The Information Edge Is Temporary
In trading, an edge — a piece of information or a strategy that gives you an advantage — degrades the moment others discover it. The alpha in statistical arbitrage strategies half-lives in months.
In AI engineering, the same is true. The techniques that are novel today (RAG, agents, tool use) will be table stakes in 12 months. The edge isn’t knowing how to build a RAG pipeline — it’s knowing how to build the next thing while everyone else is still learning RAG.
The trading instinct: Build at the frontier, not the median. When I chose the Claude Agent SDK (released days ago) over LangChain for my finance agent, I wasn’t choosing the safer option — I was choosing the one that positions me 6 months ahead.
6. Cutting Losers Early
The hardest thing in trading is admitting you’re wrong and closing a losing position. The instinct is to hold on, add to it, wait for it to come back. Professional traders develop the discipline to cut losers fast and let winners run.
In AI engineering, the equivalent is knowing when an approach isn’t working and pivoting — not spending three more days debugging a prompt chain that fundamentally can’t solve the problem. After two failed corrections with an LLM, clear the context and rewrite the prompt from scratch. After a day of fighting a framework, switch to a simpler one.
The trading instinct: Sunk cost is irrelevant. The only question is: what’s the best action from here?
The Meta-Lesson
Trading taught me that the world is uncertain, that models are approximations, and that the system around the model matters more than the model itself. Position sizing, risk management, execution quality, and the discipline to cut losers — these aren’t finance concepts. They’re engineering principles.
The best AI engineers I know think like traders: they size their bets (model selection, context allocation), manage their risk (guardrails, fallbacks, evaluation), execute with discipline (production engineering, not notebook prototyping), and stay at the frontier (building with new tools, not just reading about them).
If you have a non-traditional background — trading, medicine, law, operations — don’t see it as a gap. It’s a mental model that most AI engineers don’t have. And mental models are the hardest thing to teach.