Zachary Anker
Principal Software Engineer at Stripe
San Francisco, California, United States
Summary
🤩
RockstarZachary Anker is a Principal Software Engineer in San Francisco with eight years of experience turning messy, large-scale systems into reliable, maintainable platforms. At Stripe and previously at Square, he led migrations, consolidated services, and reduced operational pain—cutting paging by 40% and improving signup activation by 2% through pragmatic product/engineering tradeoffs. He mentors teams, evangelizes modern Ruby practices, and builds developer-facing libraries that make monitoring and incident response straightforward. An early platform lead at Placester, he designed APIs and data-import tooling that drove growth and high MLS coverage, showing a talent for pairing developer ergonomics with business impact. An active contributor to the open-source einhorn project, he implemented process control, preload garbage collection for copy-on-write memory gains, and enhanced worker monitoring with pinged request IDs. He thrives on diving into chaotic problems and surfacing simple, measurable improvements across people, code, and systems.
8 years of coding experience
7 years of employment as a software developer
Stackoverflow
4,510reputation
390kreached
59answers
0questions
file-upload
top-5%
ruby
top-5%
ruby-on-rails
top-5%
mongodb
top-5%
Github Skills (23)
socket-io10
process-management10
ruby10
socket10
system-administration10
concurrency10
testing9
file-upload9
ruby-on-rails9
mongodb9
cli8
command-line-interface8
command-line8
database-migration6
rest6
Programming languages (5)
Github contributions (5)
contribsys/einhorn
Jul 2018 - Feb 2020
Einhorn: the language-independent shared socket manager
Role in this project:
Backend Developer
Backend DeveloperContributions:16 commits, 16 PRs, 14 pushes in 1 year 7 months
Contributions summary:Zachary contributed to the core functionality of the `einhorn` project, a language-independent shared socket manager. They implemented features to control process spin-up behavior, including limits on unacknowledged and upgrading workers. The user also added unit tests and introduced the ability to perform garbage collection during the preloading phase to improve copy-on-write memory sharing. Furthermore, they integrated a ping functionality with request IDs for improved worker monitoring and debugging.
independenttcpsocketlanguage-independent
zanker/puma
Mar 2020 - Mar 2020
A Ruby/Rack web server built for concurrency
Contributions:8 pushes, 2 branches in 17 days
rackconcurrencyrubyweb-server
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.