I'm the lead data engineer on the U.S. Marine Corps Logistics Analytics Data Services team. Day to day I write Python, PySpark and SQL in Databricks and model the results as a Palantir Foundry ontology that analysts can query with AI.
fetch('bobby-status.json') .then((response) => response.json()) .then((data) => { console.log(data.status); });// For those who can't view the console// it says "building ontologies"
I designed and built this as its primary developer. It turns 15+ years of flat, denormalized outbound data feeds from the enterprise's ERP (enterprise resource planning) systems into a connected, time-aware Foundry ontology that analysts can explore through Foundry AIP.
effective_from / effective_to dates, so point-in-time questions become simple filters.A public pipeline over New York's congestion pricing data. It records what a metric is expected to do before the data arrives, then scores each expectation automatically and shows where any gap comes from. I built it to show how I work, since most of my day job can't be published.
An experiment on which written context helps a model turn a plain-language question into the right SQL: table descriptions, table selection, or short narratives of how each process moves through the tables. Two small local models, with a prediction for every answer committed before the run.
Moved my team off a legacy AWS GovCloud stack (NiFi ETL, Redshift, Athena, QuickSight) onto Databricks and Foundry. I designed the target architecture, pipeline patterns and CI/CD, with no loss of capability along the way.
Wrote and evaluated Python and SQL solutions used to train and test LLMs. I was promoted to lead reviewer within three months and reviewed other contributors' code for correctness and quality.
Outside work, I spent two months building several Python projects with Claude as a collaborator, including a numerical library and a command-line text pipeline built on word embeddings. What carried over to my day job is the method: I set the direction, and I keep a running log of what's established, what's been tried and what failed, so each session starts with full context. I check results against tests and baselines before I trust them, and the core library runs its own verification checks.
Python (PySpark, pandas), SQL, C#, TypeScript. Automated testing, code review, CI/CD, Git
Databricks, Delta Lake, Palantir Foundry, Apache Iceberg, Apache Airflow, AWS GovCloud (Redshift, Athena, S3), Apache NiFi
Ontology and knowledge graph design, entity and relationship modeling, object-event temporal models, SCD Type 2, star schemas
Foundry AIP and AI-FDE, semantic layers for natural-language querying, LLM-assisted development (GenAI.mil, Claude), word embeddings, LLM training data