gComp - internal tool that managers use to plan total compensation for their reporting employees

Prosper - internal tool that all googlers use to view their compensation and benefits)

gThanks

I worked on many business-critical projects:

I created a team documentation site for the team (respecting confidentiality levels) including a new teammate guide. I was on 24/7 oncall rotations for production issues

Typescript, Unit testing, Integration testing, WebDriver, GSLB (Cloud Load Balancing), Blaze

I was a core contributor in the full User Interface rewrite of Google Ad Manager from GWT Front End to AngularDart. This was a massive multi-year multi-team complete UI redesign and rewrite effort which required adding and modifying features full stack. I was the owner for three business critical web pages for publishers in creating and overseeing negotiation with buyers. I also worked on the redesign and rewrite of Private Auction Troubleshooting which displays diagnostic information about a deal and why some bids failed and due to what reason (34k+ visits per month to the page).

My work included writing design docs, ensuring all features are rewritten in the new web pages, identifying and removing any unnecessary features, and fixing any issues/bugs along the way. I created components that are used across multiple Front End pages. The pages were released to be utilized by publishers with minor to no issues. I worked closely with other teams, UX Designers, Project Managers, and Tech Writers. I wrote documentation for QA testing and fixed 60+ major issues/bugs.

I also worked on SLO exceeded monitoring to improve latency for Deals, Programmatic Serviceability to find and resolve various customer issue areas, decrease latency on various API calls, and cleaned up deprecated code. I have created and maintained internal documentation for the team that they still use to help train new Googlers to the team.

Technologies used: AngularDart with HTML and CSS, Java, ACX (web application ecosystem), Stubby (aka gRPC) API, GWT (Google web toolkit), F1 database, Unit testing, Integration testing, end-to-end testing, WebDriver, Guice dependency injection, PQL/GoogleSQL, PLX, Borg (Kubernetes equivalent), GSLB (Cloud Load Balancing), Rapid/Sisyphus (Google's internal release tool), Boq (Internal Microservice system), and Blaze.

Programmatic Direct Deals are publisher and buyer negotiated deals from Google Ad Manager (formerly DoubleClick of Publishers) to Google Display and Video 360 (formerly DoubleClick Bid Manager) or Google Authorized Buyers (formerly DoubleClick Ad Exchange).

I owned many high revenue generating products:

* CPM Sponsorship deals are programmatic deals that provide exclusive access to inventory for a period of time on a cost per 1000 impressions viewed basis. This project has $1 Million - $10 Million Annual Recurring Revenue impact with many major publishers requesting this feature. I worked closely with other teams to ensure the deal is working properly from creation, negotiation, serving, billing and reporting. This product was GA released to be utilized by all programmatic publishers without any issues/bugs.

* Terms and Conditions are legal contracts between Publishers and Buyers to enforce some rules of the deals. This allows deals to be made with large values with legal bindings in place for publishers and buyers. I worked on the Buyside and Marketplace teams to propagate the terms and conditions between sellside and buyside.

* Complex roadblocks serve multiple same size creatives on the same line item on the same webpage. This is a very important feature that publishers requested for many years. This project generated millions of dollars in revenue from major publishers every year.

This project was GA released to be utilized by publishers without any bugs.

* This project allowed Ad Exchange only publishers to utilize Preferred Deals in Google Ad Manager which resulted in millions of dollars in revenue every year.

This project was GA released to be utilized by publishers without any issues.

Stubby (aka gRPC) API, XML, F1 database, PQL/GoogleSQL, PLX, Unit testing, WebDriver

I was a core contributor who worked with the Full Stack in the migration of DoubleClick Sales Manager into our simplified Programmatic Workflow and aided in migrating to other Sales Managers (e.g. Salesforce). Sales Manager was a large product which involved 170 major publishers. I rigorously tested and fixed major publisher accounts (e.g. Disney, Spotify, Amazon, New York Times, etc.) for migrating off Sales Manager to utilize Google Ad Manager accounts. The migration was done seamlessly, without any service outages or significant loss in revenue. This migration also involves deprecating and removing a lot of unnecessary code. I created extensive documentation from the Sales Manager handoff from the Shanghai team which was crucial to resolve bugs that publishers filed.

Technologies used: Java, WebDriver, Borg (Kubernetes equivalent), Rapid/Sisyphus (Google's internal release tool), Annealing (Google’s internal release monitoring), GWT (Google web toolkit), XML, F1 database, Guice dependency injection, PQL/GoogleSQL, and Stubby (aka gRPC) API.

Google Classroom is Google’s Learning Management System to utilize existing Google services (GSuite for Education) and offer them to schools, universities, and consumers. I was the core contributor for implementing course ownership from one teacher to another including all Classroom and GSuite resources associated with a class. I was the lead in designing this transfer, researching what resources are associated with a class and how they need to be transferred and implementing the transfer of resources.

My work involved collaborating closely with Product managers and interaction designers to provide an easy way to initiate, send/receive notifications of class ownership and become a class owner. Course ownership transfer involves all resources associated with a class such as Calendar, Drive, and Docs, Sheets, Slides, Drawings, Forms, etc.

The project launched successfully as part of the Back to School launch for Google Classroom in August 2017.

Technologies used: Java, Javascript, Stubby (aka gRPC) API, Protocol buffers, Guice dependency injection, Soy templates, localization, Dremel and Google’s unified email/mobile notification system.