QuantInsti (@QuantInsti) header
QuantInsti (@QuantInsti) profile picture

Empowering traders with Quant & AI skills. 📈

India
Joined October 2012
1 nanosecond in HFT, stretched to 1 second, makes a blink of an eye last about 10 years. Sameer Kumar (iRage), Stefan Jansen (@ml4trading), @G2GAjaySharma, Tony Lee (Alpaca) and Mridul Arora (Elevation Capital) at our Algo Trading Conference 2026 👇 #AlgoTrading #HFT #QuantTrading
3
11
4,374
8 free data sources we use to check market claims. From daily fed funds back to 1954 to S&P earnings and CAPE back to 1871. Links in the reply. These are the sources behind this series of posts. What would you add?
4
5
471
Buying the S&P 500 at an all-time high has done about as well as buying on any day. Since 1950, the next 12 months averaged +8.7% after a record close and +9.4% after any day. Record days cluster, so the sample is smaller than it looks. History, not a forecast.
5
2
325
Method: S&P 500 price index (no dividends), Yahoo Finance daily closes. A record close = above every close since 1927. Return = next 252 trading days. Start dates 1950 to Oct 2025: 1,315 record days of 19,068. 2026 had 28 record closes by 16 Oct. Reply if you want the code.
1
88
Momentum's 10 worst months since 1929: 9 came as the market bounced after a two-year fall. Aug 1932 -53%. Apr 2009 -34%. Daniel and Moskowitz (2016) found this. It holds on Ken French data to Aug 2026. The beaten-down losers jump most, and momentum is short them.
4
3
482
Backtest, Jan 1929 to Aug 2026, Ken French US momentum factor (winners minus losers), before costs. Rebound = market down over the past 24 months, up that month. A caution: the factor earned 0.6% a year since 2000, vs 7.7% before. Past results do not predict future returns.
1
127
The Fed's September hike was its first after a run of cuts. That has happened 6 times before since 1990. A year later the S&P 500 was higher in 5 of 6. But the median gain was 5.2%, vs 11.8% for any 12 months since 1990. Six cases is far too few to lean on.
3
342
Method: target-rate changes since 1990 from the Fed's open market operations pages. First hike = a rise right after a cut (1994, 1997, 1999, 2004, 2015, 2022). S&P 500 price index, decision-day close to a year later. History, not a forecast. Not investment advice.
121
"Buy when the VIX is above 30" looks great if you count days. The VIX closed above 30 on 734 days since 1990. The S&P 500 was higher a year later after 87% of them. But that's only 22 separate scares. Of the 21 with a full year, 14 were higher (67%). Any day: 81%.
2
2
387
Method: VIX and S&P 500 price index via Yahoo, 1990 to Oct 2026. Episode = first close above 30 after 60+ sessions without one; 12 months = 252 sessions. A 20-session rule gives 62%, 126 gives 80%. 21 cases, a small sample. History, not a forecast. Not investment advice.
1
118
"Sell in May" mostly faded after the paper that made it famous. Bouman and Jacobsen published the Halloween effect in 2002. S&P 500, 1950 to 2002: Nov to Apr beat May to Oct in 35 of 53 years. Since 2003: 12 of 23, a coin flip. May to Oct still averaged +4.3% since 2003.
4
3
424
Method: S&P 500 price index (no dividends), month-end closes, May 1950 to Apr 2026. Each year pairs May to Oct with the Nov to Apr after it. Averages: +7.4% vs +1.1% to 2002, +5.9% vs +4.3% since. 23 years is a short sample. History, not a forecast. Not investment advice.
97
The S&P 500 was higher a year after every US midterm election since 1950. All 19 times, average gain 15.1%. The same date in other years: up 38 of 56, average 7.3%. 19 cases is a small sample, and part of the gap is the Nov to Apr season. A base rate, not a forecast.
4
1
425
Method: S&P 500 price index (no dividends), close on election day to the close a year later, midterms 1950 to 2022. Other years: the same November date in the 56 non-midterm years, 1951 to 2024. Data: Yahoo Finance ^GSPC. History, not a forecast. Not investment advice.
131
Python or C++ for a quant career? It depends which seat you want, and the answer is clearer than the arguments online. Researcher: Python. pandas, NumPy, statsmodels, scikit-learn. How fast you can try ideas matters more than how fast they run. Trader: Python for analysis, plus the desk's own tools. Mental maths matters more than either language. Developer, low latency: C++. Memory, cache behaviour, networking, Linux. Here microseconds are the job. Developer, research platform: Python plus one compiled language, and strong testing habits. Risk: Python and SQL. If you don't know your seat yet, start with Python. It's the shared language between research and everyone who uses it. Add C++ when a role asks for it.
1
6
963
What a new quant hire gets judged on in the first 90 days. It isn't alpha. Nobody expects that in month one. What people watch for: • Did you learn the data before you trusted it? • Did you ask before assuming? • Did you finish something small, end to end? • Can you reproduce your own result when someone asks on day 40? The fastest way to lose the room is a number you can't reproduce. The second fastest is a model built on a column nobody told you was backfilled. Ask what every field means and when it lands. Most first-quarter wins are unglamorous: a data check that caught a bad feed, a test someone else can rerun, a note that saved a colleague a week. Send this to someone starting a quant job this year.
4
3
524
What does a quant earn in India? Anyone who gives you one number is guessing. Published ranges put entry-level quant trader roles around ₹20 to 35 lakh, and quant developer roles starting near ₹14 lakh, with experienced seats quoted well above both. The band is wide because three things move pay more than the title does: • Firm type: bank, fund or prop desk • Asset class, and the desk's own P&L • How the variable part is decided Two developers at one firm can sit in different bands, one priced against research and one against systems engineering. So treat any figure as a reference point, not a rate card. Ask which track a seat sits in and how the bonus is set before reading anything into the number. Published ranges and the caveats behind them: quantinsti.com/articles/quan… and quantinsti.com/articles/quan…
1
601
Five things that get quant CVs passed over, and the fix for each. 1. A Sharpe ratio with no test period. Fix: state in-sample and out-of-sample, with costs. 2. "Built an LSTM to predict stock prices." Fix: say what you predicted, against which baseline, and whether it beat it. 3. Every tool you've ever touched. Fix: list only what you could be quizzed on for 20 minutes. 4. One CV aimed at every quant seat. Fix: one version per seat. 5. Certificates in the top half. Fix: projects first, certificates last. The common thread: a reviewer wants evidence you know where your own result could be wrong. Which of these was on your last CV?
3
2
523
A reviewer gives your quant GitHub about two minutes. They're rarely looking at the returns. They're checking whether you handled the boring parts, because the boring parts are the job: • Data source and date range stated • Rules written down before the test • Costs and slippage applied • A test period you never touched while building • A README that says what you'd do differently Six projects that give a reviewer something to ask about: 1. Momentum on 50 stocks, run on today's index members and on point-in-time members 2. A pairs trade, plus the test that showed when the pair broke 3. A backtester that handles splits, dividends and missing days 4. An options P&L explained day by day through its Greeks 5. A limit order book simulator in C++ or Python 6. A cost study: how much edge a simple strategy needs to survive fees Three finished projects beat nine certificates. And a failed backtest, written up properly, is often the best one to show.
2
534
What does a quant trader actually do all day? The algos place the trades. The day goes on checks: positions vs the broker, every fill, a lookback tweak that failed out of sample, one strategy at 92% of its risk limit. A simulated desk day in 54 seconds.
1
1
445