A plain-English wiki to the roles, skills, and technologies behind the world's most elite trading firms — Citadel Securities, Jane Street, Hudson River Trading, and D. E. Shaw. Built for the recruiter who has never written a line of code or placed a trade.
Before we list job titles, let's demystify the business. Quantitative (or "quant") trading firms are part hedge fund, part research lab, part high-performance software company. They don't pick stocks the way a traditional investor would — they write mathematical models and computer programs that buy and sell millions of times a day. Every role you'll be recruiting for exists to support that core idea.
Citadel Securities, Jane Street, and HRT are market makers. Think of them as the wholesaler at a busy marketplace — they are always willing to quote a buy price and a sell price for a stock, option, or ETF. They earn a tiny sliver on each trade (the "spread") and do it billions of times a year. D. E. Shaw is slightly different — it's a hedge fund that invests its own capital using similar quantitative methods.
Systematic means rule-based and automated. A model — written in code — decides what to buy, sell, when, and how much. No human clicks the button. Most of what these firms do is systematic. Semi-systematic means humans still sit on a trading desk and oversee the models, intervening in unusual markets. Discretionary (the D. E. Shaw side) means humans make the final call, with software helping them.
Because they are tech companies that happen to trade. The edge isn't usually one brilliant idea — it's faster computers, cleaner data, smarter math, and better engineering. That's why they recruit physicists, PhDs, compiler engineers, FPGA designers, and Olympiad winners. Pay is high because the firm competes with Google, OpenAI, and DeepMind for the same talent.
These four firms sit at the top of the quant trading world. They compete fiercely with each other for the same small pool of talent — frequently the same candidates receive offers from all four. Understanding each firm's flavor will help you position opportunities and read candidate signals correctly.
The largest retail market-making business in the U.S. Founded by Ken Griffin. Hires heavily for semi-systematic traders, ML researchers, and C++ engineers. Core languages: Python & C++. Founder-CEO Peng Zhao is a quant researcher himself.
Famous for puzzles, functional programming, and a deeply academic culture. The single largest user of OCaml in industry. Trading, Research, and Machine Learning operate as one collaborative quant team. A strong culture of humility and intellectual rigor.
14 offices worldwide, one of the most latency-obsessed firms on earth. Distinctive role split: "Algo Developer" (quant researcher) vs. "Core Developer" (systems engineer) vs. "Algo Engineer" (hybrid). Heavy C++, Python, FPGA, and custom network hardware.
Founded 1988 by David Shaw. Both systematic (Quants write models) and discretionary (humans invest, tech assists) divisions. Legendary for hiring Math Olympiad and Putnam winners. Signature title: "Quantitative Analyst" rather than "Quant Researcher."
You will hear these words in every interview, résumé, and job description. Memorize the plain-English meaning — not the textbook one — and you'll hold your own in any conversation with a hiring manager.
Traders make real-time decisions about risk. At Citadel Securities and Jane Street, most trading is automated — but humans sit behind the models, watching unusual markets and intervening when needed. These roles mix sharp probabilistic thinking with a stomach for uncertainty and a willingness to work fast under pressure. Most firms do not require any finance background on day one.
A Quantitative Trader sits on a trading desk and oversees automated strategies in live markets. They watch screens full of numbers, decide when to turn strategies on or off, adjust risk limits, and step in when markets become unusual — think Fed announcements, crashes, or unexpected news. They work hand-in-hand with Quant Researchers to identify what's breaking, what's working, and what new strategies the firm should pursue.
Strong candidates exhibit mental math speed, comfort with probability puzzles (think Jane Street's interview guide — coin flips, expected value, Bayesian reasoning), ability to program at a working level (Python primary, SQL, sometimes kdb+/q), composure under pressure, and intellectual honesty when a strategy goes wrong.
An ETF or Equities Trader specializes in the largest, most liquid instruments in the world — exchange-traded funds, single stocks, and their derivatives. They quote tight prices to institutional clients (pension funds, asset managers), manage the firm's inventory risk, and understand the mechanics of how ETFs are "created" and "redeemed" with their underlying baskets of stocks.
Deep understanding of primary markets (how ETFs are created and redeemed), client relationships with institutional asset managers, and the ability to price risk across correlated baskets of securities. Less coding-heavy than a quant researcher role; more relationship and product-intuition heavy.
Options traders price and hedge "derivative" contracts — instruments whose value depends on the movement of an underlying asset. Every major market maker runs an options desk. Traders manage complex risk exposures nicknamed "Greeks" (delta, gamma, vega, theta) and constantly adjust hedges as markets move. This is one of the most mathematically intensive seats on a trading floor.
Fluency with implied volatility surfaces, skew/smile, term structure, Monte Carlo pricing. Strong candidates can whiteboard a binomial tree pricing model, explain why a 10-delta call in biotech behaves differently from a 10-delta call in utilities, and discuss gamma hedging in practice.
Institutional Sales & Trading (IS&T) professionals are the client-facing face of the firm. They work with hedge funds, pension funds, insurance companies, and asset managers who want to trade in size — executing block trades, providing market commentary, and helping clients express views efficiently. Unlike retail-facing brokers, these professionals speak the language of portfolio managers and institutional execution.
Strong capital markets fluency across ETFs, fixed income, or equities. Series 7 & 57 licenses typical. Excellent written and verbal communication, client-service instincts, composure under pressure. Coding is optional but Python literacy is a plus.
At D. E. Shaw and inside Citadel's parent fund, there are also discretionary traders — humans who make investment decisions using fundamental analysis (reading filings, modeling cash flows, visiting management teams) while leaning on the firm's quantitative and technology infrastructure. They manage portfolios in areas like corporate credit, macro, energy, fundamental equities, and private investments.
Deep industry knowledge in at least one sector, ability to build three-statement models, credit analysis, comfort reading SEC filings and bond prospectuses. At D. E. Shaw specifically, they hire across asset-backed, corporate credit, discretionary macro, energy, renewable energy, and fundamental equities teams.
A Trading Desk Operations Engineer is a hybrid seat — part trader, part engineer. They sit on the desk during market hours, monitoring live strategies, fielding alerts, and troubleshooting why something isn't trading correctly. After markets close, they write code to prevent those problems from happening again. Jane Street calls this role TDOE. At HRT the team is called Trade Operations. D. E. Shaw calls it Trading Systems Ops.
TDOEs need fast Python skills for ad-hoc analysis, Linux command line fluency, SQL for investigating trade data, familiarity with FIX protocol (the industry standard for order messages), and cool-headed incident response. Jane Street explicitly lists this as a great role for candidates who want to blend technical depth with market exposure.
Quantitative researchers are the scientists of the trading firm. They find patterns in noisy data, build mathematical models, and translate those models into code that can make trading decisions faster than any human. Every firm has a slightly different taxonomy — Citadel Securities and Jane Street use "Quant Researcher," D. E. Shaw uses "Quantitative Analyst," and HRT uses "Algorithm Developer" — but the DNA is the same: mathematics PhDs or top-of-class STEM graduates who can ship production code.
A Quantitative Researcher studies markets like a scientist studies physics. They observe patterns, form hypotheses, test them on historical data, and if the results hold up, ship a model that trades real money. A typical day involves reading academic papers, cleaning petabyte-scale datasets, writing Python or C++ to test ideas, and presenting findings to a small team. At Citadel Securities, Jane Street, and HRT, researchers are compensated on the P&L their strategies produce.
Advanced degree (MS/PhD) in math, statistics, physics, CS, or EE is typical. Strong candidates demonstrate rigorous scientific method, comfort with messy real-world data, fluency in probability and linear algebra, and the humility to discard their own best ideas when data doesn't support them.
ML Researchers apply modern deep learning, reinforcement learning, and large-model techniques to trading problems. Think: training neural networks on enormous order-book datasets, using NLP to extract signals from news and filings, or building systems that predict price moves over microseconds-to-days horizons. Citadel Securities, Jane Street, and HRT all compete directly with DeepMind, OpenAI, and Meta AI for these candidates.
PhD in ML, CS, statistics, or physics. Publication record at NeurIPS, ICML, ICLR, or KDD is a strong signal. Experience with large-scale distributed training, GPU optimization, and "real-world ML" (not just Kaggle notebooks) matters. Financial experience is not required at top firms — they actively recruit from academic AI labs.
Strategy Developers own a trading strategy end-to-end — from initial research idea, through backtesting and validation, to live production, to ongoing monitoring and optimization. They combine the research mindset of a quant with the operational rigor of an engineer. Both D. E. Shaw (under "Systematic Investing") and HRT (under "Strategy Development") run this as a distinct role, often senior to pure researchers.
Strong mix of research rigor plus engineering maturity. Portfolio construction, risk modeling, transaction cost analysis (TCA), execution algorithms, capacity analysis. Able to discuss why a strategy generates returns — the economic story — not just the statistics.
Alternative data is one of the biggest arms races in modern trading. Firms buy or license hundreds of exotic datasets — satellite images of parking lots, credit card receipts, shipping container movements, app usage telemetry, weather data, web-scraped prices. The Data Scientist / DSG role is to evaluate new datasets, clean them, understand their quirks, and hand them off to researchers in a usable, trustworthy form. At Citadel this team is explicitly called the "Data Strategies Group"; D. E. Shaw runs a "DATA Associate" program for early-career hires.
Strong pandas / numpy, advanced SQL, data visualization, statistical thinking (understanding bias, coverage, sample selection). Curiosity about how datasets are generated — who collected it, why, and what's missing. Communication skills to explain data quirks to researchers and traders.
All four firms now have dedicated crypto research teams. Crypto is a different beast: 24/7 markets, dozens of venues (Binance, Coinbase, OKX, Bybit, DEXs), fragmented liquidity, on-chain data, MEV (Maximal Extractable Value), smart-contract risk, and far less regulation. A Crypto Quant Researcher builds strategies for this messy, fast-moving market — arbitrage across venues, market making on spot and perpetual futures, on-chain alpha mining, and cross-asset plays vs. traditional markets.
Microstructure experience matters — crypto perpetual funding rates, cross-venue arbitrage, basis trades, and understanding of market-making risks. Familiarity with on-chain tools (Dune Analytics, Etherscan, TheGraph). Awareness of counterparty risk — which exchanges to trust, custody best practices.
The bridge between researchers and production trading systems. A quant writes a model in a Jupyter notebook that works beautifully — but it's slow, uses too much memory, has hard-coded paths, and assumes no errors. The Quantitative Research Engineer rewrites it as a production-grade service: fast, monitored, tested, fault-tolerant, running inside the firm's risk framework. HRT calls this role "Algo Engineer"; Citadel calls it "Quant Research Engineer." Every firm has some version of it.
Dual fluency. Comfortable with stochastic calculus, regression diagnostics, and bias-variance trade-offs and with memory profilers, concurrency, testing frameworks, and CI/CD. Can read a research paper and implement it cleanly in production-grade code. Takes operational reliability seriously.
Engineers are the skeleton of a modern quant firm. Without them, the researchers would have no systems to run models on, no exchange connections, no risk controls, and no production code. These firms compete directly with FAANG for the best engineering talent — and often win, because the problems are harder and the feedback loop from deployment to profit is measured in microseconds. Software Engineer, Algo Engineer, Core Developer, Hardware Engineer — the job titles vary, but the common thread is extreme technical depth combined with the discipline required to work in a regulated, no-mistakes-allowed environment.
Builds the hot path — the code that receives a market data update, decides whether to trade, and fires an order. Every nanosecond matters. Engineers at this level obsess over cache lines, branch prediction, memory allocation, lock-free data structures, kernel bypass networking (Solarflare, Mellanox), and CPU affinity. The job is adversarial: every other firm is doing the same thing, so staying competitive means relentless profiling and optimization. HRT calls them "Core Developers"; others just say "Low-Latency C++ Engineer."
Modern C++ (move semantics, templates, concepts), deep knowledge of hardware (NUMA, cache hierarchies, branch prediction), lock-free programming, memory allocators, low-latency network programming, kernel bypass, perf / VTune / ebpf profiling. Multi-threading. Often some assembly literacy.
Builds the internal tooling — research platforms, strategy monitoring dashboards, backtesting infrastructure, data pipelines, deployment systems, configuration management. Not on the trading hot path but absolutely critical: a bad deploy or buggy monitor can mask real P&L risk. HRT has publicly written about their Python monorepo managing thousands of services. All four firms run massive Python codebases despite the "C++ firm" image.
Senior Python (type hints, asyncio, performance considerations), modern web frameworks, containerization, infrastructure-as-code, observability stacks (Prometheus, Grafana, OpenTelemetry). Strong testing discipline and experience with large monorepos. Some C++ / Rust literacy for bridging services.
Builds the front-end applications that traders, researchers, risk managers, and operations staff use every day — real-time dashboards showing positions and P&L, strategy control panels, data exploration tools, compliance interfaces. These are high-stakes internal apps where a UI bug can cost real money. Expect React or modern TypeScript front-ends talking to Python or Go back-ends, often with WebSocket streams pushing live market data. HRT's Fullstack team has publicly written about this work.
React with hooks, TypeScript with strict typing, state management (Redux, Zustand, TanStack Query), WebSocket streams, data-grid rendering at 60fps with thousands of rows, charting (D3, Plotly, TradingView). Back-end fluency — REST, GraphQL, protobuf — to build the APIs they consume. Design literacy matters.
The hardware engineer writes trading logic not in software but in silicon — using Verilog or SystemVerilog to configure FPGAs (Field-Programmable Gate Arrays). Because FPGAs execute logic directly in hardware, they can process a market data packet and generate an order response in ~100 nanoseconds or less — 10-100× faster than even the best C++ implementation. HRT publicly lists "Hardware Design Engineer" as a role. This is one of the rarest and highest-paid specialties in all of technology.
Verilog / SystemVerilog, RTL design, timing closure, synthesis, simulation (ModelSim, Vivado, Questa), understanding of digital signal processing, TCP/UDP offload engines, PCIe, deep understanding of networking stack. Low-level C++ literacy to interface with host systems. Pipeline design and parallelism in hardware.
The engineers responsible for the physical and virtual plumbing that makes a trading firm work: data-center servers, switch configurations, co-location cages inside exchange buildings, dark-fiber and microwave links between cities, time synchronization (PTP / GPS clocks to within nanoseconds), Linux kernel tuning, storage, observability. When trading systems are slow, when a production host goes down at market open, when an exchange changes a protocol — these are the people who fix it. At D. E. Shaw this group is explicitly called "Systems: Engineering."
Deep Linux internals — schedulers, cgroups, NUMA, huge pages, IRQ affinity, perf / ebpf / bpftrace. Networking stack expertise — switch configuration, BGP, multicast, PTP time synchronization. Infrastructure as code. On-call discipline and strong incident response. Vendor relationships (Cisco, Arista, Mellanox, Juniper).
Protects the firm from intrusion, insider threats, data leakage, and regulatory breach — stakes that can be firm-ending. Think of it as a fusion of software engineer, detective, and auditor. Scope spans endpoint security, network segmentation, identity and access management, secrets handling, code signing, software supply chain, insider threat monitoring, detection engineering, threat modeling, and incident response. Jane Street explicitly lists "Cybersecurity" as a dedicated department.
Offensive + defensive depth. Threat modeling (STRIDE / attack trees), detection engineering (Sigma rules, EDR tuning), identity platforms, secrets management, code signing, SBOM / supply-chain security. Scripting in Python, Go, PowerShell. Incident response muscle memory. Familiarity with MITRE ATT&CK, NIST frameworks, SOC 2 / regulatory audits.
Quant firms compete for a tiny pool of extremely specialized talent. LinkedIn alone will not get you there — every recruiter at every firm is fishing the same pond. The platforms below are where elite quant, research, and engineering candidates actually spend their time. Many have no LinkedIn at all, or keep their profiles deliberately minimal. Learning how to read a GitHub profile, a Kaggle leaderboard, or an arXiv publication list is a genuine advantage.
The fastest way to build fluency in any of these domains is to watch people explain them. Below are eight YouTube channels curated for non-technical recruiters — none assume a math or CS background to start. Watch one or two videos before a screening call and the jargon on the candidate's resume will stop being a wall.
A former CFA and investment analyst explaining finance in plain English. Perfect first watch for anyone new to markets. Covers hedge funds, short selling, crypto, market structure — all in the steady, well-sourced style of a patient teacher. No hype, no "get rich quick." Start with "How Hedge Funds Make Money" and "What is High Frequency Trading?"
Patrick is a retired hedge-fund manager and current finance lecturer. His videos cover trading firm history, market crashes, derivatives blow-ups, and current events with a characteristic dry humor. Excellent for understanding the culture and stakes of quant trading. Watch his videos on Jane Street, Renaissance Technologies, and the 2010 Flash Crash for maximum context.
A quantitative analyst who produces practical videos on getting into and navigating the quant industry. Topics include what an MFE really teaches you, salary expectations, how to talk about projects in interviews, what a quant resume should look like, and the real difference between quant titles at different firms. One of the few channels specifically addressing quant careers.
Walks through actual Python code for quantitative finance problems — option pricing, Monte Carlo simulation, portfolio optimization, backtesting. Useful for recruiters who want to see what "writing Python for trading" looks like in practice. The code style on-screen is similar to what a real quant would produce during a coding screen.
Not quant-specific, but the gold standard for Python tutorials online. If a candidate says "I use pandas every day" or "I write async Python," his videos will show you exactly what those skills look like in practice. Essential baseline for understanding what an engineering candidate is claiming on their resume.
Grant Sanderson produces some of the most beautiful mathematical visualizations on the internet. His series on linear algebra, neural networks, and probability give you intuitive footing for concepts that show up constantly in quant research candidate conversations. Watch "Essence of Linear Algebra" and "But What Is a Neural Network?" before any ML-researcher screening call.
Produces seminars and interviews with top practitioners applying machine learning to trading — including interviews with authors of foundational books like Advances in Financial Machine Learning. Higher technical bar than most channels on this list, but invaluable for understanding what ML-focused quant research looks like in practice.
Daily and weekly video analysis of FX, rates, and equity markets with a macro lens. Useful background for understanding how discretionary traders and institutional sales & trading desks think about market-moving events. Helps decode the difference between "rates sold off on the print" and "vol compressed into expiry" — phrases that might otherwise sound like a different language.
Disclaimer & Trademark Notice. This document, Recruiting for Quantitative Trading Roles, is an independent educational reference authored by Jolly Paily as part of the series FREE!! Open Source - A Technical Recruiter's Daily Wiki. It is not authored, sponsored, endorsed, reviewed, or approved by any of the firms referenced within.
Firm references. References to Citadel Securities, Jane Street, Hudson River Trading, and D. E. Shaw & Co. are made solely for informational and illustrative purposes to help non-technical recruiters understand the roles, skills, and hiring patterns that commonly appear in the quantitative trading industry. All firm names, logos, brand marks, service marks, job titles, and organizational structures referenced are the property of their respective owners. No claim of endorsement, affiliation, or partnership is made or implied.
Technology & platform trademarks. YouTube™ is a trademark of Google LLC. GitHub™ is a trademark of GitHub, Inc. Kaggle™ is a trademark of Google LLC. Stack Overflow™ is a trademark of Stack Exchange Inc. Hugging Face® is a registered trademark of Hugging Face, Inc. Google Scholar™ is a trademark of Google LLC. Python® is a registered trademark of the Python Software Foundation. C++ is a trademark of its respective owner. Linux® is a registered trademark of Linus Torvalds. All other tech stack logos, programming language marks, product names, and company names referenced (including but not limited to Bloomberg, kdb+, Verilog, SystemVerilog, Xilinx, AMD, Intel, Kubernetes, React, TypeScript, AWS, FINRA, SEC, CFA Institute) are the property of their respective owners. Their inclusion is purely illustrative of technologies and platforms that appear in job descriptions for the roles discussed.
Compensation & role accuracy. Role titles, team names, departmental structures, and any salary or compensation figures mentioned in this guide are approximations or community-reported ranges. They vary substantially by seniority, location, year, individual negotiation, and firm-specific practices. They are provided solely to help recruiters calibrate their conversations and should not be relied upon as guarantees or quoted to candidates as official figures.
Not investment advice. Nothing in this document constitutes investment advice, trading advice, legal advice, or a recommendation to buy, sell, or hold any financial instrument. Discussion of trading strategies, instruments, and firm practices is purely educational context for recruiters evaluating candidates. Readers considering any trading or investment activity should consult a qualified professional.
YouTube channel listings. Creator names, channel names, and subscriber counts referenced in the YouTube section are provided as publicly available reference points at time of writing and are subject to change. Their inclusion is solely a recommendation for educational self-study by recruiters and does not imply endorsement of any channel's broader content, nor does it imply that the channel creators endorse this guide.
Contact. Jolly Paily — LinkedIn: linkedin.com/in/jollypaily. Feedback, corrections, and suggestions for future guides in the series are welcome.