The Engineer Who Reads the Production Logs
When Aurimas Griciūnas says something about AI, he has logs to back it up. Not demos. Not benchmarks. Logs from systems he shipped, monitored, and fixed at 2am. That distinction - between someone who talks about AI and someone who runs it - is the whole premise of SwirlAI.
He grew up in Lithuania and studied Financial and Actuarial Mathematics at Vilnius University, which is a pretty specific way to enter the ML world. But the training held: probability, risk, the math of uncertainty. That's the lens he brings to every architecture decision he's made since.
His early career read like a tour of production ML before production ML was glamorous. Danske Bank, where he built affordability models for a financial institution with real regulatory skin in the game. Transactie Monitoring Nederland, where he engineered systems specifically designed to detect financial crime. Not POCs. Production systems that had to work every time, because the alternative was letting criminals through.
"The most valuable specialist can actually build end-to-end, starting from figuring out products and implementing POCs, shipping it, and reacting to feedback."
- Aurimas Griciūnas, on what he looks for in AI engineersBy the time he joined neptune.ai as a Senior MLOps Engineer, the ML community was starting to wake up to the gap between notebook experiments and real-world deployment. Aurimas had been living in that gap for years. He rose to Chief Product Officer - the person responsible for deciding what neptune.ai built and why. Then OpenAI acquired neptune.ai. The product he helped shape ended up in the most famous AI lab on earth.