Experience
I work on security features of the Android Operating System. Our team is responsible for protecting billions of Android users from a wide range of security threats.
Some of the user-facing features I have contributed to include:
- Android Safe Browsing — protecting users from dangerous websites and downloads across the platform.
- Android Advanced Protection Mode — providing the strongest security settings for users at elevated risk, such as journalists and public officials.
Beyond these visible features, I've worked across a range of platform security efforts that are harder to summarize but equally critical to keeping Android secure.
I worked within Capital One's retail banking line of business, building enterprise-scale solutions for product and customer data. The work involved modernizing legacy systems onto cloud-native microservices architectures using Node, Python, React, and Kafka.
Chariot builds software products with small teams of highly capable engineers. I worked on three consulting projects spanning fintech, IoT energy management, and neuroscience data platforms. The variety was the best part — each project brought a different stack, a different domain, and a different team.
I was a senior developer on an enterprise Court Management System (CMS). The software serves courts in the U.S. and abroad, streamlining processes such as document management, courtroom scheduling, financial accounting, and much more.
As a member of the accounting team, I helped implement a configurable financial system to support various processes including fee calculation, payment processing, and general ledger accounting.
I implemented and extended SAP products in the logistics space, focusing on Transportation Management and Extended Warehouse Management. The role started as configuration but evolved into development as I learned to build custom enhancements in ABAP.
As a supply chain major coming out of undergraduate school, this was a great job. A lot of things I did revolved around spreadsheets, and involved interacting on a production floor. I fell in love with coding via the Microsoft Office Suite (Excel, VBA, and Access).
Little did I know, a decade later Microsoft would be popular for different things and I would be a Typescript fanboy.
Background
I have a deep appreciation for programming languages and type systems. I prefer languages with robust type systems that shift bugs and design problems as far left as possible. That said, I've worked professionally in over a dozen languages, and if my career has taught me anything, it's that the best tool is the one that fits the problem — and that I can pick up new ones quickly. With AI transforming how we write software, that adaptability matters more than ever. These days, markdown might be the most important programming language of all — and I've been leaning into that.
At Google, I work on Android Platform Security, writing Rust, Java, Kotlin, C, and C++ across the platform. My current focus is a system using uprobes and eBPF for rapid deployment of telemetry and abuse mitigation. I've also contributed to user-facing features like Safe Browsing and Advanced Protection Mode, and developed static analysis tooling with Android Lint.
I started my career in supply chain and logistics, where I fell in love with programming through Excel and VBA. That led me to SAP, where I went from configuring warehouse systems to debugging and extending them in ABAP.
A master's degree in computer science opened the door to full-time software engineering. At Thomson Reuters, I worked on a large-scale enterprise Java application. At Chariot Solutions, I got to work across a wide variety of stacks on short-cycle consulting projects — Scala and Akka for event-sourced systems, React and Vue on the frontend, Node and Python for APIs, all deployed on AWS with Terraform and CloudFormation.
At Capital One, I worked on cloud-native microservices in a large retail banking organization — building data synchronization pipelines with Kafka, services in Node and Python, and driving CI/CD adoption.
Education
GPA: 3.9
After too many years of dabbling, I committed to a technical career by pursuing a technical education.
The final few quarters of my degree were spent with a research group studying graph databases, specifically the exploration of graph data structures as they evolve over time. I worked with a brilliant Ph.D student named Vera Zaychik Moffitt. We have all moved on since then. If you d like to know more about the work, the website (which I built, don't judge) still exists here.
GPA: 3.8
I studied Supply Chain Information Systems, and minored in Spanish and International Business. SCIS was a degree from Penn State's business college. It was like a business degree combined with an industrial engineering degree, with less physics and more accounting.