TransactAPI
Concurrency-safe financial core in Spring Boot.
- Pessimistic row-level locking
- Idempotency keys for safe retries
- PostgreSQL · JWT · Spring Security
Engineering taught me how to read physical systems and reason around it. Now I write software and train models that control systems.
Software & Machine Learning engineer building high-integrity backends, applied ML systems, and industrial IIoT pipelines from embedded firmware to cloud.
Concurrency-safe financial core in Spring Boot.
AI-assisted battery-swap coordination for e-boda and e-matatu fleets over USSD/SMS.
End-to-end IIoT backend for copper tailings pipelines: telemetry ingest, orchestration, and inference fan-out.
XGBoost regression served through a FastAPI inference layer and a Spring Boot client, with a live prediction endpoint.
Physics-informed sequence model for pipeline anomaly detection on 51 engineered features.
Darcy-Weisbach pressure modeling drives the feature space.
Neural surrogate for hot-compression flow stress in stainless steel: closed-form replacement for empirical constitutive models.
Trained with scipy L-BFGS-B against experimental hot-compression data.
XGBoost regression on standard concrete mix + curing features, served for live inference.
Feature engineering on age, cement, water, aggregates and admixtures.
A LangGraph-driven research assistant orchestrating specialized Claude agents. FastAPI shell, Redis pub/sub for inter-agent messaging, Tavily for grounded web retrieval.
Multi-objective plant optimization using NSGA-II with an ANN surrogate model over IAPWS-IF97 steam thermodynamics. Targeting throughput / efficiency Pareto frontiers at Olkaria II.
Most machine learning tutorials stop the moment the model trains successfully — this one goes further, from notebook to a real deployed API.
Read on Medium →Part 1 of a beginner-friendly system design series for backend, ML, and AI engineers.
Read on Medium →Built the 12-month financial model used in the pre-seed investor meeting.
Spring Boot and FastAPI project delivery for external clients.
Mining engineering got me through the door of university. It wasn't where I found my footing; coding was. Somewhere in year three I stopped forcing myself through mineral processing problem sets and started staying up late building things instead, and that was the first time engineering felt like mine.
I still carry the rigor from that background: physics-informed features, deterministic systems, respect for what happens when something fails in the real world. But I don't want a mining degree to be the headline of who I am. I'm a software and ML engineer now. That's the through-line I'm building on.
Open to backend, ML, and applied-research roles and even Collaborations.