jane street
for algorithm engineers
Why this scored 0
every term, weightedIts fastest-moving item, measured against the pace of its own source
Whether that velocity is itself speeding up, as a per-hour rate
How many independent communities its own items come from
Decays to zero over 14 days, counted from when we first saw it
Subtracted once something is big and old — sized by its biggest item, aged from when we first saw it
Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On an entity's first sighting there's no previous reading to compare against, so acceleration starts from a neutral prior rather than a measurement, and velocity falls back to engagement over its whole lifetime until a second reading exists. Full methodology
Signal history
7-day window (free)The evidence
The live items this entity's score aggregates — every community independently talking about it right now. This is the corroboration, shown, not claimed.
- 117
Solving the Jane Street reverse engineering challenge
Solving the challenge reveals low-level optimization tactics relevant to high-frequency trading code. · for algorithm engineers
hackernewsSteadydevtools38d ago - 216
Jane Street suffers $15B hit after meltdown at Situational Awareness
Jane Street lost $15 billion after a situational-awareness system failure, highlighting risk-management fragility. · for quant traders, risk engineers
hackernewsSteadybusiness58d ago