Zoe Weil on ranking that moves you, not finds things
Sequen reranks retail products in real time from the signals most systems ignore, such as hover time and scroll speed, to influence behavior in a high-intent moment, judging itself by what people buy rather than what they click.
You Can't Unsee It
For its entire history the field tried to help people find things faster; Sequen rejects that goal and instead tries to influence a shopper's behavior in the moment they already have high intent.
that is really the golden thread because once you realize it and you see, hey, even though you're operating in the search space, you're not trying to help people find things, you can't unsee it.
The Papers Don't Transfer
The biggest advances in ranking are published by social media companies, but a Wayfair or Priceline scientist who implements those papers gets a fraction of the lift, because the method was tuned to data they will never have.
It doesn't drive the same outcomes for you as it does for them because you don't have the data that they have.
Large Event Models, Not an LLM
Sequen's starting point was a model that generalizes to human behavior the way a language model generalizes to text, built deliberately without any large language model or generative AI.
it's not a large language model. We actually don't use large language models anywhere. That's not our business whatsoever.
Look Between the Clicks
Most teams optimize the rare explicit signals, a click or a thumbs-up; Sequen relies overwhelmingly on implicit micro-signals like dwell time, scroll speed, and how many times you go back and forth before the cart.
I'm talking about hovers, scrolls. I'm actually talking even deeper than that. The speed of a scroll, right? The dwell time on a hover.
You Are a Session, Not a Name
To Sequen a user is a collection of events in a live session, not a stored identity, so there is no name, location, or cross-site profile to hold onto in the first place.
When I think about a user, think about it as a collection of events in a session. I don't care if you're John Smith or Adam, whatever.
Under 50 Milliseconds, in Rust
Cleaning raw events, passing them through hundreds of models, and serving a re-ranked page in under 50 milliseconds at thousands of requests per second is what forced the core backend into Rust rather than Python.
the core of our backend is all in Rust. So no, I can definitively say we could not have done it in Python at all.
Residual Knowledge Beats the Algorithm
Making these models work takes an innate sense of which features drive value that is not written in any research paper, so Sequen hires it out of big labs and codifies it into a reusable knowledge base.
requires you to have an innate understanding of what features drive value and that is not written in any research paper.
Why It's Called Recursive
Early on Sequen retrained ranking models from scratch, sometimes hourly; the recursive stack instead learns continuously with small updates layered on prior ones, compounding gains at a fraction of the compute.
you don't have to rebuild the entire ranking stack every time