Machine Learning Engineering · USA
Machine Learning Engineer
I train, evaluate, deploy, and monitor ML systems that work in production - not just on benchmarks. Specializing in model training pipelines, distributed ML infrastructure, and computer vision.
Industry Experience
72% to 89%: How It Actually Happened
At Omdena from July to October 2024, I led ML engineering for a health and longevity data platform processing over one million records. The starting point was a 72% accurate model on the primary classification task - functional, but not production-ready. The goal was to improve accuracy while also reducing the preprocessing latency that was making the pipeline impractical to run at scale.
The accuracy improvement to 89% came from systematic feature engineering, not from swapping in a more powerful model. I ran structured ablations across feature sets, identified which signal sources were adding noise rather than signal, and redesigned the preprocessing pipeline so feature extraction was reproducible and auditable. The 40% latency reduction came from architectural changes to the data loading pipeline - specifically, eliminating redundant transformations that were being applied per-sample instead of once per batch.
This is the work that most ML engineering job descriptions describe but rarely see: not just achieving a metric, but understanding why the change worked and building infrastructure that makes the next improvement easier to measure. I led the 15-person cross-functional team as the senior ML engineer, responsible for architecture decisions, experiment tracking standards, and review of all model changes before they moved to evaluation.
Current Work
Geospatial CV at Production Scale
At ASU School of Sustainability I engineer geospatial computer vision pipelines to analyze photovoltaic infrastructure at county scale from multi-year NAIP satellite imagery archives. The scale is significant: multi-year archives of high-resolution satellite images, processed to extract structured information about solar panel installations across entire counties.
The engineering challenges here are representative of production CV work in general: large input data volumes that do not fit in memory, spatial preprocessing that must preserve fidelity across image transformations, and quality gates that determine whether a processed image is usable before downstream model inference runs on it. I defined spatial fidelity quality gates using PSNR, SSIM, and RMSE metrics so that the pipeline is self-validating rather than requiring manual inspection of outputs.
The pipeline runs on AWS S3 for storage and uses PyTorch for model inference. The requirement that outputs be reproducible - that running the pipeline on the same input twice produces identical results - forced architectural decisions around random seed management and deterministic preprocessing that most CV pipelines skip and then pay for later.
Research Experience
ML Evaluation Frameworks
At Auburn University from August 2023 to January 2024, I designed a reproducible ML evaluation framework that systematically benchmarked CNN architectures against classical methods across multiple medical imaging datasets. The framework made model selection decisions defensible - each architecture comparison was run under identical conditions with documented hyperparameter choices and reported with confidence intervals, not just point estimates.
I built experiment-tracking infrastructure for diabetic retinopathy classification that tracked every run: model architecture, training configuration, dataset split, and metric history. This infrastructure is why the findings contributed to a peer-reviewed publication - the experiments were reproducible by design, not because someone remembered to save a checkpoint.
At VIT CHAIR over two summers, I built end-to-end deep learning pipelines for Parkinson's detection and diabetic retinopathy classification, and signal-processing models using VMD and statistical features for automated sleep apnea classification. All work contributed directly to peer-reviewed publications. Shipping a pipeline that produces publication-quality results is a different engineering standard than shipping something that just runs - and that standard shapes how I approach ML evaluation in industry contexts too.
Tech Stack
Tools and Frameworks
Open to ML engineering roles.
Google · Meta · Amazon · Apple · Microsoft · Nvidia · OpenAI · Anthropic.