Rocket Pro Navigate is a mortgage-specific large language model platform integrated into the Rocket Pro portal for mortgage brokers. The platform features an AI-powered sales coach for role play and objection handling, a Lead Scanner that analyzes client and prospect lists to identify refinance opportunities, a Document Analyzer to generate client-ready explanations, and many other tools for our mortgage partners. This was the first product I worked on at Rocket Mortgage. I helped design APIs and database schemas, patched security vulnerabilities, and architected the application to be multi-tenant in order to support Rocket's broker partner network.

Panther is a cloud-based SIEM (Security information and event management) cybersecurity company that I worked for. The product ingests logs from various sources and helps security teams identify threats based on pre-built and custom detection rules. One of its differentiators is that the detections were built as code - in Python. The backend was a mix of golang and python deployed to a largely serverless infrastructure and made extensive uses of queues, document-based data stores, data lakes, etc. The front-end was react and typescript and interfaced with the backend via GraphQL. My primary focus was on our detection and alerting interfaces, as well as integrating with third party services, and building out tooling for AI. Within these realms, I worked on the full stack of the Panther application - from architecting features, defining graphql services, and implementing backend logic in golang to building out front-end components and MCP servers.

The Teen Card is one of the last initiatives that I worked on before leaving PayPal/Venmo. This project was particularly challenging due to all of the restrictions and red tape that come along with building financial software for minors. This was the first time that we needed to introduce a new type of "delegate account," which would allow the teen to log in, be restricted from certain features, and also be managed by / linked to their parent's Venmo account. I spent most of my time on this project working with PayPal architects to design the systems to manage the delegate accounts, allow them to act as entities on our existing Venmo models, and also designed interfaces between PayPal/Venmo backends and our mobile app.

Venmo Gift Wrapping provided a fun way for users to send payments with animated greeting cards to friends and family. This was a shotgun project with a tight deadline that I co-led, architected, and developed alongside a small team of engineers. We leveraged AWS lambdas and DynamoDB to power the storefront for the different designs and proxied all mobile requests through the Venmo Platform API. The product shipped on time and launched with a beautiful short film produced by Wong Fu Productions.

Purchase Protection provided a simple toggle button for Venmo consumers to specify whether or not they're paying for goods or services while sending a payment. When a payment is sent for goods and services, the seller would be charged a small fee and the payment would automatically be covered under Venmo's Purchase Protection Program. If something went awry with the transaction, both the buyer and seller could be covered and reimbursed. I was the lead architect for this feature and designed the APIs, data storage and fee collection solutions.

The Venmo Credit Card offers up to 3% cash back on a user's top expenditures. After Venmo launched the ability for users to buy and hold cryptocurrency in their accounts, we decided to allow Credit Card users to automatically turn their cash back rewards into the cryptocurrency of their choice. I co-led the effort and worked with a small team of engineers to architect and build the new functionality that made heavy use of Cloudevents, PayPal's crypto APIs, and internal Venmo services to get the job done.

Amidst the start of the COVID-19 pandemic, the Chicago Venmo team was tasked with launching one of our most ambitious products. We worked closely with PayPal Credit, Synchrony Bank, and several internal Venmo teams to launch a branded Venmo Credit Card product in just 10 months time. I served as a tech lead and cross-company liaison to help architect and lead the development of the Credit Card servicing portion of the product. This included the data syncing, data structures, and API design to power the interfaces that a user sees when viewing or managing any information about their credit card in the Venmo Application. Later, I worked with a small team to add Cryptocurrency Reward functionality and also led the effort to get the Credit Card service's codebase upgraded to a more modern version of Python.

Venmo Payouts is a product that I got to build as a proof of concept and then turn into a full-fledged product alongside a small team of developers. The initial proof of concept was a shotgun hack to power a couple marketing campaigns that would allow merchants like Chipotle to send small payments to users in an effort to get them to buy burritos. After the success of the pilot campaigns, I acted as a tech lead and liaison between the Venmo team and PayPal MassPay teams to architect and build out a highly scalable merchant-to-consumer payout platform. I designed the APIs, data stores, and contracts between PayPal and Venmo.

The Venmo Debit card is a physical card that Venmo users can request to make purchases with their Venmo balance. This was one of the first products that we offered that would allow users to do more than just peer-to-peer payments with their Venmo wallet. I developed APIs and data stores related to storing sensitive user information including the federally required Customer Identification Program (CIP) user information. I also worked on various other debit card servicing APIs like the card design picker and card renewal.

Voter Registration SaaS was a thin, skinnable, multi-lingual, voter registration web application built on top of the DNC's Voter Registration API. This app lived in several places - most notably at the hilariously named gottaregister.com, which was mentioned by President Obama in several speeches, on television, within social media and even on reddit. In most states, this application basically acted as a fancy PDF filler that the user could print and mail in. However, it also allowed us to capture their information so that we could follow up and target that potential voter in the future. I inherited this application early-on and was in charge of making sure it was both stable and scalable while overseeing implementation of the campaign's evolving feature requests. It was one of the most interesting applications to scale because it rarely received organic traffic. It would get absolutely slammed when the president or some celebrity mentioned or linked to the application in speeches, on air, or in social media. This was addressed by extensive caching, limiting dynamic content on landing pages, and queueing API requests in the event of API downtime or latency. The queueing backup that I implemented (using Amazon's SQS) saved us thousands of voter registrations alone. We also made this application embeddable and eventually open sourced the core of it.

The 2012 Obama Re-election campaign was a firm believer in that the more voters who turn-out to vote the more likely Democrats are to win the election. With that, the campaign put a huge effort into cataloging voting locations and making sure voters had the tools they needed to find these locations. As the lead engineer of voter contact I architected and built the data layers, integration tools, and APIs to allow client applications to get at the data. I worked very closely with our data team, the DNC, voting location experts, and our front-end team. Despite the incredible challenges that came with the constantly evolving, incomplete/disorganized data and different laws/rules in each state, we built a comprehensive, nation-wide election day lookup tool. In addition to that, we built the first ever nation-wide "early vote" lookup tools. Not only was this data available via online lookup tools, it also integrated with DNC applications and allowed our phone canvassing applications to automatically display relevant voting locations for the canvassed voter.

Narwhal was the famous technology infrastructure behind Barack Obama's 2012 Re-election campaign. It was a Python-based interface and integration layer that allowed us to unify the disconnected pieces of what we knew about voters, volunteers, event-goers, voting locations, etc. I was one of the top 5 contributors to the Narwhal project. The integration side was a small web layer that handled syncing data with our vendors in real-time. Incoming data was saved to a local database and then became queued via SQS for translation and loading (by our integration workers) into the Narwhal interface layer. Here, I extended existing integrations and built some parts to sync voter applicant and precinct data. The interface side allowed us to use this unified data to quickly build dozens of client applications for various tasks across the campaign. I spent most of my time in Narwhal building and extending models and endpoints to support client application needs. The pieces I worked on helped support pollster surveys, phone canvassing, volunteer organizing, image processing, voting location lookup, incident tracking, etc. I also built a thin Ruby Gem that allowed our ruby based API consumer applications to quickly and easily interface with the Narwhal API.