Andrew Gwozdziewycz
Principal Engineer at Docker, Inc
Portland, Oregon Metropolitan Area United States
Summary
🤩
Rockstar🎓
Top SchoolAndrew Gwozdziewycz is a Principal Engineer with 17 years of experience building high-throughput, cloud-native infrastructure and operational systems from Heroku’s Logplex and metrics pipelines to multi-tenant secrets management at HashiCorp and AI-driven access tooling at StrongDM. Based in Portland, he excels at turning ambiguous product needs into executable architectures and operational plans on accelerated timelines, often founding or rapidly maturing new initiatives into private beta. He combines hands-on backend engineering—evidenced by contributions to the Heroku logplex router and significant query-performance optimizations—with cross-functional leadership that aligns product, security, and SRE concerns. Known for improving operational recovery times dramatically and introducing SLO-driven practices, he balances reliability, observability, and developer productivity. Andrew also brings a practical curiosity—he mentors teams, prototypes integrations (including AI assistants), and peppers conversations with dad jokes—making technical work both rigorous and human.
17 years of coding experience
14 years of employment as a software developer
Bachelor of Science - BS, Computer and Information Sciences, General, Bachelor of Science - BS, Computer and Information Sciences, General at Temple University
Stackoverflow
2,641reputation
372kreached
25answers
8questions
python
top-5%
Github Skills (19)
erlang10
apidoc10
api10
logging10
debug9
debugging9
python9
error-handling9
performance-optimization8
heroku7
coding-style6
lisp6
naming-conventions6
clojure6
android6
Programming languages (18)
Github contributions (5)
heroku/logplex
Nov 2014 - Jan 2018
[DEPRECATED] Heroku log router
Role in this project:
Back-end Developer
Back-end DeveloperContributions:20 commits, 8 PRs, 9 pushes in 3 years 2 months
Contributions summary:Andrew primarily contributed to the backend logic of the `logplex` project. Their work involved adding detailed logging information for debugging and performance analysis, especially related to HTTP drain responses and token timeouts. They also refactored code to improve readability and maintainability by extracting nested cases into a single function. These changes directly address issues within the log processing and routing functions.
herokurouter
apg/racket
Jul 2015 - Nov 2017
The Racket repository
Contributions:2 PRs, 5 pushes, 5 branches in 2 years 3 months
racket
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.