Jan 2021 – Oct 2024 · 3 yrs 9 mos · San Francisco Bay Area

Jan 2019 – Jun 2021 · 2 yrs 5 mos · San Francisco Bay Area

Jan 2016 – Jan 2018 · 2 yrs · Redwood City

Jan 2014 – Jan 2016 · 2 yrs · Sunnyvale, CA

• Responsible for GoDaddy's Personalization infrastructure including both the heuristic and the ML infrastructure. Also responsible for the core Data Sciences team.

Jan 2012 – Jan 2014 · 2 yrs · Palo Alto, CA

• Leading the engineering team thats building a tremendously scalable solution that helps Rokketlaunch re-invent how we interact with e-mail and what we do with it.
• E-mail is the primary async mode of communication and yet we consume it in the same way that we've always done regardless of the content.
• Using heuristics and machine learning we aim to present your messages in their most natural form and in the right context.
• But it all starts with being able to handle the volume of content people get in their email followed by categorizing it.

Jan 2011 – Jan 2013 · 2 yrs · Menlo Park, CA

• Lead the engineering effort for the Shazam TV infrastructure, which allows live audio from various sources to be tagable by end users. Responsible for creating the entire TV experience for Shazam from infrastructure to the end user viewable experience.
• Implemented the audio listener, which is a multi-threaded sever which on the back-end extracts audio from various types of feeds and data sources and on the front-end is a HTTP server that supports serving the data to various sources using long polling.
• Designed the receiver, which handles the user facing requests and performs the recognition
• Setup the San Diego Engineering office of Shazam as an extension of the Menlo Park Engineering team.

Jan 2009 – Jan 2011 · 2 yrs

• Leading and mentoring a group of engineers responsible for the development of all of Yahoo!’s Edge Services platforms which includes static and dynamic HTTP caching and the HTTP proxy that handles approximately 80% of Yahoo’s HTTP requests.
• During my tenure, the team also
• implemented the ESI specification to allow for page creation at the Edge thus reducing page serving time and providing a solution to excessive requests not bringing down the property.
• implemented a caching paradigm to allow for shared clustered caching
• Designed and implemented the core portions of the replacement for Yahoo’s traffic server (aka Apache Traffic Server). The platform provided the following benefits
• Allowed for easy development of both multi-threaded and multi-process network client and server software in C++. The underlying code can be asynchronous in nature, but the developer building on top of it is not made aware of it.
• The core is designed and implemented to create a lock-free programming model so that a thread and thus the underlying connections managed by that thread to ever be blocked.
• Using the platform and its support for plugins, we easily designed and implemented a multi-tier scalable HTTP push server built on Comet. This is going to be the basis for Yahoo’s HTTP push technology.
• Implemented the complete HTTP cache support within the proxy server.

Jan 2006 – Jan 2009 · 3 yrs

• Developed the framework for Y!Mail Anti-Spam’s Velocity based engine. The engine is used in various capacities to throttle flow of various different types of tokens into the system.
• Implemented the real-time Machine Learning framework for outbound message spam filter using multiple strong and weak features built on top of the velocity framework.
• Designed, implemented and deployed the Yahoo Mail Anti-Spam high and low volume Traffic shaping systems. The system dynamically throttles the rate of delivery into the system per host thus allowing Yahoo Mail! to maintain bulk delivery volumes to be below ham deliveries even though, the system sees about 10 times as many spams as hams on a daily basis. Furthermore, this has allowed Y!Mail to limit the need for MTA hardware as email volume has grown.
• Implemented Y!Mail's in memory cache. The cache is a server that provides the memcache API and its throughput, while adding the ability to have redundant copies of the data across nodes, distribute keys across caches and persist the data to various types of back-end persistent storages including mmaped based DBs, MySQL, etc. Yahoo Mail deployed a redundant, multi-colo memory cloud based on that software. The software has replaced all in-memory caches in Yahoo Mail delivery and anti-spam due to its support for storage of data in a non-volatile fashion and auto-replication of data in various colocations.
• Created the object oriented asynchronous I/O server framework, job handler and connection pooling support in C++ using State Threads for various asynchronous servers in Y!Mail.
• Technical leader and manager of the Y! Mail delivery team responsible for all development and operational related concerns for inbound and outbound messages for mail. Developed software that handles the scalability and maintenance tasks associated with handling >20Billion SMTP connections and >8B mails delivered per day.

Nov 2002 – Aug 2006 · 3 yrs 9 mos

• Senior Engineer responsible for all delivery related issues including development and operations associated with mail.yahoo.com. Maintained the Yahoo! Mail delivery system.
• Implemented the Object Oriented Domain Keys wrapper API.
• Implemented in PERL a real time configuration parser, reader and distributor for Yahoo! Mail machines. The configuration parser allowed a reader to read multiple different file types through the same interface and automatically pickup changes without having to re-read or reload the file.
• Implemented in object oriented PERL the performance running framework which is used to run performance tests on the MTA software and to run end to end monitoring on the MTAs
• Iimplemented the Yahoo Mail IP DataBase system.
• Implemented several features from delivery’s point of view, including Disposable Email Addresses and Anti-Virus for incoming delivery messages and messages downloaded by POP.

Jan 2001 – Jan 2002 · 1 yr · Cupertino, CA

• The project was a scalable http proxy and cache server
• Implemented an asynchronous SSL (secure socket layer) server in C++ using openSSL to be plugged into the front side of the http cache server so that we could natively handle secure requests and provide cached SSL documents too. Also implemented the client side SSL request handler so as to download the initial page from the origin web server.
• Implemented distributed shared storage of cache data to support cache coherency across multiple nodes.

Jan 2000 – Jan 2001 · 1 yr

Jan 1998 – Jan 1999 · 1 yr