Platforms I designed and built end to end, using the same architecture patterns as the federal and defense programs I work on.
A production-shaped data platform designed and built from the hypervisor up: virtualisation, infrastructure as code, Kubernetes, a three-broker Kafka cluster, schema registry, change data capture from PostgreSQL, object storage, and automated TLS. Every change goes through a merge request and a pipeline. Nothing was clicked into place by hand.
Every architectural decision is recorded with the alternative that was rejected and the reason: for_each over count for stable resource addressing, monitoring deliberately outside the cluster it observes, one PostgreSQL instance rather than Patroni, and why the CI runner cannot safely restart the virtual machine that hosts it. Runbooks are written for the person on call at three in the morning, not for the person who built it.
Designed and built a full AWS GenAI data assistant architecture from the ground up, integrating AI, voice control, document intelligence, and automated CI/CD into a single cohesive platform. Built using production-grade architectural patterns, AWS services, and data pipelines aligned with real-world federal and enterprise data operations.
Two views of the same system. The client reference shows the shape of the solution. The engineering view adds the delivery chain, identity boundaries, voice channel and analytics path. Click either diagram to enlarge.
Project source is kept in private repositories. Access is granted on request to hiring teams, prime contractors, and clients.
Nothing here originates from a client or government environment. Work performed under federal and defense programs stays inside those boundaries and is described only at an architectural level.