WebSockets
Tommy + the technology of WebSockets
Home Capabilities Technologies WebSockets
WebSockets Examples

Castle Risk Online
Personal Project2025 - present
Castle Risk Online is an online multiplayer board game with chat, animations, and AI players. It supports social login, mobile, dark mode, and is a blast to play with family and friends.
The game is built with React, with jotai for atomic state management on the frontend, and optimistic state synchronization viaWebSockets, proxied thru a K8s (Kubernetes) ingress controller equipped with Cert Manager to the underlying Express JS servers, which autoscale based on tcp connection rules, and use RxJS for Functional Programming stream processing of game events.
Key Results
- Launched fully functional multiplayer game with realtime chat, social login, mobile + desktop support, dark mode
- Achieved <200ms latency for real-time game state synchronization across all players
- Kubernetes + Skaffold used for cloud-agnostic deployments

Intertru.ai
AI-assisted Hiring2023 - 2024
The candidate summary page summarized a candidate's performance during multiple interview stages by presenting radar charts showing degree of fit against the values and attributes being evaluated for their position, as defined in the Interview Builder.
I built the frontend in React and Typescript, and integrated with the backend, which I partially built, which leveraged RAG and ran several Machine Learning models to produce scores and explainable AI. For example, models to break down interview transcripts into quotable fragments, evaluate relevance against configured company values, and call chatGPT APIs to obtain summaries and scores related to that content
Key Results
- Built AI-powered candidate evaluation dashboard enabling data-driven hiring decisions
- Integrated 3 ML models to support explainable AI
- Performed Quick prototyping with product and design to get product-market-fit cheaply

Appen AI
Formerly Figure Eight2022 - 2023
Instead of splitting devops and infrastructure and tests completely separate from development teams, I moved the needle so that product development teams could own more of their own infrastructure and tests, creating less back-and-forth and empowering teams to deliver.
We used Devspace, which meant any dev or team could stand up a reproducible, isolated stack with multiple services and frontends running, in the cloud, as well as modify the definitions of the infrastructure and code themselves, directly, without permission or external team tickets.
This enabled product engineers to do more experimentation and testing thru declarative infrastructure and configuration management while still protecting our production environments, unlocking their shackles and potential as the experts in the software.
At the same time I worked to reduce the outsized role our amazing DevOps team was playing in the day to day management as well as enhancement of environments, which unfairly impeded expert developers by introducing red tape and inter-team processes that didn't add value.
Key Results
- Reduced deployment lead time by 75% enabling product teams to self-serve infrastructure
- Decreased inter-team ticket volume by ~60% through developer empowerment
- Enabled parallel development with isolated cloud environments for each developer