$ cat resume.txt

Baltimore, MD (Remote)

• — Design and build reference architectures and production-grade demo applications on NATS.io and Synadia Cloud, demonstrating event-driven patterns including pub/sub, JetStream persistence, and key-value and object stores.
• — Author developer documentation, technical guides, and tutorials for adopting NATS in production.
• — Work across the stack in Go, TypeScript, and hypermedia frameworks to demonstrate low-latency application patterns from broker to browser.

Baltimore, MD (Remote)

• — Architected scalable backend services with Vert.x and HyperExpress, deploying a Hazelcast-backed Vert.x cluster for resilience, redundancy, and distributed state management.
• — Implemented secure authentication workflows using OAuth2 and PKCE, and designed and enforced Role-Based Access Control for granular, auditable access to protected resources.
• — Established data governance practices in compliance with ISM standards, defining the controls the team built against.
• — Optimized PostgreSQL schemas and query performance; integrated WebSockets into Ember.js for real-time updates.
• — Mentored junior engineers and raised the team baseline on security and scalability practices.

Baltimore, MD

• — Built real-time weather monitoring dashboards in React and Redux, reducing data load times by 30%.
• — Developed Spring Boot and Hibernate services backed by Redis to cache and serve high-frequency weather data.
• — Designed an AWS ingestion pipeline using Lambda for real-time processing and S3 for durable, scalable storage.

Distributed Sensor Cluster Vert.x · Hazelcast · Datastar · Docker Compose

Three-node Vert.x cluster where virtual sensors are deployed and torn down at runtime. Nodes coordinate over the clustered event bus with Hazelcast managing membership; readings stream to the UI over SSE rather than polling.

Real-Time Multiplayer over Redis Pub/Sub Node.js · WebSockets · Redis

Implemented the WebSocket handshake by hand rather than using a library, broadcasting moves through Redis Pub/Sub; game state persists so matches survive a server restart.

ECS Game Server Go · entity-component-system

ECS design separating data from behavior; systems iterate contiguous component arrays for cache locality.