AI / ML & LLM Engineering
Evidence-grade retrieval and agentic systems — hybrid search, claim-level verification, and LLM platforms built to prove what they claim instead of guessing.
About / The person behind the work
AI & machine learning research engineer
I build the software, data infrastructure, and AI that turn complex information into useful decisions. My work spans federal and aerospace programs, financial systems, and independent research into reliable machine learning.
A full-stack engineer by practice, a researcher in how I approach a problem. I follow it from the underlying mathematics and data through to the application someone depends on.
Background / From curiosity to research
I started coding at twelve, building apps and publishing games. I still get the same satisfaction from turning an idea into something people can use. Today, I bring that drive to full-stack software, data engineering, and AI and machine learning. The problems have grown: aircraft readiness, financial data, complex enterprise systems, and the evidence behind an AI-generated answer.
My professional work spans defense, aerospace, and federal programs. At SteerBridge, I engineered data infrastructure supporting the USMC F-35 program, then built core data infrastructure for a Veterans Affairs claims program as a Senior ML/Data Engineer. My experience also includes contract work on proposals, prototypes, and architecture for Lockheed Martin and Sikorsky, and AI solution development through the IBM Partner Program. At Accenture Federal Services, I now build agentic and financial systems, bringing data engineering and applied AI into workflows where security, traceability, and sound decisions matter.
I work across the whole system: the interface someone uses, the APIs and services behind it, the pipelines that prepare its data, the models it depends on, and the infrastructure that keeps it running. Python, Rust, Go, and TypeScript are part of that work, alongside distributed processing, feature engineering, retrieval, model evaluation, and secure AWS architecture. Being able to follow a problem across those layers shapes how I design a solution.
My research starts with a question I can test. What does the data actually support? Does a neural model improve on a simpler baseline? Can an answer be traced to its sources? I use mathematical reasoning, statistical evaluation, and reproducible experiments to examine those questions. That direction connects my engineering experience to a growing interest in biomedical data and research tools, where the quality of the evidence determines what we can responsibly conclude.
Independent projects give me room to pursue those ideas in depth. I'm developing Structura around source-addressable retrieval, Praxis around governed AI-assisted development, and AegisOS around computing when connectivity is limited. Guardis, Relay, SignalForge, and ViDaT extend that work into security, data integration, signal processing, and visualization. I write about the decisions and limitations as the work develops.
I'm pursuing a Bachelor of Arts in Computer Science at Virginia Commonwealth University, expected in 2026, and a Master of Science in Computer Science at the University of Colorado Boulder, expected in 2027. My credentials span data engineering, machine learning, cloud architecture, and generative AI. I'm building on that foundation through research and hands-on engineering, with a consistent aim: make difficult problems understandable, then build systems people can use, inspect, and improve.
What I do
I work where AI, data, and secure infrastructure meet — on systems that have to be right the first time, for people who can't afford for them not to be.
Evidence-grade retrieval and agentic systems — hybrid search, claim-level verification, and LLM platforms built to prove what they claim instead of guessing.
Multi-stage pipelines and lakehouse infrastructure moving petabytes — streaming ingestion, transforms, and provenance for systems where correctness isn't optional.
Production infrastructure on AWS GovCloud — FedRAMP-aligned, zero-trust, IaC-driven systems supporting defense and government programs.
Rust and Python at the core — my flagship systems Structura, Praxis, and AegisOS, plus full-stack products delivered end to end.
Delivered across
Skills
A breakdown of the tools and technologies I work with daily, rated by depth of production experience.
Career
Federal fraud analytics, production data pipelines, and research into agent-based AI solutions.
Data infrastructure and ML integration for a U.S. Department of Veterans Affairs claims program.
Sustainment data engineering and operational analytics for the F-35 program.
Prototypes and architecture for legacy-service modernization and aviation data platforms.
Proofs of concept and architecture proposals developed through Lockheed Martin supplier channels.
Partner-program work across enterprise, government, aviation, and defense use cases.
Led full-stack engineering and cloud infrastructure across a growing software consultancy, delivering scalable MERN and data engineering solutions.
Served as CTO of a non-profit organization, leading all technology and software development operations and defining long-term technology strategy.
Conducted research into emerging technologies and built practical software prototypes across the full development lifecycle.
Founded a 3D modeling and open source printing organization, building software solutions that connected with Raspberry Pi to enhance the 3D printing process.
Credentials & collaborations
The work happens where precision isn't optional — defense, aerospace, and government programs, delivered under real accountability.
Current work / Engineering & investigation
Reliable retrieval, accountable agents, and useful AI beyond the cloud. These independent systems give me room to work through each problem in depth.
In professional practice
Accenture Federal Services
Agentic and financial systems for federal programs, connecting data, applications, and secure infrastructure.
Can an answer lead back to its source?
Developing retrieval that keeps source locations and evidence accessible through the path to an answer.
What should an agent be allowed to change?
Building development workflows around explicit context, permissions, evaluation, and reviewable changes.
What remains useful without a network?
Exploring local AI, retained evidence, and recovery when connectivity is limited or interrupted.
Philosophy / How I make decisions
The discipline I bring to an aircraft data pipeline also belongs in a web application or an ML experiment: clear assumptions, deliberate interfaces, and evidence that the result holds.
A choice in the interface can change an API contract, a query plan, or an operator’s workload. I trace those relationships before optimizing one component.
For ML and AI, I want to understand the objective, the available information, and the baseline. A useful result survives inspection of the examples where it fails.
Data arrives late, requests repeat, and services become unavailable. I treat retries, observability, and rollback as design decisions that deserve their own tests.
I document the tradeoffs and revise them as new evidence arrives. Writing, open-source work, and focused experiments help turn an individual lesson into something another engineer can use.
Experience / Defense & aerospace
Supporting aerospace programs has shaped how I think about software: understand the people using the information, preserve its context, and make the system possible to inspect and maintain.
My work supporting the USMC F-35 program at SteerBridge connects data pipelines and analytics to fleet sustainment. The source, meaning, and freshness of a record matter to the decisions built on it.
I consider identity, access boundaries, and data movement alongside the application itself. An integration needs a clear account of who can use it and what it exposes.
Documented interfaces, lineage, and explicit failure handling help another engineer understand what changed, why it changed, and how to investigate a problem.
Method / From question to operation
I want the finished system to carry an explanation of how it works, what it assumes, and how it was tested. That applies to a frontend, a data platform, and a trained model.
The engine study is a reminder to look at the interfaces between parts. In software, that means examining contracts, dependencies, and what happens when one stage behaves differently than expected.
Identify the user, the decision, and the operating constraints. Examine the existing data and define what a useful result would look like.
Map interfaces, data flow, and trust boundaries. For ML, define the baseline, evaluation split, and assumptions before comparing approaches.
Implement in reviewable increments. Exercise edge cases, inspect failures, and measure the behavior that matters to the original question.
Deploy with a recovery path. Monitor real behavior, investigate unexpected results, and bring those observations into the next design decision.
Building innovative systems
A snapshot of my contributions and coding activity over the past year — building tools, shipping features, for private orgs, research & Development and more.
Across private & public repos including FinoSync Corp, AWS, and defense projects
Days with contributions since 2019
Consecutive days of shipping code
Interests
The things that fuel my engineering work and keep me curious — from writing and open source to aviation and AI research.
I publish deep-dives on architecture, AI pipelines, and engineering best practices. Writing clarifies thinking and builds community.
Contributing to the tools I rely on and building new ones. OSS is how I give back to the community that taught me to code.
A lifelong fascination with flight, from aerodynamics to avionics. It shapes how I think about precision, systems, and reliability.
Experimenting with autonomous agents, RAG architectures, and the frontier of what software can do when it can reason.
Helping early-career engineers navigate the industry through code reviews, pair programming, and knowledge sharing.
Currently exploring Rust systems programming, edge computing, and ML infrastructure. The learning never stops.
Let's build
Evidence-grade AI, mission-critical infrastructure, or a platform that needs to be right the first time — if it has to hold weight, let's talk.