Below is my work experience that I have gained through various internships and extra-curricular activities.

Turnberry Solutions, Inc.

Click here to learn more about what I have learned from my internship at Turnberry Solutions, Inc.

Hytech Racing

Click here to learn more about what I have learned from my experience on the Hytech Racing team!

Storm Robotics

Click here to learn more about what I have learned from my experience on my high school robotics team!


Turnberry Solutions

As a software engineer intern at Turnberry Solutions, Inc. I was able to work on various software products for a fortune 500 company. I was able to learn a lot about microservice architecture as well as REST and SOAP APIs. I was also able to learn about SSO systems and dabble with predicitve analytics.

Single Sign-On

One of my primary projects with Turnberry Solutions was to implement a Single Sign-On system for the users of one of Turnberry Solutions’ products. To accomplish this, I used Okta and worked with the redirects that would be required to implement this system correctly.


Additionally, I worked on making small edits to certain APIs to improve customer experience. Turnberry Solutions gets a lot of requests from its costumers to improve their products and I was responsible for working on certain APIs that were later deployed into production.

Predictive Analytics

One of the most difficult projects I worked on for Turnberry Solutions was working on a Predicitve Analytics project using XGB Boost. Although I was not able to understand a lot of this as I was relatively new to AI and Data Science, I was able to understand the basics of how XGB Boost works and make an algorithm that utilized it.

Original Data Acquisition Dashboard
My Data Acquisition Dashboard

Hytech Racing

With my time at Hytech Racing, I learned a lot about managing both the backend and the frontend of a data acquisition system. From gaining essential information about the racecar through sensors connected via CAN bus to parsing it and sending it up to the AWS cloud with MQTT and storing it and presenting it using InfluxDB and Grafana/Plotly, I was able to work on all of the various parts of the data acquisition infrastructure.

Data Acquisition Dashboard

The Data Acquisition Dashboard was my primary focus on Hytech. There was much room for improvement when I joined, as there was only a list of values. I spoke with the chief engineer and he requested a graphical interface to better track trends. Therefore, I used Grafana and Plotly to help present the copious data from the MQTT server in real-time. This is an essential system for our live-telemetry process.

Transportation of Data through MQTT

I worked on setting up an MQTT server in the AWS cloud to allow the rapid stream of data coming from the car to be managed by the server. In this way, it would be easier to store the data in the database (InfluxDB) as well as present the data in a graphical and easier to understand manner through Grafana and Plotly.

Low-Level Work

I was also able to get to low-level/machine-level by looking at the CAN Bus messages and parsing them. I would look at the C structs and the binary and then parse it into a more usable form. From there, I also helped with setting up an RTOS (Zephyr RTOS) with the LTE to send data to the MQTT server.


Storm Robotics

Storm Robotics is an FRC (FIRST Robotics Competition) team that was a major part of my career in high school. I started off by jumping directly to the “varsity” team in my freshman year and had a very strong software focus. I eventually became software director where I was able to implement various autonomous features as well as improved workflows. This eventually propelled me to team director where I was able to focus on greater leadership problems like morale and overall communication between departments.

Work on Scouting App

My first year on Storm Robotics saw me focus primarily on the Scouting App. This was an Android app in which strategic information about other teams’ performcance during matches was placed into a database and was used to make strategic decisions and plans. I focused mostly on creating the user interface.

Software Director

As the Software Director in my sophomore year of high school, I focused on bringing industry best practices and implement them to the team. I brought ideas from agile development and GitHub best practices and enforce them onto my team. In addition, I encouraged a lot of commenting on each part of the robot so that future generations can look back and understand what was happening. This has led to a robust robot with a lot of automation which helped us be a top robot for the short season (interupted by covid).

Team Director

I was selected as the team director for the junior and senior years of high school. This was during the time that the Covid-19 Pandemic was very active. This led to having a virtual season my junior year and our first in-person season my senior year. During this time, I had to focus on a lot of holistic challenges like keeping morale up and ensuring proper transition of the knowledge base. It was difficult but I learned a lot about leadership and fostered a great team culture.