Ryan Schlesinger
Principal Software Engineer at deTASO
North Wiltshire, Prince Edward Island, Canada
Summary
🤩
Rockstar🎓
Top SchoolRyan Schlesinger is a Principal Software Engineer based in North Wiltshire, Prince Edward Island, with over 20 years of experience building reliable infrastructure and solving hard engineering problems. As President of Instance Consulting and former Ops Lead at Outstand, he grew a cloud footprint from a single instance to multi-cluster container orchestration with terraform, automated fault detection and resolution, and CI powered by Buildkite. He is an active open-source contributor in the Ruby ecosystem—notably improving Doorkeeper (OAuth2 token revocation and transactional robustness) and maintaining Restforce compatibility—bringing a security-minded approach to backend systems. Known for “painting bikesheds and shaving yaks,” he blends hands-on backend engineering, ops automation, and pragmatic leadership to deliver stable, scalable platforms.
16 years of coding experience
17 years of employment as a software developer
BS, Computer Science, BS, Computer Science at Virginia Tech
Stackoverflow
89reputation
10kreached
6answers
4questions
Github Skills (31)
oauth2-110
api-doc10
cookbook10
authorizations10
oauth210
faraday10
testing10
user-authentication10
authentication10
rails10
ruby10
chef-client10
api10
authorization10
chef-solo10
Programming languages (20)
Github contributions (5)
doorkeeper-gem/doorkeeper
Nov 2015 - Mar 2020
Doorkeeper is an OAuth 2 provider for Ruby on Rails / Grape.
Role in this project:
Back-end Developer
Back-end DeveloperContributions:7 commits, 7 PRs, 40 comments in 4 years 5 months
Contributions summary:Ryan made several contributions to the Doorkeeper OAuth2 provider, focusing on enhancing its core functionality and addressing specific issues. They added the ability to include `created_at` in token generation options, enabling customization. Key improvements included implementing token revocation for client credentials, ensuring proper security, and revamping the process by using transactions and row locks. The user also addressed translation errors and improved overall stability and API functionality.
omniauthoauth2-serveridentitydoorkeeperruby
sous-chefs/rvm
Mar 2011 - Oct 2011
Development repository for the rvm cookbook
Role in this project:Backend Developer
Backend DeveloperContributions:6 commits in 6 months
Contributions summary:Ryan primarily focused on improving the functionality and maintainability of the `rvm` cookbook. They fixed resource default actions, added missing types in metadata, and made all set actions explicit, contributing to a more robust codebase. The user also handled installing gems from local files and corrected versioning-related issues. This work demonstrates a focus on refining the core logic of the Ruby Version Manager (RVM) interaction.
cookbookrvmchef-resourcemanaged-by-terraformchef
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.