Shashank Shankar is a Product Manager II at Microsoft Azure with 11 years of software engineering and product experience building B2B2C cloud, ML/AI, and API-driven platforms that enable customers to develop their own applications. He combines hands-on backend engineering expertise—from contributing substantial refactors to OpenStack Neutron to shipping cloud features at Intel and Workday—with product leadership that helps customers adopt Azure Blob storage and labelled-data pipelines at scale. Comfortable both in code and strategy, he previously built Kubernetes operators in Go and helped enterprise SaaS expand into GDPR-sensitive regions. He also volunteers as a Venture Partner at GoingVC, sourcing and evaluating early-stage startups, reflecting a strong interest in technology investing and founder-side problems. Based in Mountain View, he balances engineering curiosity (open source, Dota 2, photography) with practical product delivery across cloud and AI domains.
11 years of coding experience
5 years of employment as a software developer
Pre-University, Physics, Chemistry, Mathematics, Biology, Pre-University, Physics, Chemistry, Mathematics, Biology at MES PU College of Arts, Commerce and Science
GoingVC
Master of Science - MS, Telecommunications Engineering, 3.5/4, Master of Science - MS, Telecommunications Engineering, 3.5/4 at The University of Texas at Dallas
Bachelor of Engineering - BE, Telecommunications Engineering, 8.4/10, Bachelor of Engineering - BE, Telecommunications Engineering, 8.4/10 at Visvesvaraya Technological University
Fundamentals of Product Management, Fundamentals of Product Management at Stanford Continuing Studies
Software Product Management, Software Product Management at UC Berkeley Extension
OpenStack Networking (Neutron). Mirror of code maintained at opendev.org.
Role in this project:
Back-end Developer
Contributions:10 commits in 3 months
Contributions summary:Shashank primarily focused on refactoring and relocating database models within the OpenStack Neutron project. Their work involved moving provisioning block and router extra attributes models to address cyclic import issues. This included modifying existing code and introducing new objects for managing router attributes and provisioning blocks. The changes indicate a focus on improving the project's structure and addressing dependency issues.
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.