Background
Scientist by training. Engineer by profession.
My original training was in chemistry, followed by computer science. The disciplines are different; the habit of mind is not. Both reward decomposition, evidence, skepticism toward convenient explanations, and the ability to move between a model and what the system is actually doing.
That way of thinking has remained consistent across software architecture, machine learning, payments, and healthcare. What follows is the arc — by scope of responsibility, not by employer. I am based in the United States.
Foundations in production software
I started in conventional software engineering: systems that had to operate, not merely demonstrate an idea. Most of the later work still rests on that.
Commercial systems at global scale
Early in my career, I worked on business-critical payment infrastructure for a major global online gaming platform. It was an early lesson in consequential engineering: when software sits directly in the path of revenue, reliability and operational discipline stop being abstract qualities. Transaction integrity, availability, and international scale had immediate commercial consequences.
From software to data and machine learning
The work moved toward increasingly analytical systems — data, then machine learning, then applied research — without the conventional engineering going away. Architecture, data, and machine learning became one repertoire.
Regulated healthcare
Recent years have concentrated on healthcare: systems where engineering choices live inside regulatory, integration, reliability, and operational constraints, and where a demonstration is a long way from a product. The scope expanded from architecture through data and machine-learning platforms to regulated production systems, cross-team technical direction, technical governance, and customer delivery.
I was hired directly into a senior individual-contributor role at Oracle rather than reaching it through internal promotion, and the responsibility has kept widening since. I am the first-named inventor on a published US patent application in healthcare, Autonomous medical coding system (US 2026/0120194 A1, 2026).
Technical leadership beyond the org chart
Over time, my work moved beyond designing individual systems. I increasingly became responsible for problems spanning architecture, delivery, dependencies, technical standards, organizational alignment, and customer commitments. Many of those problems did not have a clean owner. Someone still had to own the outcome.