The alpha, twice a week
That was 3 min.
Get the best new moments in your inbox every Wednesday and Saturday. It's free.
Check your inbox
We sent a link to your address. Click it to finish signing up. Not there in a minute? Look in spam.
or
The TWIML AI Podcast · 3 min · Oct 15, 2026
Sequen chose Rust for low-latency feature serving
Zoe Weil says Rust's low-latency support made Python impractical for Sequen's feature transformations, though the team still uses Python for R&D. The example ties a language choice to its serving constraint.
Zoe Weil is co-founder and CEO of Sequen.

Sam Charrington, Host · Host, The TWIML AI Podcast
About this segment
Zoe Weil says Rust's low-latency support made Python impractical for Sequen's feature transformations, though the team still uses Python for R&D. The example ties a language choice to its serving constraint.
From “Optimizing AI Recommendations for Revenue with Sequen Founder Zoe Weil”, Oct 15, 2026. Watch the full episode
Thanks. We'll look at and fix what's off.
“I genuinely don't. I don't think that we could have because we, you know, ultra, ultra low latency feature transformations serving are so core to what we do.”
Takeaways
- Low-latency feature transformations are central to the backend.
- Zoe says Python could not meet the serving needs.
- The team uses Python for R&D and Rust for its core backend.
In this episode
Full episode- 4:17Retail ranking should optimize purchases, not just relevance7:35
- 15:52Sequen personalizes a session without tracking user identity2:57
- 39:29Recursive updates compound ranking gains without rebuilding models4:45
- 32:12Ad and organic revenue can rise together3:51
- 27:11Recommendation ranking changes after a shopper commits2:22
- 44:16Large mesh models relate multiple event streams2:31
18:53Sequen chose Rust for low-latency feature serving2:49
- 48:46Sequen is prioritizing ranking models over representations2:51Up next
Transcript
Transcribed by machine (Whisper) from the episode’s audio, so a word may be off here and there.
- 18:58
in trying to put this, you know, platform or environment in place? I think we got lucky in a sense because maybe, like, six, seven years ago. Rust didn't have a ton of support in, like, open source AI libraries like Hugging Face. That began to change rapidly in the past, I would say, three to four years. And, you know, this is why I always say whenever you make a successful startup, like, there's quite a bit of luck there as well.
- 19:33
Timing is everything. Yeah, timing is everything. We got very, very lucky because we started building this company at a time when support for Rust and many, many open source frameworks, AI, ML frameworks. You think you could not have done it in Python? No, I don't. I genuinely don't. I don't think that we could have because we, you know, ultra, ultra low latency feature transformations serving are so core to what we do.
- 20:03
I do not think we could have done it in Python. Certainly, we do a lot of R&D in Python, but 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. And we are very, very lucky to benefit from a lot of the open source contributors that have, you know, for free, devoted their time and efforts to bringing support for languages like Rust. I'm imagining that another, you know, timing tailwind is the availability of coding agents now.
- 20:38
You know, you may have needed to build a lot of, you know, supporting infrastructure before because it just wasn't available for what you're trying to do. But now you can just ask an agent to build that for you. For sure. I mean, a thousand percent. You mentioned that Wayfair was an early adopter of transformers. Are your models transformer based? We have some that are transformer based. We have, I would say, all of our models certainly use self-attention, the self-attention mechanism.
- 21:06
I can say that without a doubt. All of them do. We have many mixture of experts models now, but they all rely on self-attention. I wouldn't say that they use the transformer architecture across the board because, I mean, now we have so many proprietary models that we have built that kind of it's kind of like an orchestra of many many many many models it's like mixture of experts but for ranking is the idea