I support a team of roughly 100 engineers that own the end to end messaging flows, storage, and related systems for Facebook, Messenger, Instagram, and more.

Supported teams of 10-40 engineers for Facebook's Video and Voice Chat mobile product experience and backend. Launches included Mobile Video Calling, Group Audio & Video Calling, Video Calling Effects, and an attempt at a new mobile app, Bonfire, as well as platform integrations with Facebook Live, Portal, and Instagram.

Engineering Manager for Kindle's messaging middleware that consists of a communication protocol, push services, and device to device team.We focus on supporting the launch of a new messaging middleware and custom protocol supporting bi-directional messaging over a long lived WebSocket based connection to enable cloud to device, device to cloud, and device to device communication and discovery. This middleware powers many special features on current and unreleased devices and products.Accomplishments• Amazon Device Messaging 2013 Launch: Provides the pipe to devices for delivering push messages.• Amazon Kindle Mayday 2013 Tablet Launch: Enabled audio/video signaling and remote device control between customer tablets and customer service agent PCs.• Amazon Instant Video Second Screen 2013 Tablet Launch: Enabled device to device communication between Amazon Kindle tablets, Amazon Fire TVs, Sony PS3 and PS4 and Samsung 2013 Smart TVs.• Amazon's Fire Phone 2014 Launch: Provided messaging that powers multiple key apps including Firefly and Maps.In order to provide persistent connectivity for our customers, we face regular challenges with:• Networking: Device firmware integration/validation, Wi-Fi and 3G/LTE networks, handling various restrictions from internet infrastructure like web proxies and firewalls, and TLS/TCP/IP gotchas• Battery: Adaptive heart beating, keep-alive optimizations to minimize wake-ups, wake lock leaks, firmware optimizations• Scale: Load balancer connection limits, managing more tcp sockets on a server than default number of allowed open file handles, connection and messaging throttling and back off algorithms, • Device Libraries: Maintaining multiple device libraries, on multiple device platforms (Android, iOS, JavaScript), for many use cases, across multiple client teams is hard.

Engineering Manager for Kindle Whispernet Services, providing ubiquitous wireless coverage for Amazon Kindle globally in over 100 countries.Our team focused on supporting new devices and their connectivity, international launches, improving customer experiences, and cost reductions.The Whispernet team owned:• Device gateway proxies that provide authentication, authorization, and accounting (metering) for device connectivity.• Push messaging via SMS, TCP, and UDP coupled with server-side queues.• Key business metrics including Kindle's Books in 60 seconds metrics• Carrier integrations to manage devices, SIMs, SMS, and connectivity.• Manufacturer integration to support device provisioningAccomplishments• Launching Whispernet 3.0 architecture, which migrated carriers from a tight integration (VPNs between carrier GGSNs & Amazon Prod Network + RADIUS AAA and SMPP connections to carrier SMSCs) to a looser integration (APNs with IP filters, RESTful web services, and automated CDR bill reconciliation).• Expanding Kindle's E-Ink Whispernet cellular carrier integrations from 3 to 7 supporting Whispernet 3.0 launches in Canada, Europe, Japan, and Brazil.• Launching push messaging support for the original Kindle Fire tablet in 2011.• Launching Kind Fire HD tablet's cellular support for AT&T (provisioning, notifications, and data plan purchasing).• Kindle E-Ink cellular cost savings including international roaming limits on 3G browsing and data compression.

Fulfillment By Amazon (FBA) is a highly successful Amazon product, which takes away all the operational pain out of selling and fulfilling products online. FBA supports a range of customers, from one time sellers to fortune 500 sellers in 6 countries (United States, United Kingdom, Germany, France, Italy, China, and Japan). Check it out FBA at fba.amazon.com.I ran a team of software developers that followed scrum and agile software development practices and followed one month sprints. We dealt with interesting and challenging problems like dealing with massive scale, financial transactions, and non-trivial business logic & algorithms.Specifically, my teams owned:• Providing sellers visibility and tools to manage their inventory.• Monitoring FBA inventory and assessing appropriate fees and reimbursements.• Ensuring FBA inventory is available for sale on Amazon websites.• Providing a robust and flexible report framework to support various FBA reports.

I was the fourth developer to join the Fulfillment by Amazon team. At first we had just a few beta sellers that were very patient with out progress and grew it into thousands of successful sellers and millions of happy customers.This was very challenging and rewarding position. I defined, designed, and developed solutions to problems with ambiguous requirements, large scale issues, financial transactions, etc. that had direct correlation to the success of the product. As a FBA SDE, I was best known for owning and delivering a tier-1 service to map inventory and seller listings (FNSkuMapper), delivering the initial workflow engine for FBA's offline shipping system (branded Multi-channel Fulfillment) with another engineer, and independently delivering FBA's reporting system.We changed the game in e-commerce and continue to do so with new initiatives within FBA. No longer do sellers worry about operations. They now focus on product acquisition, merchandising, etc. instead of worrying how they'll get thousands of shipments fulfilled each day.

Shipping Services owned configuration and calculation of shipping rates and rules (how can product X ship to address Y) and launched the Prime member free 2-day shipping option in 2005.We owned highly scalable systems that provided shipping information on the Amazon.com detail page, evaluated shipping eligibility and costs withing the checkout pipeline, and managed updates to Amazon.com retail and seller configuration. We developed in C++ and migrated a significant amount of our code based out of a monolithic system into a more distributed / Service Oriented Architecture (SOA) solution.

I was an intern for the Tivoli Event Console group within Tivoli at IBM. I learned a bit about j2ee and IBM's love of documentation.