Interview prep · ML × trading role

Agustin Lebron — comprehensive briefing

Synthesized from 10 podcasts / talks (~99k words of Deepgram transcripts) plus your own arc (agents, NoCap, colonization, hiring AS, costs vs edge, Bayesian process). Tuned for interview: vibes + substance — edge, costs, motivation, risk you’re paid for.

Ex–Jane Street trader / researcher Author · The Laws of Trading Engineer → poker → prop trading → consulting / crypto Decision-making as the core skill Transcript atlas + EDA →

0 EquiLibre Technologies — who you’re interviewing with

Company site: equilibre.ai. Official framing: Frontier AI Trading Research Lab — not a classic prop shop pitch deck. They build reinforcement-learning trading agents that “learn, adapt, and compete,” and they claim their models trade billions of dollars daily on hard markets.

One-line identity

Ex–DeepMind / DeepStack researchers applying imperfect-information game AI + RL to real financial markets (crypto → equities), partnered with quant infrastructure, lab-first culture.

Name confusion (for you)

  • EquiLibre Technologies = company (Prague)
  • DeepStack = famous 2017 poker AI (Science) the founders co-authored — origin myth, not the product name on the home page
  • Your local folder equilibre/ = interview prep workspace, not their codebase

Origin story they want you to know

  1. DeepStack (2017) — first AI to beat professional humans in heads-up no-limit Texas Hold’em (imperfect information; search + value nets; continuous re-solving). Published in Science.
  2. Founders also linked to Player of Games — strong play across perfect- and imperfect-information games.
  3. Time at IBM Research then DeepMind Edmonton (visiting/project work with Alberta poker / RL community).
  4. ~2022: leave DeepMind, found EquiLibre in Prague — “rather than playing poker, algorithms play algorithmic trading.”
  5. Thesis: poker and markets share structure — uncertainty, hidden information, adversarial other agents, sequential decisions, simple scalar score (money / chip EV).

Founders (from equilibre.ai)

PersonRoleBackground (public)
Martin Schmid, Ph.D. CEO & Co-Founder Algorithmic game theory. DeepMind project lead / senior RS; IBM. Co-author DeepStack & Player of Games. Public quote: markets score is simple — “how much money did the agent make?”
Matej Moravčík, Ph.D. CSO & Co-Founder Algorithmic game theory. DeepMind RS; IBM. Co-author DeepStack & Player of Games.
Rudolf Kadlec, Ph.D. CTO & Co-Founder Episodic memory modeling. DeepMind tech lead / senior RE; IBM. Neural LM work referenced in GPT lineage narrative on site. Co-author Player of Games.

Site stress: mix of big-tech AI labs, top-tier trading, academia — “builders and dreamers.” No sales/marketing theater — “success is quality of models and algorithms.”

What they say they do (product / tech)

Reinforcement learning

Self-learning agents that learn to trade like learning poker/chess/Go — strategies humans might not hand-design.

Trading as the arena

Compete on hard markets; efficiency / quality of algo as the scoreboard. Crypto rollout then equities (S&P / Nasdaq) in press.

Continual learning

World and other participants change — agents must adapt (non-stationary adversaries).

Funding & scale (public, mid-2026)

Advisors (signal density)

This board says: serious RL + game theory credibility, not a random fintech wrapper.

Prague / culture notes (from their site)

How this maps to your story (use in interview)

EquiLibre DNAYour bridge
Poker → imperfect-info sequential decisions You already study decision-making under uncertainty (Lebron prep + risk language); competitions = adversarial eval
RL agents, self-play, continual adaptation Agent orchestration, experiment loops, keep/kill, non-stationary reality (NoCap-style discipline)
Score = money / simple reward You insist on clear denominators and benchmarks before claiming win
Lab-first, model quality over theater Public artifacts, no chat-cosplay; costs vs edge honesty
Colonize: games → markets Your colonization: DS → text/vision → hardware → this ML×trading tile
Founder expertise density Your Law 1 motivation: paid to learn next to people who already paid DeepStack/DeepMind tuition
Why join them (in their + your language): You want the cost structure of a frontier lab — stability, structure, founder expertise, collective hours — applied to the same intellectual family as DeepStack: learning agents in adversarial, incomplete-information environments, with a scoreboard that is real markets. Your edge is manufacturing and measuring systems; their edge is game-theoretic RL at trading scale. Together: you bring assembly, eval, multimodal/product range; they supply the densest prior on multi-agent RL trading.
Questions that show you researched EquiLibre
  • How do you think about non-stationarity when other participants adapt to your agents (continual learning in live markets)?
  • What transfers cleanly from DeepStack-style search / value models to market microstructure, and what had to be invented from scratch?
  • Where does a new ML engineer create leverage first — research experiments, production training, evaluation, or systems reliability?
  • How do you prevent adverse selection on research ideas (proxy wins that don’t survive live) — what’s the keep/kill culture?
  • Lab-first vs partner trading (Tower etc.): how do you balance paper/research ambition with live PnL constraints?
Landmines specific to EquiLibre
  • Don’t call them a retail trading app or “AI stock tip” company.
  • Don’t confuse DeepStack (poker system) with the company name.
  • Don’t overclaim “I know RL for HFT” if you don’t — curiosity + solid ML/eval/systems is better.
  • Don’t dismiss finance as boring; they chose markets as the hard multi-agent domain.
  • Don’t treat press PnL claims as verified facts in their face — respectful curiosity instead.

Sources: equilibre.ai · TechCrunch / Recursive / CNBC coverage of founding & Series A · DeepStack (Science 2017) public literature · Tower Research partnership press. Verify live details before relying on valuation/volume numbers in conversation.

1 Who Lebron is

Career arc

  • Engineering degree → ~6 years designing front-end RF chips (cell / GPS).
  • Online poker boom (~2006) — enjoyed incomplete-info decision making under money.
  • Wanted “half engineering, half poker” → quant trading.
  • Quit in Jan 2008; got offer from Jane Street mid-March as Bear Stearns imploded. Future boss: trading is busy, making money, still hired.
  • ~6 years at Jane Street (incl. London); recruiting experience; left ~2014.
  • Book: The Laws of Trading (Wiley). Consulting tech cos on decision-making / hiring / growth. Crypto protocol work (mentioned in interviews).

Identity & positioning

  • Self-describes as stronger on the systematic / structured side of the spectrum than pure discretionary.
  • Heavy on analogies (poker, table selection, baloney sandwiches, jungle laws).
  • Core product he sells (book + consulting): trading as a general decision-making framework, not “how to get rich trading.”
  • Frequently gives the “Straussian” reading of his own book: if you’re honest, most people shouldn’t trade.
  • Twitter-ish handle referenced in show notes: @AgustinLebron3.
“I decided to look for jobs that were half engineering and half poker… that pretty much describes trading.” — Predicting Alpha podcast · career origin story

2 Vibe & how he thinks

Communication style

  • Warm, candid, slightly self-deprecating; not “alpha bro.”
  • Prefers precise definitions (edge, risk you’re paid for, costs).
  • Loves poker analogies for sample size and decision quality.
  • Honest about uncertainty: “if we’re being honest… you can’t know for sure.”
  • Will push back on overconfident retail narratives without being cruel.

Mental models he returns to

  • Competition denseness → “laws of the jungle,” not laws of nature.
  • Table selection — don’t sit at the wrong table.
  • Adverse selection / winner’s curse everywhere (markets, hiring, crypto deals).
  • Incremental colonization of adjacent markets / skills.
  • Process vs. outcome — good decisions can lose; bad can win.
  • Life is long — many shots to learn (said to his kids).
Interview vibe tip: Match his register — curious, concrete, probabilistic. Avoid hype (“guaranteed alpha,” “I always win”). Prefer: hypotheses, failure modes, costs, sample size, OOD.

3 Edge — his core concept

Edge is something that either you know or you can do that the marginal participant in that market either doesn’t or can’t. — Multiple interviews; formalized in the book

Forms of edge he lists

  • Technology / speed — systems that act faster / more reliably.
  • Models / research — better forecasts or structure understanding.
  • Access — unique market access, flow, relationships, geography.
  • Cost structure — lower fees, better financing, better ops.
  • Skill + judgment — discretionary edge via superior process (harder to prove statistically).

How do you know you have edge?

You don’t know for sure. You only get statistical bounds.

  • High-frequency / many trades → more data, more certainty; edges usually smaller.
  • Infrequent trades → fewer samples; need larger edges (or external evaluation of process).
  • Poker analogy: 100k hands for win-rate stats vs. ~1k hands for a pro to judge decision quality.
ML mapping: Edge ≈ a durable, deployable advantage after costs. A model with nice offline metrics is not edge until it survives transaction costs, adverse selection, capacity, and regime shift.

4 The 11 Laws of Trading

From The Laws of Trading: A Trader’s Guide to Better Decision-Making for Everyone. He taught new traders with these as mental shorthand; claims they’re timeless (Shakespeare knew versions of them). Aaron Brown’s foreword frames them as laws of the jungle — dense competition for scarce resources.

01
Motivation
Know why you are doing a trade before you trade. “What is trading about? Fundamentally, the relationship between you and the rest of the world.”
02
Adverse selection
You’re never happy with the amount you traded. Good trade → should have done more; bad trade → shouldn’t have done it. Information asymmetry is structural.
03
Risk
Take only the risks you’re being paid to take. Hedge the others. Right EV call can still lose.
04
Liquidity
Put on a risk using the most liquid instrument for that risk.
05
Edge
Clearly define and validate your edge. If you can’t explain it simply, it may not exist.
06
Models
Models should express your edge; be robust, transparent, adaptable — not cargo-culted complexity.
07
Costs & capacity
If your costs seem negligible compared to your edge, you’re wrong about at least one of them. Capacity kills good ideas.
08
Possibility
Respect extreme / fat-tail events; what’s possible is not what’s been in your recent sample.
09
Alignment
Incentives, org structure, and personal goals must line up with the risk you’re taking.
10
Technology / systems
(As treated in interviews & reviews) Execution, data, reliability — tech is often the edge or the hole that gets exploited.
11
Adaptation
Markets change; edges decay. The process of updating beats static “holy grail” systems.

Note: chapter titles vary slightly across summaries; the substance above is consistent across his interviews + book reviews. Motivation / Adverse Selection / Risk / Liquidity / Edge are the ones he drills hardest on podcasts.

For your interview: Pick 2–3 laws and connect them to your ML work. Example: “My calibration work is really Law 6 + Law 7 — the model only matters after costs and capacity.”

5 Jane Street & quant firms

Origin-story pattern of great firms

  • Start with something simple, self-contained you can do well.
  • Improve incrementally (trading yields to incremental improvement).
  • Colonize adjacent markets — next most similar thing you’re not doing yet.
  • Don’t try to build “do everything” firm on day one.

Jane Street edge (his take)

  • Not just excellence at best things — even their worst thing is pretty decent.
  • If you’re exploitable, you will be exploited → constantly plug holes.
  • Market making as a service business (liquidity), not “calling the market.”
  • Recruiting: hard to explain; he used the baloney sandwich analogy for ETF/ADR MM.
“If I can buy baloney, bread, and cheese for $3, make a sandwich, sell it for $4 — that’s a business. That is what ETF market making is.” — Outlier podcast · explaining prop market making

Why quant profits rose (hypotheses he floats)

Industry structure

6 Market making & adverse selection

Market making goal

  • No strong directional opinion; collect spread / provide continuous two-way markets.
  • Value of the service rises with volatility.
  • Crises can be excellent if you’re not forced to trade (liquidations, margin calls force others).

The hard part

  • Adverse selection: smart counterparties hit your bad prices and avoid your good ones.
  • Post a bad market → do all the bad trades you want.
  • Retail often confuses “emulate the big guys’ MM” with a viable personal strategy.

Adverse selection outside markets (he loves this)

ML angle: Training on “what you can observe” is often adversarially selected. Label bias, survivorship, fill-only-on-bad-prices — classic adverse selection in data.

7 Strategy building (practical, from Outlier sessions)

He did a cold “poke holes in a strategy” session — useful as a template for how he evaluates ideas.

What he values in a strategy discussion

  • Clear economic story for why an effect exists (not only backtest).
  • Where the edge comes from and who is on the other side.
  • Costs, capacity, liquidity choice, risk not paid for.
  • What would falsify the strategy / when to turn it off.
  • Separation of process quality vs. luck in outcomes.

Systematic vs discretionary

  • Spectrum, not binary. Even “fully systematic” shops have humans who turn systems on/off in crises.
  • OOD judgment: is this in-sample of training data? If not, keep running or shut off?
  • He’s uncomfortable at pure discretionary “read Bloomberg and be smart” end; respects people who make money that way but doesn’t claim expertise there.

Crisis / regime shift

8 ML lens — talk his language

He doesn’t center “deep learning hype.” He centers decision quality under competition. Translate your ML story into that frame.

ML thing you might sayHis language / upgrade
“My model has 62% accuracy”“What’s the economic edge after costs, and who is the marginal counterparty?”
“We beat the benchmark offline”“Is that in-sample of the regime you’ll trade? What’s the OOD plan?”
“Feature importance shows X”“Is that a causal/economic story or a correlated artifact?”
“We retrain weekly”“Adaptation law — how do you detect decay without overreacting to noise?”
“Low latency stack”“Tech as edge — and as a hole if you’re second-best.”
“We optimize Sharpe”“Which risks are you paid for? What are you accidentally warehousing?”
“More data = better”“More trades → statistical certainty, usually smaller edges; sample size math matters.”
“Black-box neural net”Be ready: models should express edge; transparency/robustness matter under stress.
Strong interview move: Describe one ML project as a mini trading system: (1) motivation, (2) hypothesized edge, (3) model that expresses it, (4) costs/capacity, (5) adverse selection in the data or fills, (6) how you adapt when it breaks.

Topics where ML naturally fits his worldview

8b Example: NoCap as risk capital (your story)

Use this when he asks for a concrete ML example. Map your nocap-agent-architecture work into his laws — not as “I built a cool agent,” but as risk-managed research capital under competition.

“I treat cloud credits and GPU hours the way a desk treats risk capital: I only take the scientific risk I’m paid to take, and I systematically hedge the risks that just burn bankroll — confounded experiments, silent re-spend, and ideas that look good on a noisy proxy.” — Spoken framing for interview

What NoCap actually is (one breath)

A closed-loop experiment runtime for BottleCapAI NoCap-Test: instrumented GPT-2 trainer + two-stage FineWeb triage + Modal serverless DAG + pre-registered keep/kill gates. Goal: reach val loss ≤ 3.3821 on one GPU faster than a re-benchmarked stock baseline — with a ~$25 cloud budget and negative results as first-class evidence.

Risk translation table (Lebron → your system)

His languageNoCap implementation
Risk you’re paid to take Whether a pre-registered idea (data band, prior, warmdown, …) improves time-to-target vs self-baseline. That’s the only “directional” bet.
Risks you hedge / refuse Wrong denominator (using 4090 board hours), silent A100-80 upgrades, re-running paid work, confounded stacks, pure hyperparam search as the “idea.”
Bankroll / capital Modal / cloud credits split across accounts; hard timeouts; smoke phase (~$0.01–0.04) before real spend; peak GPU concurrency capped by plan.
Adverse selection Proxy races and short curves will adversarially select flukes. Kill gates + dual-seed rules for tiny effects + trajectory-based keep/kill (not one snapshot).
Costs & capacity (Law 7) If a stack looks free or “basically free,” assume you’re wrong: scoring GPU prep is disclosed cost; composition risk parked ideas that only buy wall-clock.
Models express edge (Law 6) Flags default to stock semantics — every experiment is opt-in. The model/trainer is the instrument; the edge claim is the recipe + evidence, not a black box.
Adaptation Waves of races (kill MTP/shape, bank parallel, scale triage); F1 mint denominator then F2 stack — incremental colonization of adjacent arms.
Panic / risk off modal run --detach + one CLI panic stop; idempotent phases so restart doesn’t double-bill the same exposure.

Where is the edge?

Not primarily…

  • “We used GPT-2.”
  • “We have an LLM agent that chats.” (explicitly not — no tool-calling LLM in the loop)
  • A single magic architecture tweak without cost accounting

Actually…

  • Orchestration + capital discipline under a hard metric
  • Pre-registered gates so you don’t invent the stop rule after seeing the curve
  • Durable memory (volume) + skip rules = higher research throughput per dollar
  • Honest evaluation protocol (self-baseline F1) so claims survive adverse scrutiny
Edge sentence (use this): “My edge isn’t a secret loss function — it’s that I can allocate scarce compute like a risk book: fan out only pre-registered arms, kill losers with evidence, never re-pay for the same work, and only promote a stack after it beats a self-measured baseline under one-GPU rules.”

Credits as automation of risk management

If you also build a broader agent orchestration framework with credits, connect it like this:

Align with his “not an LLM agent” honesty: Emphasize control loop + policy + memory + tools. Humans write gates; machines execute the book. That matches his respect for systems that plug holes instead of cosplaying intelligence.

30-second spoken version

“For the NoCap challenge I built a serverless research runtime, not a chatbot. Cloud credits are the bankroll. The orchestrator is the risk system: smoke before size, parallel arms with pre-registered kill gates, idempotent phases so I don’t double-spend, and a hard rule that the only risk I’m paid to take is ‘does this idea beat my re-benchmarked baseline on one GPU.’ Architecture experiments that bought loss but destroyed wall-clock got killed or parked — Law 3 and Law 7. That’s the same muscle I’d bring to ML in a trading firm: treat experiment spend as risk capital, and treat methodology as part of the edge.”

If he pokes holes (be ready)

Source: software_i_built/modal/nocap-agent-architecture.html · rainbowpuffpuff/nocap

8c Baloney sandwich · AI agents as your edge

He explains Jane Street–style market making as the baloney sandwich business: buy components cheap, assemble, sell the finished product at a spread — a service with no deep directional view, but extreme pressure on costs, selection, and execution. Steal the analogy. Map it onto how you use AI agents.

“If I can buy baloney, bread, and cheese for $3, make the sandwich, and sell it for $4 — that’s a business. That is what ETF market making is.” — Outlier podcast · his framing of mechanical edge

Your sandwich (default mapping)

IngredientMarket making (him)You + AI agents
Inputs (baloney / bread / cheese) Securities that are mechanically related; raw quotes; capital Problem statement · context packs · tools/repos · model APIs · cheap compute credits
Assembly (make the sandwich) Hedge legs, stitch products, provide two-way market Short, sharp prompting · agent orchestration · verify/kill loops · stitch outputs into a shippable artifact
Sale / spread Liquidity service; earn spread if not adversarially selected Finished research, code, transcript atlas, experiment evidence — faster than someone doing it by hand
Adverse selection (the hard part) Smart flow hits your bad prices Models hallucinate, flaky tools, wrong baselines, quiet cost blowups — you only “fill” on bad work if your gates are weak
Edge Tech + people + costs so even the worst part is “pretty decent” You turn AI from a chat toy into a production sandwich line: recipes, capital limits, keep/kill, evidence
Edge one-liner: “My edge isn’t ‘I prompt ChatGPT.’ It’s that I buy raw model capacity and tools like sandwich ingredients, assemble them with a thin orchestration layer and hard stop rules, and sell finished work — research runs, systems, decision support — at a wall-clock and quality spread most people can’t run.”

Multiple spoken variants (pick 1–2, don’t recite all)

Variant A · Classic steal (closest to his words)
“You talked about the baloney sandwich business for ETF market making — buy the parts, assemble, sell the service. That’s how I use AI agents. Models, scrapers, notebooks, cloud credits are the ingredients. I don’t sit around chatting. I take a problem, put a thin control loop around it — prompt, run, check, kill or keep — and ship a finished sandwich. The edge is the assembly line and the adverse-selection filters, not the bread.”
Variant B · Risk capital (pairs with NoCap)
“For me AI is a sandwich line funded with risk capital. Credits are the bankroll. Agents assemble the sandwich; I only take the scientific risk I’m paid for — ‘does this idea beat baseline?’ Everything else I hedge: smoke tests before size, idempotent reruns so I don’t double-buy ingredients, pre-registered kill gates so I don’t keep a bad sandwich because it looked tasty on a short proxy.”
Variant C · Against retail AI (table selection)
“Most people use AI the way retail traders click futures — same table as everyone, no edge. I treat agents more like a prop desk: small number of recipes I understand, clear PnL metric, and I refuse games where I’m just hoping the model is smarter than the competition. Prompt → verify → ship. If I can’t define the sandwich, I don’t open the kitchen.”
Variant D · Mechanical relationship (no magic)
“Market making works because of mechanical relationships between ingredients — ADRs, ETFs, underlyings. Agent work is the same: the problem has parts that compose. I spend effort on the composition function — tools, memory, gates — not on pretending the model has a directional view of the universe. I’m not predicting the future; I’m manufacturing a deliverable with controlled cost.”
Variant E · Plug the holes (Jane Street “worst thing is decent”)
“You said a big firm edge is that even their worst skill is still pretty decent — holes get exploited. That’s how I build agent systems: the interesting model call is maybe 10% of the stack. Logging, timeouts, eval checks, human kill switches — those are the unsexy ingredients that stop adverse selection. If the sandwich line is leaky, smart failures will hit me every time.”
Variant F · 20-second ultra-short
“AI agents are my baloney sandwich line: cheap ingredients, thin assembly, sold as finished work. Edge = orchestration + kill gates + capital discipline — not clever vibes in the prompt box.”

How to land it without sounding gimmicky

Why you’re not the marginal participant

Edge (his definition): something you know or can do that the marginal person in the same game doesn’t or can’t. In “people using AI at work,” the marginal participant is not “someone without GPT.” It’s someone who treats the model as magic autocomplete: vague prompt → accept first answer → pay full rework tax. Your gap vs that margin is concrete.

DimensionMarginal AI userYou (non-marginal)
Tool surface Browser chat only CLI agents, scripts, libraries that already solve subproblems — lower assembly cost
Model map “The AI can code / write anything” Learned envelope: what models are good/bad at; when to not call them
Measurement Vibes / “looks right” Benchmarks and task suites to price capability before betting time
Risk choice (Law 3) Burns time on toil and re-discovery without noticing Hedges unpaid risk (blank-page tax, boilerplate, search) so you can concentrate risk on work the company actually pays for
Adverse selection Silent failures, confident wrong answers ship Gates: checks, reruns, human review where the cost of being wrong is high
Honest bound: Knowing CLIs and libraries is not infinite alpha — it decays as everyone learns it. Your edge is the bundle under time pressure: tool selection + model envelope + benchmarks + choosing which risks to take. That’s closer to “desk skill” than to a secret prompt.

Risks you’re paid for vs risks you refuse

Paid risk (take it)

  • Committing your time and reputation to this company / role
  • Judgment calls on product, research direction, what to build next
  • Owning outcomes when the sandwich is wrong under your gates
  • Learning domain-specific edge the firm actually monetizes

Unpaid risk (hedge / outsource)

  • Re-deriving known library solutions from scratch
  • Blank-page drafting, glue code, mechanical ETL, first-pass search
  • Holding model uncertainty without an eval when a benchmark exists
  • Infinite chat without a shippable definition of done
Variant G · “Not marginal” (use this — most honest)
“In your language, edge is vs the marginal participant. For AI-assisted work the marginal user opens a chat box, pastes a vague task, and hopes. I’m not that. I know the CLI and library surface, so I don’t rebuild ingredients that already exist. I’ve spent time learning what models can and cannot do, and I look up benchmarks before I bet a day on a task class. That lets me take the risk I’m actually paid for — putting my time into this company and the decisions that matter — and hedge the risks I’m not paid for: toil, re-discovery, and silent model failure.”
Variant H · Career risk as principal
“Law 3: take only the risks you’re paid to take. The principal risk I’m taking is career risk — my calendar and focus here. AI agents are how I hedge operational risk around that bet: faster sandwiches, measured model use, tools instead of heroics. I’m not trying to be paid for ‘prompting.’ I’m trying to be paid for judgment and shipped systems, with a lower cost basis.”

8d His phrase bank — embed this in your brain

Built from high-count content bigrams/trigrams in the corpus plus how he actually uses them. Goal: when he speaks, you already have the slot filled — and you can reuse the same language without parroting randomly.

Institutional world (he lives here)

Phrase (corpus)What he usually meansHow you can use it
jane street / jane street capital / left jane street Origin story, recruiting, MM culture; “left Jane Street” = career chapter, not bitterness. “Coming from a JS-style process culture…” when talking keep/kill and evidence.
prop trading / prop trading firms Principal risk, internal capital, tight feedback — not asset-management storytelling. Frame NoCap credits as a tiny prop book for experiments.
trading firms / quant trading / quant trading firms Industrialized edge: tech + research + ops; consolidation pressure on small shops. “At quant trading firms the waterline rose…” when discussing competition for ML talent.
market maker / market makers / etf market maker / options market maker Service business; no strong directional view; adverse selection is the job. Baloney sandwich + agent assembly line analogy.
financial markets Default arena for laws of trading; dense competition metaphor. “Same laws show up outside financial markets…” (his consulting pitch).
investment banks Old middlemen being disintermediated by quant MMs / direct RFQ. Optional color if talking industry structure — not your main story.
hedge fund Appears as industry furniture; less central than prop/MM language. Don’t force it; he is more prop/MM than “PM narrative.”

Edge, risk, selection (core doctrine)

PhraseLoad-bearing ideaMemorize / remix
adverse selection You’re never happy with size; counterparties / applicants / data hit you when you’re wrong. “Agent failures are adverse selection on my gates.”
personal edge Edge is local to you vs the marginal participant — not “I read a book.” “My personal edge is orchestration + capital discipline.”
risk taking / risk tolerance set / tolerance set point Risk is chosen; people have a set point (incl. “red-blooded risk” color in book talk). “I set an explicit risk-tolerance set point for experiment spend.”
expected value terms Right EV decision can still lose — process ≠ outcome. “In expected value terms the arm was good; the outcome can still be red.”
common failure mode He names patterns of how people/systems fail (retail, hiring, strategy). “Common failure mode for AI work is no kill criteria.”
market clearing price Price as coordination; competitive equilibrium thinking. Use sparingly; good if talking hiring/comp or market structure.

Retail vs pro / “wrong table”

PhraseWhat he’s doingYour mental hook
retail trader / retail traders / retail trading Not contempt — structural disadvantage vs machines, capital, data. Retail AI use = same table as everyone; your sandwich line chooses a better table.
trend following Often used when stress-testing “where is the edge?” in systematic stories. If you mention momentum/trend, be ready for “who pays you?”
pro gambling direction / gamblization World adding more betting surfaces → more uninformed flow for MMs. Industry color; shows you heard secondary themes.
micro cap stocks Classic “maybe small shops can still play where big firms don’t care” — and that waterline rising. Analogy: niches for agent automation before they’re saturated.

Origin story triggers (if bio comes up)

PhraseContext
online poker / poker boomBridge from engineering to trading — incomplete info + money.
left jane streetClean chapter break → book, consulting, crypto/protocol work.
machine learning / machine learning spaceHe names ML as one possible edge source (models/research), not as magic.
compound annual growth / annual growth rateNumeracy furniture — long-horizon framing when talking careers/returns.
obscure chess variantColor for “specialized games / wrong table” style analogies — rare but sticky.
buy home insuranceRisk-transfer analogy territory (risks you’re paid for vs hedge).

Flash drill (2 minutes before the call)

If he says…

  • baloney sandwich → your agent assembly line
  • adverse selection → gates on agent/model output
  • marginal participant → who you’re better than, specifically
  • costs seem small → Law 7, always wrong
  • retail → wrong table / wrong game
  • plug the holes → timeouts, evals, panic stop

You reply with…

  • ingredients → assembly → finished artifact
  • credits as risk capital
  • pre-registered keep/kill
  • self-baseline / honest denominator
  • personal edge = orchestration, not vibes
  • one concrete sandwich (NoCap / atlas)
Don’t overfit the n-grams. High counts measure what the corpus talks about, not a sacred vocabulary list. Prefer 5 phrases you can use cleanly over 25 you force. Best embeds: adverse selection · personal edge · market maker · expected value terms · common failure mode · prop trading · risk tolerance.

8e Colonize adjacent · your arc + conquering hiring AS

He describes great trading firms as: start with something simple and self-contained, get good, then take the next most similar thing you’re not doing yet — “colonize adjacent markets.” Plug holes so even the weakest part is still decent. Your career is the same pattern on skills and proof surfaces.

Your colonization map (say it in order)

StepTerritoryWhat transferredProof surface
1 · Core Data science problems Metrics, baselines, holdout honesty, “what does win mean?” Projects / coursework / job work — define denominator first
2 · Adjacent modality Text → vision (e.g. deepfake detection) Same loop: labels, leakage, eval protocol — new sensors/features Detection systems, papers/demos; still supervised learning discipline
3 · Adjacent stack Hardware / BCI · think2earn.com ML meets physical constraints, product, infra — not only notebooks Shipped product surface; systems that leave the laptop
4 · Adversarial validation Competitions with other participants Win rate under competition — closest thing to market contestability Leaderboards / ranked outcomes vs peers (not vibes)
5 · Portfolio as market carolcalin.com Public track record employers can sample without trusting a cover letter Examples that survive cold inspection
6 · Current colonization Agent orchestration · capital discipline · ML × trading seat CLI/tools/benchmarks + sandwich line + risk-you’re-paid-for NoCap-style runs, equilibre prep, production habits
One breath version: “I colonize adjacent skill markets the way you describe firms colonizing adjacent markets. Data science first — clean metrics. Then text and vision, including deepfake detection — same eval muscle, new modality. Then hardware and product via Think2Earn — constraints leave the notebook. I check win rate in competitions against other participants, and I keep a public sample set on carolcalin.com. Next adjacent tile is applying that stack where decisions and risk capital matter — including this role.”

Why this is edge (not a random resume walk)

If he pokes: “That’s just a career, not edge”
“Agreed it’s a path. The edge claim is narrower: under time pressure I already know how to move into an adjacent problem class without dropping the measurement standard — and I’ve stress-tested that against other participants, not only private demos.”

Hiring is adverse selection — how you conquer it

His point: the hiring market is stacked against employers and noisy for candidates.

What employers fear (winner’s curse)

Your anti-AS kit (make selection work for you)

AS problemYour counter-signalWhere it lives
“On the market = residual” Show optionality you’re choosing — deliberate colonization toward this domain, not drift Arc narrative + why this firm/role now
Cheap talk Public artifacts that can be adversarially inspected carolcalin.com · think2earn.com · competition results
Private overfit stories Win rate vs participants — external contestability Named competitions / ranks (be precise, not vague “I win a lot”)
AI hype without gates Model envelope + benchmarks + kill criteria + paid vs unpaid risk NoCap / sandwich variants G–H
Can’t work with smart people Invite them to poke holes; bring a strategy to stress-test Ask good questions; take feedback live
Employer winner’s curse Make it easy to falsify you quickly — trial task framing, clear past failures killed with evidence “Here’s how you’d know in 2 weeks I’m wrong”
Conquer hiring AS = become easy to select, hard to mistake. Dense public signal + competitive outcomes + honest kill list of failures + clear statement of the risk you’re taking (your time here). You’re not asking them to bid blind; you’re posting a two-way market with evidence.
Spoken — hiring adverse selection (if the topic opens)
“You write about hiring as adverse selection — people on the market are selected against, and employers can overpay on a bad read. I’ve tried to reduce that for both sides. I keep work inspectable on carolcalin.com and Think2Earn instead of only private claims. I care about win rate in competitions with other participants so I’m not only grading my own homework. And I’m explicit about the risk I’m taking: my time and focus here — Law 3 — while I use tools and agents to hedge unpaid toil. If the signal’s wrong, you should be able to see it fast from the artifacts, not six months in.”
If they ask “why are you looking / available?”
“I’m not framing myself as leftover inventory. This is an adjacent colonization step — I’ve built measurement, multimodal ML, and product/hardware proof; I want the next tile where decision quality and risk capital matter day to day. I’m choosing the table, not fleeing one.”

Pre-interview checklist (this section)

  1. Name one competition with true participants + result (precise).
  2. Name one failure you killed with evidence (AS-friendly honesty).
  3. Open carolcalin.com + think2earn.com paths you’ll actually point to.
  4. One sentence: why this role is the next adjacent tile, not a random jump.
  5. One sentence: risk you’re paid for = time/reputation here; what you hedge with tools/agents.

8f Motivation · costs vs edge · why work at a firm

Two laws at once: Law 1 Motivation (know why before you act) and Law 7 Costs (if costs seem tiny vs edge, you’re wrong about at least one). Your honest read: you have some edge, but costs are high — so the rational move is not “go solo forever,” it’s to change the cost structure by joining a firm that supplies what you’re missing.

If costs seem negligible compared to your edge, you’re wrong about at least one of them. Attention and risk management are costs too. — Laws of Trading · costs / capacity family

Your situation in his language

Edge you already have (non-zero)

  • Tool surface: CLIs, libraries, agent orchestration
  • Model envelope + benchmarks (price the bet before sizing)
  • Adjacent colonization: DS → text/vision → hardware/product
  • Contestability: competition win rate vs participants
  • Auditable work: carolcalin.com · think2earn.com
  • Capital discipline habits (kill gates, unpaid vs paid risk)

Costs that are high alone (honest)

  • Attention — you pay full focus tax on every domain jump
  • Risk management — no desk/process default; you invent gates every time
  • Learning bandwidth — tuition in time without being paid for it
  • Missing infrastructure — data, prod constraints, multi-person review
  • Missing expertise density — founders/peers who already paid those costs
  • Stability tax — volatility of solo path steals capacity from deep work
Key reframe: You’re not saying “I have no edge.” You’re saying edge / cost is still bad solo because costs (attention, RM, learning, isolation) dominate. A good firm is not charity — it’s a cost-sharing and prior-sharing machine that lets your edge compound.

Your motivation (Law 1) — use this, it’s clean

You want to be paid to take the right risks and buy the missing inputs:

Spoken — costs high, edge real, why join (primary)
“Law 7 hits me personally: I think I have some edge — tools, agents, eval habits, a track record I can show — but my costs are high. Alone I pay full price for attention, risk management, and learning. I want to work here because Law 1 for me is clear: I want to be paid to learn, with stability and structure, inside a company that’s already innovating, with founders and teammates who’ve put in the hours I haven’t yet. That’s not ‘I need a job.’ It’s choosing a better cost structure so the edge I do have can actually compound.”
Spoken — shorter
“I have edge on assembly and measurement; I don’t have edge on institutional density. Joining is how I stop paying retail prices for mentorship, structure, and hard problems.”
If he says “then just consult / stay independent”
“Independence maximizes freedom and also maximizes cost surface — attention, RM, no shared priors. I’m deliberately buying the package: paid learning, stability, structure, founder expertise, and the integrated work of a team. That’s the trade I want to make with my time — the risk I’m paid for.”

Map motivation → his hiring / firm story

You wantHis world equivalent
Paid to learnJS day-one sitting next to seniors; mentors accelerate learning
Structure / processGates, culture, “even worst skill is decent”
Founder/team expertiseDense talent; plug holes as a group
Collective hoursFirm as multi-person sandwich line / shared cost basis
StabilityRisk capital so you’re not forced flow in personal crises
Innovation problemsAdjacent colonization with real markets/constraints

8g Bayesian software decision process

Practical loop for product, ML, and incidents — aligns with his process-vs-outcome honesty and your keep/kill experiment culture.

BayesSoftware meaning
PriorBelief before this observation (base rates, past systems, team defaults)
Likelihood / LRHow expected is this evidence if H vs not-H? Strong/medium/weak is enough
PosteriorShip / kill / dig / hire after the test
Posterior → new priorWrite it into runbooks, defaults, CI, personal model map — don’t restart at 50/50
One-liner
“I treat software decisions as Bayesian updates: priors from past work, likelihoods from pre-registered tests and benchmarks, posteriors as ship/kill, and those posteriors become the next defaults — including the institutional priors I’d gain on a team.”

9 Career advice & “don’t trade”

If you’re smart enough and hardworking enough to make a living in financial markets, there’s probably an easier way to make money and have a satisfying life. — Trading, Crypto & Adverse Selection podcast

Why default advice is “don’t trade”

  • You’re up against firms with talent, capital, data, and microsecond stacks.
  • Retail often buys courses to click S&P futures — wrong table.
  • Table selection (poker) is everything.
  • Every trade pays someone (spread, risk transfer, attention, risk management load).

When trading can make sense

  • You found a niche you actually understand via long trial-and-error.
  • You stick to what you’re good at (friends who make money retail do this).
  • You’re not competing head-on with the machines on their home field.
  • As a career inside a firm: institutional resources flip the resource equation.

Who should become a quant trader?

10 Hiring, talent, culture

Signal you can send: Talk about a time you found a hole in your own system (bug, silent failure, distribution shift) and fixed it. That maps to “plug the holes or get exploited.”

11 Questions you can ask him

Prefer questions that show you read his mental models — not generic “what’s a day in the life.”

Edge & ML
In an ML research seat, how do you distinguish “a better offline model” from “a real edge after adverse selection and costs”? What failure modes do you see most?
Systems on/off
You talk about even systematic shops needing judgment to turn systems off in crises. How should an ML engineer design for that human–model loop without creating silent risk?
Laws in org design
Which of the laws do you find tech companies break most often when they scale hiring and product decisions?
Adjacent colonization
Jane Street–style growth is “colonize adjacent markets.” What’s the analogous move for an ML team inside a trading firm today?
Talent
When you recruited, what separated people who thrived from people who were merely very smart?
Personal calibration
How do you personally update when a strategy or model stops working — sample size vs. structural break?
Career honesty
Given your default “don’t trade,” when is joining a trading firm the right move vs. building decision systems in tech?

12 How to present yourself (ML + trading role)

Narrative spine

  1. Motivation: why markets / decision systems (not “I like money”).
  2. Edge hypothesis: what you uniquely know or can build.
  3. Model: how you express that edge technically.
  4. Reality check: costs, capacity, adverse selection, evaluation.
  5. Adaptation: monitoring, decay, OOD, human override.

Story bank (prep 2 concrete examples)

  • A project where metrics looked great but economics failed (costs / leakage).
  • A time you reduced risk you weren’t paid to take.
  • A debugging of silent failure / distribution shift.
  • Collaboration: turning research into a reliable production decision system.

One-sentence positioning (customize)

“I build ML systems the way a careful trader builds strategies — clear motivation, explicit edge, cost-aware evaluation, and a plan for when the world goes out of distribution.”

Full pitch skeleton (2 minutes)

  1. Motivation (Law 1): paid to learn · stability · structure · company innovation · founder/team expertise · collective hours.
  2. Edge: non-marginal AI user — CLI/libs, model envelope, benchmarks; sandwich line; colonization DS→vision→hardware; competitions; public portfolio.
  3. Costs (Law 7): solo costs (attention, RM, learning) are high vs that edge → join to improve cost structure, not because edge is zero.
  4. Risk paid for: time/reputation here; hedge unpaid toil with agents/tools.
  5. Hiring AS: make yourself easy to select — artifacts, contestability, fast falsifiability.
  6. Close: adjacent tile, not leftover inventory; curious peer, honest uncertainty.

Deep links: motivation + costs · NoCap · sandwich / agents · colonization + hiring AS · Bayesian process · phrase bank · today’s synthesis.

12b Today’s synthesis — all threads in one place

Everything we built in this prep arc, compressed for final review.

1 · Edge vs marginal AI user

Not “I use GPT.” CLI + libraries + model can/can’t + benchmarks. Edge = better production function under time pressure.

2 · Baloney sandwich

Ingredients (tools/models/credits) → thin assembly (prompt/orchestrate/verify) → finished artifact. Hard part = adverse selection on outputs. Variants A–H in §8c.

3 · Risk you’re paid for

Principal: career time & judgment at this company. Hedge: toil, re-discovery, silent model failure via agents/gates.

4 · Costs vs edge (Law 7)

Some edge, high solo costs (attention, RM, learning). Firm = cheaper structure for mentorship, stability, density, hard problems.

5 · Motivation (Law 1)

Paid to learn · stability · structure · innovation · founder expertise · collective work hours of the team.

6 · Colonize adjacent

DS → text/vision (deepfakes) → hardware/Think2Earn → competition win rate → carolcalin.com → this seat as next tile.

7 · Hiring adverse selection

Don’t be residual inventory. Public artifacts, contested results, kill list of failures, fast falsifiability for employer.

8 · NoCap / capital discipline

Credits as bankroll; orchestrator as risk system; pre-registered keep/kill; honest self-baseline.

9 · Bayesian process

Prior → LR from pre-registered evidence → posterior ship/kill → freeze into new prior (defaults, runbooks, model map, firm priors).

10 · Phrase embeds

adverse selection · personal edge · market maker · expected value terms · common failure mode · prop trading · risk tolerance · financial markets.

Master close (optional): “I treat decisions like a trader: know why I’m here, know my edge versus the marginal participant, admit costs, take the risks I’m paid for, and update beliefs with evidence. Solo, my costs dominate; at EquiLibre I can buy structure, mentorship, and hard multi-agent problems — DeepStack-grade imperfect-information learning applied to markets — and put my assembly-line skills to work on something denser than a one-person kitchen.”

Company deep-dive: §0 EquiLibre / DeepStack.

13 Landmines to avoid

14 Source index (your 10 transcripts)

DateIDTitle (short)Why it matters for interview
2019-06zAdWY4KezZ8Laws of Trading — Better System TraderBook origin; Law 2 adverse selection; decision-making pitch
2021-09Dzh6Wc-VvqgPredicting Alpha — art & science of decisionsFull career story; mentors; incomplete info; retail advice
2022-01gKZbHsQRB8IEngineering compensation (CTO room)Hiring markets, incentives, org decision-making
2022-063BBNG0TlVwMTrading, crypto, adverse selection“Don’t trade” Straussian read; hiring as adverse selection; crypto
2022-08c1VAqJv1p4sDerivative — edge + laws roleplayProp-firm crypto greenlight exercise; edge application
2024-02CEjrwbgBQ8IAudiobook preview — Laws of TradingAaron Brown foreword; jungle framing; formal book voice
2025-07UmCRYENRp7YHow to find edgeEdge definition; quant structure; crises; gamblization
2025-076PX9JnyFTG8How quant firms took overCompact Jane Street / talent / incremental edge clip
2025-12Wxndr3Ady24Outlier — why you should (not) tradeTable selection; baloney sandwich; retail vs MM
2026-04ayqbZirKPkMOutlier — building a trading strategyLive critique style; systematic spectrum; strategy hygiene

Full text: equilibre/transcripts/ · Deepgram JSON: equilibre/deepgram/

90-second pre-interview checklist

  1. EquiLibre: lab-first RL trading · DeepStack lineage · 3 founders · Prague · Tower partnership · continual multi-agent adaptation.
  2. Motivation (Law 1): paid to learn · stability · structure · innovation · founders/team · collective hours.
  3. Edge: vs marginal AI user (tools, envelope, benchmarks) + colonization proof + one competition result.
  4. Costs (Law 7): edge real, solo costs high → firm improves edge/cost; not “I have nothing.”
  5. Risk paid for: time/reputation here; agents hedge unpaid toil.
  6. Sandwich or NoCap: one finished-artifact example + adverse selection on outputs.
  7. Hiring AS: artifacts + contestability + “you’d know fast if wrong.”
  8. Bayesian: prior → evidence → posterior → new prior (defaults/runbooks/team).
  9. Question for them (continual learning / DeepStack transfer / keep-kill culture).
  10. Energy: curious peer, honest uncertainty — not fan, not retail tips seeker.
Closing energy: You know why you’re at the table, what you bring, what costs too much alone, and what risk you’re willing to take with your time. That’s Law 1 + 3 + 5 + 7 in one posture.