About
From rockets to AI
I build AI infrastructure on my own hardware. There is a two-node GPU cluster (an RTX 3090 and an RTX 5090) that serves local models, an agentic RAG system that retrieves and cites answers against a real 321,000-chunk corpus, and a multi-agent platform of about 32,000 lines that runs a two-model team through a peer-review loop before anything ships. I have built it over the past year and a half — designing it, debugging it hands-on, and folding in what worked from earlier projects, and increasingly using that two-model team itself to write and review code faster.
This work came out of my day job. I test RS-25 flight engines, and I also took on a documentation problem there: a large, scattered pile of technical material that had to be searchable and trustworthy. I cannot share any of that, so I rebuilt the ideas from scratch on public data. That is what these repos are, my own versions of retrieval problems I actually run into at work.
The day job is verify-before-ship. Cryogenic inspections, leak checks, flight-readiness testing, and nothing goes out until it is proven. I hold my own systems to the same standard: config is the source of truth, defaults fail closed, and I label every number measured or estimated instead of just asserting it. I am looking for remote ML-infrastructure or applied-AI work where that kind of discipline is the point.
How I work
Principles
-
Measured, not asserted
Every project metric is labeled measured or estimated and traces to evidence. No head-math, no single uncontrolled samples. I hold the writing to the same bar by hand.
-
Reproducible over clever
Config-as-truth, verify gates, and one-click revert. If it cannot be reproduced, it is not done.
-
Offline-capable by default
Local-first with no hosted-LLM dependency. Privacy and independence are design constraints, not afterthoughts.
-
Safety-critical mindset
Least-privilege and fail-closed by default. The habits that keep flight hardware safe are the same ones that keep an autonomous system from doing something it should not.
Timeline
Where I've been
-
2025 — Present
Test Engineer — RS-25 flight engines
Aerojet Rocketdyne (L3Harris)
- Cryogenic inspections, leak checks, and flight-readiness testing to flight-qualification standards.
- Self-initiated: built an agentic RAG knowledge base over a large enterprise technical-documentation corpus that substantially cut specification-research time (figures available on request).
-
2024 — Present
AI Infrastructure Engineer (self-directed)
Personal — Local AI Infrastructure Lab
- Designed and operate a modular, offline-capable multi-agent LLM platform (~32k LOC).
- Stood up a two-node multi-GPU cluster with containerized model serving and fault recovery.
-
2024 — 2025
Manufacturing Engineer
Aerojet Rocketdyne (L3Harris)
- Authored and executed 40+ V&V procedures and acceptance protocols.
- Built Python/VBA automation and led production capacity modeling for the assembly facility.
-
2023 — 2024
Systems Engineer T1
Leidos
- DoD/Navy underwater acoustic systems integration and testing.
- Automated PCB acceptance testing with LabVIEW (~5× faster); authored V&V protocols.
-
2022 — 2023
Undergraduate Research Assistant
Raspet Flight Research Lab — Mississippi State University
- BVLOS UAV flight testing (ArduPilot / PX4); engineering analysis in MATLAB.
- Education
- B.S. Aerospace Engineering (Astronautics), Minor in Mathematics — Mississippi State University, 2023
- Citizenship
- U.S. citizen. Held a prior U.S. security clearance (currently inactive) — details on request.