Ryan Gregg Email & Phone Number

Redmond, Washington, Us

Mountain View, Ca, Us

I joined the Serverless team on Google Cloud in Jan 2018 and worked on a new project from the earliest days. I guided the engineers how to take an open source project, known as Knative, into a product offering for Google based on Kubernetes, named Cloud Run. I’ve been involved since the early days, and help set strategy around open source and product to ensure we’re focused on customer success and running a business. I’ve kept our engineering teams focused on building a single product experience, despite having two implementations build in two remote sites. As the lead PM for the team in Seattle, I’ve also helped grow a team of product managers, starting as only PM on the project and growing it up to four, allowing the team to take on bigger challenges and continue to meet the needs of customers with our expanded scope.

I came to the OneDrive team in 2014 to build a new developer platform for OneDrive. My goal was to build a team to deliver a new platform for OneDrive ensuring that both internal and external partners would have a scalable platform for integrating their business with OneDrive. I hired and lead a team that built out our "1st = 3rd" approach, ensuring that the APIs we make public are the very same APIs we're using internally to build our own applications. The OneDrive API is used by thousands of applications and hundreds of millions of users, across both Microsoft and external partners.Along the way Microsoft Graph was born and I led our team to adopt Microsoft Graph as the API story for OneDrive, working with the Microsoft Graph team to define and adopt new patterns and practices for how to define great APIs, which were later published as the Microsoft REST API Guidelines. Our early adoption of Microsoft Graph has helped catapult Microsoft Graph to be the REST API for Microsoft, and showcase that big workloads like OneDrive and SharePoint can participate in cross-company efforts. After achieving our OneDrive platform goals, I expanded the role of the team to bring more capabilities around SharePoint into the Microsoft Graph, including Sites and Lists APIs, making files and lists across the SharePoint ecosystem available through Microsoft Graph.In this role I've also been driving our team's adoption of "documentation driven development" where we define the APIs and developer platform scenarios by using our end-user documentation as the functional spec. I've written Markdown Scanner, an open source tool for validating and testing our API documentation, ensuring that our API docs are always accurate, both with themselves and with the service. This toolset helps ensure that API docs are great across OneDrive and Microsoft Graph, and I've made it available to the community to use and improve.

- Managing a team of up to 4 Program Managers in strategic design and engineering efforts, aligned with multiple cross-team interactions across the MOD business group.- Lead planning and early R&D efforts around next generation experiences for communication- Deep technical problem solving within the constraints of a legacy code base- Focus on delivering great user experiences and high customer satisfaction

- Developed, tested, and deployed complex iPhone and iPad applications- Implemented multiple networking protocols in Objective-C to connect to a variety of services for data synchronization

.NET development working with embedded systems and HMI for oil and gas industrial systems. Developed scheduling software, inventory management and truck loading systems, and numerous internal tools.

Founded and ran a small consulting business, provided technology solutions and recommendations for a variety of companies in and around North East Kansas.