Aaron Barnes Email & Phone Number

I managed and optimized the Snowflake data warehouse for cost efficiency and operational utility, while also designing scalable data pipelines for ingesting Manufacturing and IoT time series data. I developed services bridging internal operations platforms with proprietary hardware, enabling communication where it was previously challenging. Additionally, I wrote software to enrich manufacturing systems with data from diverse sources, generating actionable insights. My role involved providing frontline support for a sizable codebase, swiftly identifying and resolving bugs to address client and field engineer issues in real-time. I also crafted mobile applications and associated services empowering manufacturing personnel to conduct electrical tests at various production stages and built comprehensive suites of tools to validate physical device sensors and systems.

I maintained multiple microservices crucial for sales and employee onboarding processes. I took charge of leading and facilitating code releases post-sprint cycles, ensuring smooth transitions during off-cycles. Additionally, I served as the frontline support specialist, swiftly addressing emergent issues during peak sales periods. Furthermore, I diligently investigated and resolved issues hindering the progress of Quality Assurance (QA) activities, ensuring seamless software testing and release cycles for the team.

I led a team of five engineers on the newly reformed/restructured Integration’s Team. This team was a combination of my first team and my latest team. Our goal was to offer one point of communication for any and all tech-related issues or operational work. Using everything I learned up to this point, I was able to lead the team in building tools that would streamline most of the common tasks and setup work we had to do. This made tasks that would normally take an hour take only 15 minutes from start to finish. Now that the team had more time to do project work, my next goal was to build a tool for our users that would provide them with information that initially only we had access to. When the tool was released, users were able to access the information they needed themselves, saving both them and us valuable time.The next big goal for my team was to build a system that would combine our two feeds systems and let users configure the feeds themselves, rather than requiring tech resources. The completion of the new feed system meant that all of the team’s previous work was able to be done by only one person. Once the team’s previous work was optimized, we started to assist another team by taking on their excess work and building tools for a revenue critical system.

Joining Rakuten was a vast change from what I had been doing. Everything they did moved faster, and they used open source software stacks. My team worked with the customer services department, and was in charge of making operational changes for all of the company’s clients. Everything was new to me, but I was able to become a contributing member of the team within my first week. After a few months I was moved up to a problem-solving role where I would find and fix issues that were discovered. I was able to find the root cause of some common issues and apply a fix to prevent them from happening again.I was soon moved again, this time to the Partner Integrations team. This team worked with our 3rd party vendors to pull their data into our system. They also gained responsibility for the feeds system, which I had worked on in my first team. With my previous knowledge, I was put in charge of owning the feeds system. I focused on writing documentation and code standards to get new team members up to speed on the project.

Greater Salt Lake City Area

PRMI was my first job out of school, and it allowed me to learn and grow immensely. Within 6 months I was running the production deploys. A year later, I was the go-to for many of the company's crucial systems, which meant I was often working with various departments.