I joined Roboto immediately after it raised seed funding, and immediately set about co-architecting its V1 public app from the ground up.I've made significant contributions across backend, frontend, security modeling + tenant isolation, build system, developer experience, private deploy-ability, and operationalization.

9 years at Amazon taught me a lot, but I decided it was time to try something new. Before actively pursuing new work, I took a couple months to work on house projects, visit family for the holidays, and then spend the winter skiing around the western US.

Embedded programming has always been a personal passion so I decided to take a break from web services to work on some lower-level applications.During this time, I worked on the device firmware team within the Amazon Halo organization. Halo focuses on wearable device, smartphone app, and cloud service based tracking of fitness, health, and overall wellness. The main goal of the organization is to improve the quality of life and overall health of our user base, which is a charter that's easy to get excited about!Specifically, from Jan 2020 to September 2021 I worked on the "Halo View" fitness band's firmware as the biometrics lead, focusing on the code for controlling sensors and scheduling fitness compute algorithms, as well as logic for improving our build system and seamlessly incorporating library drops from other 1P and 3P collaborators.During this time I also mentored a number of engineers, facilitated dozens of interview loops as a "bar raiser" (ending my time at Amazon at 200+ total), helped draft standards for design and operations excellence, and acted as a general consultant to many more junior engineers across a number of teams.

I spent a while working on web services teams for Prime Air, an Amazon program to deliver packages via drone.January 2019 - December 2019:I acted as the software lead and first engineer on an initiative to build a drone "airport" that operated out of an Amazon fulfillment center. I owned the initial system architecture design as well as many early non-technical product decisions while we hired a product management team. I acted as an engineering liaison between SDEs, SDMs, TPMs, PMs, and PM-Ts on dozens of teams across Prime Air and various Amazon.com and warehouse operations organizations. I acted as the primary technical representative in discussions with Prime Air's senior leadership about this initiative.During this time I also participated in Amazon's "Bar Raiser" training program, and ran interview loops for a wide variety of prospective Prime Air hires spanning many disciplines of engineering and project management.October 2015 - January 2019:I worked on a team focused on solving web services problems for Prime Air which involved post-flight sensor data upload, persistence, security/access control, normalization, analysis, playback, and simulation. I joined as the first engineer on the data platform team, and helped bootstrap it to 15 engineers through interviewing, training, and mentorship.I acted as the team's technical lead, and owned the system architecture (either through personal design or review and approval of peer designs), significant component implementation work, and operational support for a complex flight data ingestion and analysis pipeline.

See above

I maintained the Amazon.com system for storing and processing petabyte-scale anonymized customer behavior data, and helped design the next generation equivalent system. I usually describe it as the system that did the unglamorous preprocessing so teams like the one who owned the "customers who buy X are interested in Y" widget didn't have to run a hundred trillion data point sort each time they wanted to consider new numbers or tweak their heuristics.The team owned one of the largest Apache Hadoop clusters in the world, clocking in at thousands of hosts. I wrote and maintained numerous Hadoop jobs and auxiliary REST services for things like data access and daily/weekly RODB generation. I helped mitigate high-impact operational issues (cluster uptime, service uptime, data quality) as a member of a 24/7 oncall rotation, interfacing with customers through trouble tickets, office hours, and adhoc meetings and discussion.As the team grew, I trained and interviewed new software and business intelligence engineers.I spent much of the back half of my time on Clickstream doing early thinking and design work for the next generation re-architecture, which set the tone for the implementation work that would be carried out over the next few years.

My team was working on a security-oriented custom android device with some fancy hardware encryption, and I worked on building out functionality to view the X.509 certificates loaded onto the device. This was all Android 2 and 4, I focused on the background code to fetch the certs, transformation logic to X.509, and the UX to display, bind, and unbind certs.