I am a Staff Architect at VMware creating value at the intersection of applications and infrastructure. Over the years, I've had the privilege of working in high-performing teams within start-ups to large enterprises. Within these teams, I've worn many hats including team lead, software engineer, architect, and developer advocate. I thrive in teams with an affinity for getting things done, pragmatism, and open source. Since 2016, I've been working in the cloud native ecosystem with a focus on building, running, and managing large-scale Kubernetes clusters in production.
The following are languages, tools, and systems that I've used in the past year to write software, automate systems, and support applications. This list is by no means exhaustive.
At VMware, I lead an amazing team of humans responsible for working with enterprises to:
In pursuit of the above, we engage with the world's largest enterprises (financial services, telcos, and retailers) to engineer success on top of Kubernetes. We are a highly-strategic team with years of experience running distributed systems in production. Additionally, this multi-faceted role means each team member must maintain competency in software development, infrastructure, networking, communication, and leadership.
At VMware, I have:
At Heptio, I was a member of technical leadership and an individual contributor on a high-performing team. Heptio was created by 2/3 founders of Kubernetes and consisted of many industry leaders. Our focus was to bring upstream Kubernetes to the enterprise.
The field engineering team was considered the "tip of the spear" in that we went into enterprises and helped them fill gaps in the Kubernetes ecosystem. Our team spent the majority of its time writing software to fill deficiencies in Kubernetes along with providing architecture consulting to enterprises.
At Heptio, I had:
At CoreOS, I was hired as the first Software engineer with the intent of splitting time between engineering and field work. CoreOS was the company that created Container Linux, etcd (datastore of Kubernetes), rkt (container runtime), and Tectonic (Kubernetes distribution). During my time there, I worked with my director to establish a team that grew to over 30 people before being acquired. Our team's focus was primarily helping customers be successful on top of Kubernetes and be active contributors to upstream Kubernetes.
At CoreOS, I had:
At MuleSoft, I started as a services engineer and ended as a senior engineer. Our team's focus was to embed at MuleSoft customers and assist in building Java/Spring-based API and middleware solutions. Along with development, I specialized in performance engineering for many latency-sensitive customers. These scenarios involved extensive performance testing, code optimization, and JVM tuning.
At MuleSoft, I had:
At Hyland Software, I was hired to provide internal technical training to all software developers and professional services teams to ensure their success atop OnBase. During my time at Hyland, I embedded myself amongst software engineering groups and did immense amounts of self-study to establish my development skills. Overtime, I was able to contribute to products, projects, and PoCs inside Hyland. This made clear my love for software development and lit the fire to get involved in teams doing development in the context of to-be production workloads. Thus, my eventual move to MuleSoft.
Along with my day job, I love staying involved in open source communities and teaching topics around software/infrastructure engineering.