Senior Staff Software Engineer
CurrentTech Lead and Manager for Cross-Network Communication products in the Google Compute Engine’s Networking Control Plane. As tech lead, own the product definition (create the resource model that users interact with, and write user guides jointly with product management), architecture, high-level design, component design reviews, and code reviews. As individual contribute component design and implementation for some components of my products. As manager own the engineering roadmap for the products where multiple teams delivers the components of the high-level design. The teams do the component-level design and implements the REST API that exposes the resource model, validates the user requests to guarantee correctness, and translates the user requests to data plane configs. The organizing principle of the work is to allow consumers to access producer services (Google-managed or Third-Party running on GCP, or Google-managed running on GCP or Borg) using private IP address so that consumer machines don’t need a public IP address and traffic stays internal to Google cloud. The systems provide two sets of APIs: for end consumer, and for service producers.Service Connectivity Automation – Provides easy access to Google-managed services (e.g., Cloud Redis) which are built on Private Service Connect (PSC). Automatically configure (create resources and enforce policies on) consumer networks for the GCP service producers (e.g., Cloud SQL, Cloud Memory Store). PSC Propagation – For consumers of Network Connectivity Center, when one spoke connects to a Google-managed service, easily allow other spokes in the hub to connect to the service too.Peering to PSC Migration – Automated cutover of traffic from VPC Peering to PSC without changing consumer clients; requires transferring IP addresses from over VPC to its peer.Terraform Automation – Set up all the resources needed to connect to different managed services either from a VPC network or from on-prem.