I was the first engineer hired on PrizePicks’ Innovation Team, which is responsible for developing new Daily Fantasy Sports (DFS) games and expanding the company’s reach into new territories. I designed and built the first implementation of PrizePicks’ Tournament Service, a Go microservice responsible for running peer-to-peer contests, and which forms the backbone of PrizePicks’ new, highly successful Pick ‘Em Arena product.More recently, I've moved onto the Platform & DevEx team, building tools to improve PrizePicks' infrastructure and developer experience. These include:- Pathfinder: A static analysis tool that automatically generates OpenAPI spec files for backend microservices by examining Go source code.- Release Manager: A Slack-integrated service allowing development teams to easily control the release cycle for their individual projects.

At Sonar, I architected the company’s backend systems and served as the head of research and development. During my tenure, I saw the company scale from ten customers to hundreds, and dealing with the resulting technical challenges was one of my key responsibilities. In addition, I spent considerable time on production support, security auditing, DevOps, and network administration.Sonar analyzes its customers’ Salesforce metadata, which means it needs to regularly import absurd amounts of data by means of a nightly process that queries Salesforce’s various REST APIs. The scalability of this process was an ongoing concern and one to which I devoted considerable time. Shortly after joining the company, I implemented a scheme to shard our database on a per-tenant basis; prior to this point, we were on the verge of exceeding the capacity of the largest available RDS instances. Later, I performed a major rewrite of the import code that more than doubled its efficiency. Along with various other AWS right-sizing efforts and optimizations, this halved our year-over-year AWS spend.I was also largely responsible for building and maintaining Sonar’s DevOps infrastructure. I created the Azure Pipelines for Sonar’s frontend and backend projects using self-hosted agents, and I also administered all of the company’s AWS resources, which included EC2, RDS, ECS, and EKS, as well as Sonar’s VPC and networking infrastructure across multiple regions.The Sonar backend consisted primarily of a REST API written in C# and running on ASP.NET Core. Its backing store was a MySQL database hosted in AWS RDS. The nightly import process, which populated that database, was also written in C# and used TPL Dataflow to achieve high throughput. The web API ran as service in an Elastic Kubernetes Service cluster, and the import instances were hosted on-demand, per-tenant, in AWS Fargate.

At Jeeng, formerly PowerInbox, I led the development of a next-generation server that was responsible for performing real-time bidding (RTB) and distribution of advertising content using the OpenRTB standard. Based on Azure Service Fabric, the system was designed to scale to millions of requests per day.

I was part of a team of developers working on maintaining Sassy, a Java-based application used to administer Capital One's internal systems.

I worked on the backend of a system designed to do influencer marketing via Twitter and other social media platforms. Insightpool was a technological departure from my previous jobs; the technology stack was based on Go and Ruby.

From October 2014 to December 2015 I served as the technical lead for my development team at HotSchedules. In addition to my previous work as a senior developer, it was my responsibility to help improve and maintain the technical quality of the code produced by my entire team, as well as to take a primary role in the design and architecture of the features we were asked to implement.

My first team at HotSchedules (at the time, called MacromatiX) was dedicated to production support for Chick-fil-a, one of the company's major clients. I subsequently moved into research & development, where I made important contributions to the design and architecture of our mobile reporting dashboard and forecasting modules.Later, I was asked to serve as one of three developers representing North America on the company’s Enterprise Architecture Board, which is responsible for setting the company’s high-level technical direction.

At Zerowhale, I was responsible for designing and developing the core engine systems for the company's unreleased game project. The technology stack was based on Microsoft's XNA Framework and written entirely in C#.

I was a member of the production support team for Atlas, the software that was responsible for tracking the company's outstanding title loans. As production support, we were responsible for helping our users (operators in TitleMax's stores) resolve any issues that were beyond the expertise of our first tier of tech support staff. It was also our job to develop regular maintenance releases of the software in order to fix high-priority bugs.

Here I was responsible for independently developing both websites and desktop software for our clients, who operated in a number of different industries, including print media and education. The tech stack was a combination of .NET Framework, Microsoft SQL Server, and the Windows Presentation Foundation.

While at Cosairus, I was the primary developer on several projects for external clients, working primarily in C# and using Microsoft SQL Server for data storage.

I worked as a part-time freelancer for several years out of high school, mostly using ancient versions of PHP and MySQL to build basic CRUD-centric websites for local businesses.