Throughout my career, I've had the opportunity to work on dozens of projects at various levels of responsibility. During my first ten years as a software engineer, I worked on web, console, and mobile games in the game industry. I then transitioned to the healthcare industry, where I was part of a few startups and greatly influenced the products I helped develop. I am now co-founder and architect for a cyber security startup where I've been exercising my skills much more broadly and deeply.
This page is a portfolio of some of the projects I've worked on, my responsibilities as a software engineer and architect, and my involvement with companies I've worked for. This portfolio isn't an exhaustive list but highlights some of the most impactful work I'm proud to have been involved in.
Resume available upon request.
I joined Traxiom when two friends and ex-coworkers from Ripple Health Group and Rally Health needed my help and expertise. They required me to take our MVP product to the next level and make it more robust and scalable. Since then, I've rewritten most of our backend services and created new features for our web app.
As the company's acting CTO, I've also been responsible for communicating with our current and potential customers to understand their needs and how we can meet them. I've then taken these findings to create a roadmap for any necessary infrastructure changes and documented changes in cloud costs. Since most of our budget was out of pocket, keeping costs low and predictable was required.
At Enveda, I had the role of increasing developer proficiency and restructuring their data pipeline to scale their machine-learning data input by several orders of magnitude. What was most challenging about this was that, since this was my first venture into biotech and the pharmaceutical industry, I needed more understanding of what was involved in the drug discovery process and how I could apply it to make their artificial intelligence predictions more accurate. So, I spent the first weeks studying the basics of what is involved in developing a new medicine, which involved learning the roles and responsibilities of biochemists and physicists in this process. I then applied this knowledge to make the data feeding into their machine-learning applications more efficient and accurate. As a result of this restructuring, it was now possible to stream much larger datasets into the databases, and they also required less transformation before the AI processes consumed them.
I also created processes to reduce the cognitive load on developers and created a framework to make creating new lab science applications faster and easier. I left Enveda knowing I had a good influence on their developers and developed a structure they can grow upon to scale reliably and quickly.
As one of the first members of Ripple Health Group, I helped the backend team develop the services needed to launch our mobile products. I also communicated with partnering health insurance companies to design APIs that would allow us to integrate with their systems and provide eligibility and benefits information for our users.
A lot of the tech at Ripple Health Group was built from the ground up, and it took a lot of my prior learnings from my previous experiences to build a platform that allowed us to rapidly prototype new products and features and test new tech with our present applications.
Even though the backend team at Ripple was small, we still followed best development practices that worked very well in our previous companies. Some of these practices included technical discussions around problem areas in our stack and writing and reviewing RFCs for upcoming significant areas of development and refactoring.
Calm acquired Ripple Health Group in early 2022, and I spent the following months helping to integrate our services with Calm and participating in technical discussions as part of the wider Calm engineering group.
When I started at Rally Health, the company was still in its infancy and was in the middle of pivoting to a new product and tech stack. I helped with this by migrating their backend code to RESTful APIs from server-side rendering libraries. Transitioning to RESTful APIs allowed us to transition to microservice-oriented architecture and divided our product into multiple web and mobile applications.
I then became the technical lead of the mobile development group, built the team and architecture, and helped develop one of the company's first mobile apps. Afterward, I expanded and branched out the mobile team to allow us to create five more mobile apps. These mobile apps were written natively, in React Native, or in a hybrid of both. My technical focus was not only on the development of these mobile apps but also on the design of their APIs and the architecture and health of the backend services.
As Rally grew to a much larger company, I was a member of the executive technical staff(ETS), which oversaw Rally's overall technical health and was responsible for high-level architectural discussions, reviewing and writing RFCs, and discussing any improvements or changes to Rally's development practices. The ETS became an essential part of Rally as we integrated more services and products into our backend services and as we rapidly adopted more and more users and received more requests per day.
United Health Group acquired Rally Health in 2017.
I started at Zynga in the Zynga Dallas studio while living in the Dallas area. I helped work on our upcoming new game's core tech and Facebook integrations. After transferring to the San Francisco headquarters, I led efforts to integrate the services I created in the Dallas studio into the broader Zynga organization.
With all the teams I was involved with at Zynga, dealing with an enormous flood of requests into our systems was always at the forefront of our responsibilities and discussions. We developed many methods of ensuring that our services were optimal and secure, which I've taken with me throughout my career. Additionally, bots were a problem area that we'd focus on occasionally. Bots consumed a significant portion of our resources at Zynga, and I developed systems that identified them and isolated them to prevent their behaviors from affecting the overall game economy.
When Zynga started to focus more on mobile games, I developed core systems and CMS tech in C# and Unity.
I joined Rocket Gaming Systems and helped integrate Rocket's tech with the newly acquired tech from Ihsoft. In addition, I led efforts to research and develop new hardware solutions that Rocket was interested in using in upcoming slot machine games.
To ensure the quality of the slot machines once they're "on the floor," I developed systems that stress-tested hardware shipped directly from the manufacturer. As a result, we detected manufacturing defects early, which prevented costly maintenance overhead in casinos.
I joined Paradigm Entertainment(a THQ game studio) a few months before shipping our next console game. After the game's release, I helped develop a new game engine and a few game prototypes. My time at Paradigm was my first experience as a software engineer in a large team and company. I learned and grew a lot with the more senior and talented team members.