Follow the evidence
through the system.

My BSc in Geophysics included a supervised project comparing thermal scenarios for the 2015 Gorkha earthquake. I constructed the model geometry and mesh, varied thermal inputs, and extracted and compared the results.

My professional work began in warehouse operations and reporting, then expanded into warehouse systems delivery, cloud integration, data-platform modernization, and technical leadership. I have led teams and engineering practices while continuing to work directly with Python, SQL, Azure services, APIs, CI/CD, and production performance problems.

I’m now pursuing a hands-on individual-contributor direction in software and platform engineering. Backend systems, observability, performance, and explicit boundaries are the areas where my operational and data-platform experience transfers most directly.

Testing should change the design.

A technically correct request can still fail as a workflow. I want browser checks and user acceptance work to start from realistic conditions, cover recovery paths, and verify the resulting state. When the evidence contradicts an assumption, the design or the claim should change.

AI needs an engineering boundary.

I’m exploring agent-assisted investigation and operational tools through access limits, citations, evaluation, and failure handling. Those controls determine what a person can safely rely on and what still requires review.

Make the reasoning inspectable.

The projects and writing here show architecture, failure modes, recorded checks, and unresolved work. The aim is to make each decision understandable enough to question and change.