Ryan Gregg
Principal Architect at Microsoft
Seattle, Washington, United States
Summary
🤩
Rockstar🎓
Top SchoolRyan Gregg is a Principal Member of Technical Staff in Seattle with 12 years of experience building cloud-native and developer-facing platforms across Microsoft and Google. He blends product leadership and deep technical expertise in Kubernetes, Knative, and serverless architectures—having helped turn Knative into Cloud Run and driven OneDrive’s developer platform into Microsoft Graph. Ryan is known for documentation-driven development and shipping practical tools like Markdown Scanner, and has contributed sample apps and docs for OneDrive and Knative to help developers adopt APIs and serverless patterns. He now focuses on enterprise-grade personal AI assistants through Project Lobster, combining open source collaboration with product-grade delivery. A former entrepreneur and long-time program manager, he pairs hands-on engineering instincts with strategic product stewardship to scale developer ecosystems.
12 years of coding experience
23 years of employment as a software developer
University of Kansas
Stackoverflow
2,015reputation
144kreached
84answers
1question
microsoft-graph-api
top-5%
Github Skills (25)
kubernetes10
javascript10
docker10
css10
dockers10
api-documentation10
go10
kubernetes-pods10
serverless10
microsoft-graph-api9
automations8
documentation8
automation8
cloud-infrastructure8
nodejs7
Programming languages (12)
Github contributions (5)
OneDrive/onedrive-api-docs
Aug 2014 - Oct 2017
Official documentation for the OneDrive API
Role in this project:
Technical Writer
Technical WriterContributions:1 release, 145 commits, 86 PRs in 3 years 3 months
Contributions summary:Ryan primarily contributed to the documentation of the OneDrive API. Their commits involved adding and modifying CSS files for styling, and also modifying a JavaScript file to demonstrate the use of the OneDrive SDK. Furthermore, they added code that provides users with a way to easily test out the capabilities of the OneDrive API. This included implementing a sample application that allowed for file picking and saving operations.
apionedriveonedrive-api
knative/docs
Jun 2018 - Dec 2019
User documentation for Knative components.
Role in this project:Back-end & DevOps Engineer
Back-end & DevOps EngineerContributions:63 commits, 10 PRs, 3 branches in 1 year 6 months
Contributions summary:Ryan contributed to the Knative documentation by adding and modifying several "Hello World" samples, including Go, Node.js, and C#. Their work involved setting up and modifying the code samples to work with Docker and Kubernetes. They also migrated samples from another Knative repository, updated a Git webhook sample, and implemented validation token support in an autoscale sample.
paasuser-documentationserverlessknativeistio
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.