Lead Software Engineer and engineering leader with over seven years of experience, currently operating at the intersection of financial technology, digital identity, and fraud prevention at LSEG Risk Intelligence.
My technical foundation spans full-stack development across two distinct ecosystems — a React, Python, and Django background that evolved into a current focus on C#, .NET, and Azure at enterprise scale.
At this level, engineering leadership extends well beyond writing code. Delivering and evolving the Trusted Payments Platform at LSEG means operating across a genuinely wide surface: aligning with product and business stakeholders on roadmap and requirements, coordinating with infrastructure and SRE teams on platform reliability and scale, partnering with data engineering on pipeline integrity, and working closely with solutions consulting, implementations, and onboarding teams to ensure what gets built actually lands for the client.
Financial technology is not a forgiving environment. The clients we serve operate under strict regulatory and compliance frameworks where data accuracy, system availability, and audit trails are contractually and legally mandated, which means every architectural decision, every API contract, and every data handling choice carries weight that a consumer product simply does not. The real complexity lives in the translation layer between all of this — requirements arriving from multiple directions simultaneously, each carrying their own language, urgency, and definition of done.
Keeping that context intact across team boundaries, so that what the business needs, what the product specifies, what compliance mandates, and what engineering delivers are actually the same thing, is where most of the invisible work happens. It does not show up in a pull request. But it is the part that determines whether everything else adds up to something worth building.
Outside of engineering, curiosity is probably the most accurate word for how I move through the world. I read broadly and without apology across investing, behavioral finance, history, psychology, philosophy, and whatever rabbit hole presents itself. In recent years I have used AI as a genuine thinking partner to go deep on topics that interest me: dissecting the frameworks of great capital allocators, exploring Vedic philosophy and ancient systems of thought, understanding naval history and the geopolitics behind it, tracing the architectural DNA of cities, stress-testing my own investment theses, and generally treating complex ideas as something worth taking seriously rather than skimming.
Music is a constant. I listen to rap, jazz, ghazals, hip-hop, qawwalis, and Indian classical with equal affection — nothing still beats the 90s and 2000s era. I play the tabla and flute, both disciplines that reward patience and precision, which probably says something about the rest of how I think.
One passion that has grown steadily over the last few years is capital allocation. I take it seriously, I have built a structured framework around it, and I invest in global equities with no geographical constraints. You can read more about how I think about that in the investing section.
You can find more about me at —









React, Redux, TypeScript, JavaScript, HTML5, CSS3, Bootstrap
C#, .NET Core 8+, .NET Framework 4.8, Web API, MVC, Python, Django REST, Node.js/ExpressJS
MSSQL, SQL Server, MySQL, MongoDB, Snowflake, Redshift
Azure, AWS, Kubernetes, Docker, Jenkins
Datadog, Serilog, OpenTelemetry, VS Code, JetBrains, git
Studied across the breadth of computer science and software engineering — Artificial Intelligence, Secure Software Design, Database Management, Software Testing, and more. This was my attempt to get a hold of being a Full-Stack Engineer.
Four years of foundational learning — from soldering to theory of computation, mechanics to cyber security. Elected Technical Head of the student committee in my senior year.
I have been investing since 2020, spending the first few years reading deeply and building a framework before deploying capital with real structure and discipline from 2023 onward. The preparation phase was intentional — I wanted a point of view before I had a portfolio.
The approach is built around a long-term business owner mindset. Concentrated positions, high conviction, valuation discipline at entry. Not a trader, not a momentum chaser. I think about capital allocation the way I think about engineering systems — with frameworks that eliminate bad options before saying yes to anything, and with explicit criteria for when a decision is wrong and needs to be unwound.
The quality filter does most of the work. Avoiding bad businesses and bad management is a more reliable edge than finding the next great thing. If the business and the people running it pass a high bar, the entry price and hold period questions become much simpler.
Asymmetric risk-reward is the entry condition, not an afterthought. Every position needs a clear answer to what goes right, what goes wrong, and whether the downside is survivable relative to the upside.
Behavioral self-awareness is a discipline. Knowing where your process breaks down — delayed entry, undersized conviction, thesis drift — and building explicit guardrails around those gaps is as important as the analysis itself.
I run two parallel systems: one oriented toward capital acceleration through thesis-driven, catalyst-aware positions with defined exits, and one oriented toward permanent quality ownership modeled on the best long-term compounders. The separation is deliberate — the risk is letting the two contaminate each other.
No geographical constraints. I look where the opportunity is.
Building my own portfolio, on my own terms, for the long run.
Warren Buffett · Charlie Munger · Mohnish Pabrai · Stan Druckenmiller · David Einhorn · Pulak Prasad · Rakesh Jhunjhunwala · Vijay Kedia · Sanjay Bakshi · Nick Sleep · and a lot of fintwit