I jumped in with Amgen on a brief 6 month contract to help them build out a custom backend for a multicloud team management platform. I used AWS SAM (Serverless Application Model) to build out a serverless backend in Typescript. I built custom scripts to allow for deployment of a nested application stack, which allowed for a more modular and reusable codebase, unified under a single API Gateway resource. I also created and deployed several custom Lambda functions, set up roles and permissions and communication between services, and also designed a State Machine using AWS Step Functions to orchestrate the creation of new teams and their associated resources.

This is a proof of concept I built to illustrate how basic Bitcoin multisignature vaults can be constructed, allowing users to use m-of-n signature schemes for redundancy and security in custodying bitcoin. It's a single page app that allows a user to step through the flows of using an emulated hardware wallet to create addresses, combine them to a multisig address, recieve funds, and finally provide the signatures to spend from the multisig address.

The app is built with React and uses some JS bitcoin librararies to handle the cryptographic operations on the emulated wallet. I also used the buidl library to help handle the Bitcoin network interactions as well as protocol level details on the backend.

At Pearl Street, I helped to grow a web platform that was only a few months old at the time I joined. This product was crucial for allowing customers to interact with queue data and design simulations to be run on the core backend product, with the goal of saving customers time and money on their interconnection studies. The main features of the user-facing app I worked on involved Mapbox, MUI X DataGrid tables, and a custom React Hook Form implementation for creating the user-defined simulation scenarios. Also I mentored and brought other engineers up to speed on the tools and technologies (including Typescript, Cypress, and Terraform) in order to help them be more productive.

On the backend, I worked on many of the interfaces and serialization of the data models in Django, using the built-ins of Django Rest Framework and some pandas as well, one highlight being an Azure serverless function that passed summary results between different Django backend services. In addition, I improved our app's security by implementing a TOTP-based Two Factor Authentication flow using a trusted backend library to handle the details of the cryptography, which was a critical requirement for a product having access to CEII data.

I joined this energy industry company to help build out their data collection platform on their own custom built measurement systems in the field, with the end goal to help their customers save on costs and optimize their process times. I got to work on a wide variety of projects and wear a lot of different hats, but one of the highlights was the revamped web platform I built out during my last year with the company (seen above). The main technologies I used for it were Typescript/React, React Query for fast data updates and cache invalidation, and Highcharts with some custom state management for the dynamic visualizations. This took about a year to build all of the features, and I wrote almost all of the code, bringing in some contractors at the end to help parallelize the work, which I also acted as the tech lead for. This is probably one of the bigger highlights of my career, and it's a product I'm proud to have worked on. It's still in use at this time of writing by the engineers and customers of the company.

I worked on a number of backend tasks, and this is where I first started learning Django, fixing bugs and adding some features to support the frontend capabilities. I also worked on the field devices, which also ran Python on some single-board computers. Mainly the cloud configuration interface and the handling of data for the local on-site UI (run using a local Flask server). On a couple of occasions, I even got to don a hard hat and head out to the field to help install a 900MHz communication system I devised with the team’s systems engineer.

In my brief time at Clockwork I got my first feel for working on a “real”, production web software product with paying customers. Though the product was mostly done and the company appeared to be winding down at the time, I was still able to learn a lot by maintaining some legacy Angular and Flask framework code. I did build a prototype for a “sophisticated spreadsheet in the cloud” - type analytics product before I left for the next venture. I was also able to shadow the company's talented Site Reliability Engineers and gain a greater understanding of how Docker and Kubernetes are used both for development and larger scale deployments.

As an Applications Engineering Specialist with NI's RF/Wireless team, I designed custom test automation tooling, and provided debugging and software development assistance for customers doing RF SoC silicon validation and verification. There are a lot of small projects I worked on at NI in a variety of different engineering fields (think, technical sales demos) that I started my career with. They're too numerous to list here, so I figured I would focus on the bigger opportunities I worked on during my last couple of years there.

I helped a multi-million dollar sales opportunity of new RF test instruments for Intel's 802.11ax chipsets, and also went onsite with Qualcomm and a couple of other chipset manufacturers in the Bay Area. I worked with (and built!) a lot of LabVIEW and C# tools to assist customers with our driver API and measurement toolkits (WLAN, BT, LTE). I also had a unique opportunity early on to work on a software defined radio proof of concept for the National Center for Atmospheric Research's dropsonde radios.