In Young Cho on Trading Research and Finding Signal in Financial Data

In Young Cho and Ron Minsky discuss the blurred lines between trading, research, and engineering, and why machine learning in markets is difficult.

IYIn Young ChoInvitado · Jane Street
Canal
Jane Street
Publicado
12 mar 2025
Vídeo
59:46
Lectura
8 min
Original
inglés
Abrir en YouTube
Al desplazarte, el vídeo se reduce a la esquina inferior derecha y sigue reproduciéndose. Los subtítulos siguen tu idioma de lectura.
Idioma de lecturaDisponible en 2 idiomas
Este artículo aún no está en español, así que se muestra el original en inglés.
RESUMEN

En 30 segundos

Jane Street researcher and trader In Young Cho joins Ron Minsky to trace a trading idea from exploration and data collection to modeling and production. They discuss research tooling, reproducibility, low signal-to-noise financial data, regime changes, hardware constraints, and the firm’s machine-learning ambitions as described in 2025.

  1. 1Why counterparties matterKnowing a large client’s trading context can help a market maker assess impact and offer execution services.
  2. 2The research pipelineCho describes exploration, data collection, modeling, and production as related parts of a trading idea.
  3. 3Flexibility versus robustnessNew hypotheses need fast experimentation, while established systems benefit from production-grade controls.
  4. 4Reproducible researchNotebook state, changing datasets, and expensive reruns make reliable comparisons difficult.
  5. 5Signal in noiseCho uses a metaphor of abundant data with only a small unknown useful portion; markets also change as patterns are traded.
  6. 6Hardware shapes modelsAt short horizons, latency and throughput constraints can determine which models are practical.

Conclusiones

  1. Trading research, software engineering, and real-time decisions often overlap in the same role.
  2. Exploratory research benefits from quick iteration, while production systems require reliability and careful validation.
  3. Financial datasets require attention to corporate actions, survivorship bias, and other data-quality problems.
  4. Reproducibility matters during research as well as deployment, especially when notebooks and data sources can change.
  5. Market data contains substantial noise and can change as participants trade away patterns or the world enters a new regime.
  6. Model design must account for inference latency, throughput, and hardware constraints, not only predictive accuracy.
TEXTO COMPLETO

Lee el texto editado por capítulos

Solo la transcripción
01

From internship to trading

Cho recounts her path from pre-med studies to Jane Street. She describes learning technical skills and working with clients.

Ron Minsky introduces In Young Cho, a Jane Street researcher and trader who helps lead machine-learning work. They discuss her path into trading, how research is done, and what makes financial modeling distinctive.

Cho initially expected to become a doctor, while also pursuing competition mathematics. After deciding medicine was not right and trying internships in several industries, she heard friends praise Jane Street’s interview process and decided to try it.

The interviews were challenging enough that she felt mentally exhausted, but she enjoyed the experience. Despite knowing little about finance, she accepted an internship and eventually joined full-time after undergraduate study.

The internship offered a new puzzle or skill to learn each day. Cho valued both the work and the support of smart, intellectually humble colleagues who invested in helping interns learn and make the most of their abilities.

As a quantitative trader, Cho learned OCaml, VBA, shell tools, SQL, financial terminology, and how to speak to brokers. She recalls picking up a call and shouting “park” because she did not know it was a button on the phone.

02

Clients, markets, and the trader’s role

A pension fund example explains why a market maker might value information about a counterparty. Trading blends live decisions, software development, and research.

Minsky asks why a technology-oriented trading firm takes broker calls at all. Cho explains that around 2013 Jane Street began building more direct client relationships alongside trading anonymously on electronic exchanges.

A large pension fund rebalancing an index portfolio illustrates the difference. A market maker seeing a large stream of anonymous buying may not know its full size or whether it reflects information the market maker lacks, and may quote more conservatively.

Knowing the client and the intended trade can help the firm estimate impact and provide pricing or execution advice. Minsky notes that information about a counterparty can be valuable to both sides when the trade is a routine portfolio rebalance rather than an informed bet.

Cho also wrote tools to visualize trades and analyze past opportunities. She describes these activities as a mix of software engineering, research, and live trading, even though they were all part of a trader’s day-to-day job.

Minsky adds that live trading also includes real-time decisions about automated systems and their behavior, not just calls with a counterparty. Both speakers note that the title “trader” can mean different things at different firms.

03

Research from idea to production

Cho breaks down exploration, collecting data, modeling, and making trades in production. Minsky and Cho discuss simulation versus flexible exploratory tools.

Asked what research looks like, Cho outlines a process beginning with exploration. Interactive tools must display information quickly and clearly so a researcher can develop and discard hypotheses without a long delay.

For the pension-fund example, exploration might involve examining the client’s portfolio and public filings to understand changes in positions and possible order flow. The purpose is to form a view of likely market impact and what price can be offered.

A hypothesis might be that most of a client’s trades have little impact but a particular position moves the market. Testing it requires collecting possible trade dates, sizes, times, and returns, along with other relevant information.

Minsky stresses the infrastructure needed to handle stock splits, ticker changes, and errors. Cho says manually building a small dataset can be a useful way to learn where errors arise before working with millions or billions of rows.

The modeling stage asks what to predict and which features matter. With a handful of observations, a simple linear regression may be preferable because a more expressive model can overfit. Larger datasets and complex interactions may justify more sophisticated methods, including deep learning.

A model and apparently credible out-of-sample predictions are only part of the job. Productionizing means deciding how to express the prediction in the market and ensuring the technology actually executes the intended trade reliably.

Minsky distinguishes two styles: simulate something close to a production trading system, or study a simplified version of the problem and later translate the result into production. He asks how Cho weighs those approaches.

For a new market or low-conviction idea, Cho prefers flexibility and fast hypothesis iteration over building a complete production system first. But quick studies made with nonproduction tools can later create reliability and deployment difficulties.

A mature system provides a robust experimental environment, but even a small change may require learning a large library ecosystem. Neither approach is inherently better; the right balance depends on the maturity of the work, the market, and the research question.

Minsky says some desks naturally research by changing their existing algorithmic systems. Simulation still has costs, including processing huge quantities of raw data. Lightweight summaries and short iteration times matter because many research ideas will fail.

04

Training and modern research tools

They contrast older hands-on research with newer datasets and visualizations. Training starts from fundamentals, and data still needs verification.

Cho compares the evolution of research to a sketch gradually becoming a detailed painting. Earlier tools supported cruder studies, but an individual could understand each stage closely, from the meaning of every dataset column through regression and the trading implementation.

That hands-on experience was educational even when the work looks primitive in retrospect. As the tools and models became more capable, preserving that intuitive understanding for new researchers became harder.

Cho says training starts with fundamentals rather than presenting the full abstraction immediately. New traders build an understanding of individual dynamics before combining them into a strategy; researchers may spend time learning to read one example visualization before confronting hundreds.

Their tools have improved substantially. Cho estimates a study that took a week a decade earlier might take ten minutes with current tools, though the increased capability also brings complexity.

Data infrastructure must account for corporate actions, stock splits, ticker changes, and historical universes. Simply looking at companies that exist today can introduce survivorship bias when reconstructing what traded many years ago.

The firm’s tooling can attach metadata such as market capitalization, volatility, and internal historical valuations to observations at the right times. Cho nevertheless urges researchers to trust but verify: check data and report suspicious results rather than assume every value is flawless.

Visualization tools can inspect market events at finer time scales and build interactive historical or real-time plots. Minsky contrasts this with manually manipulating spreadsheet rows and using basic graphing controls.

05

Notebooks and reproducibility

Python notebooks make exploration interactive but can be difficult to reproduce or productionize. Both speakers argue for collaboration across research and engineering.

Researchers can draw on libraries of tree-based models, deep-learning models, and specialized regressions. Python notebooks make it easy to organize an interactive study and annotate the reasoning behind code, but were not designed as production systems.

Minsky finds notebook execution order frustrating: cells can be run in an arbitrary sequence, leaving visible code inconsistent with the state that produced a result. Reproducibility is also difficult because large research jobs can be too expensive to rerun casually.

Cho describes the tension between researchers wanting quick changes and engineers needing reliable, performant systems. People who work across both domains can bridge the gap and prevent those differences from becoming territorial.

Minsky argues that reproducibility is necessary inside research too. If a model changes, researchers need to know whether the experiment changed one intended variable or several things, such as underlying data sources and code, at once.

Cho agrees that hard experience often teaches this lesson. At Jane Street the boundaries between research and production roles are not rigid, and people who understand both can help build better tools and mutual understanding.

06

Machine learning in markets

The speakers compare discipline in small and large data regimes. They discuss interpretability, noise, market competition, and regime change.

The conversation turns from simpler linear models to neural networks and tree-based approaches. Cho notes that researchers accustomed to small datasets and strong prior intuitions must change habits as models and datasets grow.

When data is scarce, researchers may restrict the hypotheses they test and preserve as much data as possible for fitting. With larger, more complex models, Cho stresses discipline around training and validation sets, out-of-sample evaluation, and avoiding duplicated hypothesis searches across groups.

Minsky frames these as different forms of discipline: constrain the model and hypotheses in a low-data setting, or use careful data and evaluation procedures when models are less interpretable. Cho says the shift can be uncomfortable for researchers who want an intuitive story for model behavior.

A simple model may be understandable enough to adjust after an unusual event such as a pandemic. Minsky calls this a form of intervention-oriented interpretability: understanding the model sufficiently to decide how to change it when the world changes.

Cho describes financial machine learning as unusually hard. Her metaphor is having 100 units of data of which only one contains useful signal, without knowing which one. It is an illustration of low signal-to-noise, not a measured ratio.

Millions of interacting participants determine prices for thousands of instruments, so any feature set may explain only a small fraction of returns. Minsky adds that market participants trade against observable regularities, which can remove the very patterns researchers learn from the past.

Cho calls this an anti-inductive property of markets. Unlike a stable benchmark, financial data can shift after crises or other events; sometimes the market operates differently because the world itself has changed. A robust model must cope with such regime changes.

07

Hardware constraints and future directions

Trading models must match latency and throughput constraints. Cho and Minsky discuss scaling, transfer learning, multimodal data, and tools for employees.

The firm handles tens of terabytes of market data per day, Minsky says, and predictions span very different time horizons. Some systems care about changes on the order of ten nanoseconds, while other decisions involve humans and much longer time scales.

Cho says hardware is not an afterthought for the fastest models. Latency and throughput limits can determine the design problem: first understand what can be served on available hardware, then seek the best model within those constraints.

Minsky lists CPUs, FPGAs, GPUs, different memory systems, interconnects, and storage as relevant constraints. He connects this to the broader machine-learning lesson that architectures which scale efficiently on available hardware can become especially powerful.

He does not think scale makes prior knowledge irrelevant to every trading problem. In data-poor domains, researchers can carry insights from related markets; elsewhere the ability to scale changes both model and hardware choices.

Asked about the future, Cho is cautious about predictions but excited about recent progress. She says Jane Street had built access to thousands of high-end GPUs and improved its understanding of models, data, and serving hardware.

The firm records large quantities of market and other data and has advanced its use of deep neural networks for prediction. Cho expects further work on transferring knowledge from well-understood asset classes to data-scarce ones and combining market data with text or images.

Minsky distinguishes extracting information from familiar modalities such as text and images from modeling financial time series directly, where much relevant practical work is not published. He expects multimodal and reasoning advances to create opportunities across the wider trading process.

Both are also interested in tools that make employees more effective: assistants or agents able to work with unusual internal languages, systems, and datasets. Cho says decisions about what to build, fine-tune, or obtain from partners remain difficult and open.

Más de este canal

1:48:29EN
JSJane Street· 16 oct 2026How AI Is Changing Programming: John Krazit and Ron MinskyRon Minsky, John Krazit · Jane StreetJane Street’s AI tooling lead and the Signals and Threads host examine agent infrastructure, security, code review and the changing experience of writing software.Agentes de programaciónDeveloper productivityEvaluaciones+2
1:36:37EN
JSJane Street· 23 sept 2026Aaron Bauer on Teaching Software Engineering in the Age of AIRon Minsky, Aaron Bauer · Jane StreetHow learning goals, active practice and editor design shape engineering education when models can generate the code.AI in EducationSoftware engineeringEducation+2
9 diapositivas1:05:45EN
JSJane Street· 11 sept 2026Cyrus Omar on Live Programming and a Computational Commons for Humans and AICyrus OmarA demonstration of Hazel shows how immediate feedback, structured collaboration and carefully scoped permissions could support people and AI agents working together.Programming LanguagesHuman-AI CollaborationFlujos de desarrollo y pruebas+2
1:25:00EN
JSJane Street· 2 sept 2026Eric Mannes on Turning Messy External Data Into Trading ResearchRon, Eric Mannes · Jane StreetFrom commodity futures and an Excel risk system to point-in-time datasets and AI, Eric Mannes explains the domain knowledge behind data engineering at Jane Street.Data quality & curationFlujos de desarrollo y pruebasInvesting+2
7 diapositivas1:16:29EN
JSJane Street· 26 ago 2026Grant Sanderson and Alok Puranik: Positional Encodings Through Group TheoryGrant Sanderson, Alok Puranik · 3Blue1BrownStarting with assumptions about attention, they derive matrix exponentials and connect rotations, decay and Jordan blocks to RoPE and ALiBi.Transformers & attentionMathematicsFundamentos de ML+1
27:39EN
JSJane Street· 21 ago 20263Blue1Brown and Jane Street on Trading, Machine Learning and CultureGrant Sanderson, Nitya, In Young, Craig, Alok · 3Blue1BrownGrant Sanderson talks with Jane Street colleagues about market making, shared compute, research and the paths that brought them to the firm.Machine LearningFintechCompany Culture+2