My team makes the common infrastructure Google developers build services with. Our customers make products you've heard of, like YouTube, Search, and Maps. We focus on things like reducing development toil and making services more reliable, safe, performant, and scalable. We’re responsible for the frameworks for building services, the UIs and command line tools for operating the services, and providing quick-and-easy build and test setup for developers.

Lead a 15 engineer team supporting the Python programming language at Google. Our biggest accomplishment in my tenure was migrating the world's largest Python codebase from Python 2 to Python 3. This was a huge effort involving cooperation from hundreds of teams across Google. Through automation, my team was able to save Google hundreds of engineer-years worth of toil as we migrated the code base.

As a side project, I run Funny Money Bunny, a YouTube channel that makes getting filthy rich good clean fun.

* Led Wealthfront’s data engineering team* Helped grow Wealthfront’s data engineering team from the ground up.* Led buildout of Hadoop, and later Spark, ecosystem, including ETL jobs, data warehouse, dashboards, near-real time system, etc.* Led Wealthfront’s A/B testing infrastructure, and the analytics we use to scale our paid marketing efforts.* Previously led growth for Wealthfront, improving signup flow and funding process.

I worked on several infrastructure projects at LinkedIn. The one I'm most proud of was called Quick Deploy, a project which changed the way we wrote code at LinkedIn. It lead to a 20% productivity boost across the engineering organization at LinkedIn. I also worked on frontend infrastructure at LinkedIn, and I briefly managed LinkedIn's i18n team.

While at Agilent, I was the lead engineer behind Command Expert:http://tinyurl.com/AgilentCommandExpertThis is a PC application to integrate electronic test integration into Excel, Matlab, LabView, and other analysis applications. I came up with the basic idea, worked with customers to make it better, and implemented most of the UI.Prior to that, I worked on programming languages and user interfaces for distributed, real-time systems. This work was focused on electronic test customers who were using IEEE 1588 for clock synchronization in measurement applications:http://www.nist.gov/el/isd/ieee/ieee1588.cfm

While getting my PhD, I worked on three main project areas: control systems, simulation, and making CAD systems scale. Details of all my projects, including publications and presentations can be found at:http://ptolemy.eecs.berkeley.edu/Of this work, my master's project stands out as one of the more fun projects I ever worked on. I designed control algorithms to prevent pilots from flying aircraft into restricted airspace. This was inspired by the 9/11 terrorist attacks, and it was the most publicly visible project I have ever worked on. Due to the relevance of this project to the wider community, I regularly presented my work to journalists, government officials, and corporate executives, in addition to other researchers. Here's an old news article about what I worked on:https://www.newscientist.com/article/dn3893-soft-walls-will-keep-hijacked-planes-at-bay/

While getting my EE degree, I spent two summers and two part-time school years working on medical imaging research. When a patient has man-made metal in their body, like a metal filling or a knee pin, traditional CT scans of the area become too blurry for doctors to work with. Working with professors and graduate students, I implemented algorithms in cases when the shape and composition of the medical object were known. I also sped up some legacy code by a factor of 400, enabling radiation oncologists to use this technology during the treatment of cervical cancer. I worked with doctors at the Washington University Medical Center to apply this technology to the treatment of advanced cervical cancer.