Kuru Exchange — Quant Engineer
Handle quant infrastructure and market making across public and private vaults, with a focus on hedging and execution systems.
Rust, InfluxDB, Docker, Hedging, Market making
Quant engineer · DeFi systems · Bengaluru, India
I go deep into the things that interest me, work with strong teams, and build systems that stay reliable under pressure.
My background spans centralized exchanges, restaurant management systems, MEV on EVM chains, solver infrastructure, and high-frequency trading. I currently run quant infrastructure and market making across public and private vaults at Kuru Exchange.
Before moving into quant engineering, I built centralized exchanges and high-frequency trading systems in Java. These days, most of my work is in Rust. I enjoy the language, especially its type safety and how much I can catch at compile time.
My expertise spans Rust, Python, and monitoring systems. I choose tools and languages based on what the problem needs and my experience with them.
I have a deep interest in mathematics and optimisation, and I make a conscious effort to study both and put what I learn into practice.
Handle quant infrastructure and market making across public and private vaults, with a focus on hedging and execution systems.
Rust, InfluxDB, Docker, Hedging, Market making
Worked on a Rust high-frequency trading engine, then built a backtesting system collecting data across nine exchanges, including perp DEXes.
Rust, Python, MongoDB, NumPy, Polars
Built and maintained a solver analytics dashboard for monitoring volume and liquidity trends. Used by roughly 100 solvers and enthusiasts daily, alongside a private Grafana dashboard for deeper analysis.
Rust, PostgreSQL, Vercel, Next.js, Hetzner
Built and ran solvers for CoW Swap and deBridge. Worked on Ethereum and Base backrunning, custom liquidity indexers across Ethereum, Arbitrum, and Base, routing engines, router contracts, and self-hosted nodes.
Rust, Solidity, Assembly, PostgreSQL, Hetzner
Worked on Intent.markets for aggregated bridge data, set up normalization runners across protocols and chains, and contributed to solver research.
DevOps, Cross-chain systems, Solver research
Set up a cross-chain aggregation stack across EVM chains and built a Solana gas manager for gasless payments and transactions.
EVM, Solana, Cross-chain infrastructure
Designed and built a global crypto exchange from the ground up: an event-driven order book and matching engine on Kafka, market data and WebSockets, risk and audit systems, market making, monitoring, charting helpers, and asset management.
Java, Spring Boot, MongoDB, TimescaleDB, React, Kafka, AWS
Integrated APIs from NSDL for an e-signing system and built a distributed SeaweedFS storage cluster for customer documents.
Python, SeaweedFS, Java
Built the backend and consumer app for a restaurant management platform, piloting the mobile product in Flutter before focusing on backend and DevOps.
Java, Flutter, GCP, AWS
Rewrote the backend of an Indian crypto exchange for scale, serving roughly 50k users and handling millions of rupees in daily volume. Built deposit systems, exchange connectors, charting, monitoring, risk engines, admin tools, VPN infrastructure, and in-house hosting.
Java, Spring Boot, MongoDB, React, 50k users, AWS, DevOps
Consulted for a cloud B2B SaaS platform that simplified cloud deployments through automation, including automated policy creation and related deployment workflows.
Cloud automation, B2B SaaS, Policy creation
Company blogResearched RNNs for natural language processing and used image processing and convolutional networks to extract details from uploaded electricity bills.
Python, Pandas, NLTK, TensorFlow
Earlier in my career, I spent a lot of time answering questions on Stack Overflow: 751 answers, 30,675 reputation, and 3.4m people reached.
Mostly python, pandas, dataframe, numpy.
Placed as the 2nd runner-up in the Innoplexus online hiring hackathon.
Won the Zomato track of the inaugural edition at age 17 — the youngest winner among ~10,000 registrations. $1,000 prize.
Runner-up on the DataHack leaderboard for the data science hackathon. $500 prize.
Went to Rishikesh for Praveen's wedding. Had a great time with the Kuru team and made another set of memories together.
Started 2026 with surfing lessons in Mulki with the team. It was amazing to learn together and a brilliant start to the year.
Spent 10 days in Langkawi. It was one of the best nature-immersive experiences I have had, with the bluest water I had ever seen. Adventurous, restorative, and a great time.
Joined Kuru as a quant engineer, working primarily on market-making infrastructure and excited to contribute to the Monad ecosystem.
Spent 10 days in Vietnam. Fell in love with Ho Chi Minh City, especially District 1, then went to Da Nang and fell in love with it all over again. Ba Na Hills is still one of the core memories. Loved the food, people, and the entire vibe.
Recovered from Lasik and paused calisthenics for a month. Work at Anera was fast and deeply technical. Started preparing for quant research by going deeper into probability and calculus, with the possibility of studying physics someday.
Restarted calisthenics and math for a healthier body and mind. Began studying financial engineering, mostly through probability and differential equations.
The solo-founder journey paused and I joined Anera Labs as a consultant on the execution team. I had missed a lot of technology and engineering by staying inside echo chambers. Solver Pro paused while routing research continued. There were personal and family challenges, a wedding anniversary, and a scuba dive that was less fun than expected because I panicked.
Became more Rust-pilled while developing a general solver framework around the actor model. Kept going with math, reached 20% of Math Foundation 3, and returned to basic calisthenics with 12 slow pull-ups.
Returned from Bangkok with a lot of learning from meeting great teams. Roamed around the city alone for a couple of days, and it was a memorable experience.
Travelled to Bangkok to meet the other side of the Ethereum ecosystem: developers, investors, and solvers.
Worked more deeply on CowSwap solving and performed reasonably in the shadow competition. The next targets were Mantis, Across, and deBridge. The previous weeks had brought a huge amount of learning and strategy refinement.
Reworked the in-memory liquidity map. Decided that rewriting the CowSwap baseline solver from scratch would be healthier than fine-tuning a messy codebase. Joined the shadow competition with a general solver that could compete across multiple protocols.
Continued competitive math learning to become better at routing algorithms. Built a simple orderbook view for Uniswap V3 AMMs and kept going deeper into the math.
Met nearby builders and had a great time talking through web3. Started working on math problems through Math Academy. Rewrote the CowSwap solver and built a frontend dashboard for analysing and benchmarking its metrics.
Made more friends through coding and optimization. A conversation with a leading CowSwap solver motivated me to become a solver myself and start setting up the infrastructure that could be useful for many things in the future.
Recalled my HFT systems work and wrote down the ideas behind an event-driven in-memory matching engine. It may not help a wide range of people, but writing it down was useful for me.
Started contributing to intent.markets and worked on an in-memory liquidity map for route analysis, with the thought that this kind of infrastructure might eventually become a commodity.
Spent the last few days bug-fixing Solverscan and working on amms-rs. Added filters to the swap page. Solverscan reached its first 1,000 visitors and more than 5,000 page views in about 20 days. The simple metrics seemed to be useful, and a lot of hard work had gone into making them accessible.
Added Across to Solverscan and began indexing its data. Added average bridge time, gathered research materials for becoming a solver, and set up Artemis to understand the MEV landscape from a solver's point of view. Took a short break after burning out.
Started sharing bridge updates. Getting attention was hard, but rapid prototypes were giving me new perspectives. Also started understanding why doing everything alone is not scalable: collaboration lets people combine more energy than one person can sustain. The long-term goal was a dream team where everyone could grow with plenty of fun attached.
deBridge went live. Learned that keeping everything dirt cheap would not work forever and started reconsidering how to scale. Rethought the original solver protocol framework and decided to build a smaller project that could grow over time. Accelerator applications were rejected, which became an opportunity to reanalyse the approach.
Started working on bridge data. On-chain analysis crashed the server because block indexing is intensive, so deBridge analysis was rewritten around its stats API. Added perps to the intent landscape. Solverscan had almost 50 active daily users. Restarted violin classes too.
Added UniswapX and 1inch on-chain decoding to Solverscan. Improved the backend by moving filtered token data into transaction responses instead of querying 5KB of metadata every second. Started working on better pricing by syncing Uniswap and Curve AMMs.
Created Solverscan with the entire backend on Rust. It went live with CowSwap, leaderboards, and a solver dashboard. The frontend uses Next.js, the backend uses Rust and PostgreSQL, and blockchain interactions run through alloy-rs.
It was my birthday—one of the best birthdays yet. Lots of surprises and love.
Started adding CowSwap to Solverscan and worked on the API spec for how everything fits together. The landing page went live. Began recording my project progress to evaluate my process and improve my speaking skills.
Started working on Solverscan, a dedicated explorer for delegated transactions using Rust. Started logging what I am working on. Studying derivatives and integration in depth, moving towards probability and linear algebra. A mechanism design course is in progress, and solver protocol research will continue alongside Solverscan.