I build automation that simulates operators and environments, captures system data at scale, and runs statistical analysis pipelines, turning every test into concrete evidence that stakeholders and developers use to validate systems and make key decisions.
I'm a senior systems and software test automation engineer in defense, with a dual background in CS and Statistics and a physics minor that taught me to care about measurement. I design automation architectures that simulate operator inputs and the external environment, capture the resulting system data, and run queued analysis pipelines to verify that complex systems behave as intended. I also mentor engineers on automation practices and design.
I'm now pursuing an MS in Analytics at Georgia Tech, and I'm bringing the same rigor to data engineering, machine learning, and data science.
A simplified look at how I validate a system end to end:
(Tap to see more)
Trigger and schedule test runs automatically, via CI/CD or job queues, with no manual kickoff.
Automate operator inputs and the external environment with scripted, repeatable scenarios.
The system itself: its behavior is driven entirely by the automated inputs and environment around it.
When live results matter or time is limited, system data from step 4 can stream directly to the dashboard in step 6, skipping job-queued analysis.
Capture the system data generated during each test run.
Queue the collected data through automated pipelines to validate behavior at scale.
Validate results against requirements and present them in a dashboard built for stakeholders and reviews.
I'm open to three kinds of roles:
Automating operator inputs and the external environment, with system data collection and job-queued result analysis. It's what I do now, and I enjoy its breadth.
More analytical: understanding data and drawing meaningful conclusions from it through advanced math models like deep learning, transformers, and PCA.
Data pipelines and scale, which I find compelling from a systems-design perspective: building the infrastructure data actually moves through.
In any case, I'm especially drawn to domains where the stakes make rigor non-negotiable: defense, aerospace, and scientific or research computing. If that's what you're building, I'd love to connect.