Anthony Hsu is a Staff Software Engineer in Sunnyvale with 12 years of experience building and optimizing large-scale distributed systems, currently working on AlloyDB at Google. He has deep hands-on expertise in storage and replication for Postgres-compatible systems, and a strong background in Hadoop/YARN and workflow orchestration from his leadership on TonY and extensive Azkaban contributions. At LinkedIn he shipped infrastructure for distributed ML (Horovod, history server) and led data format and compliance efforts that materially reduced storage and compute costs. His work spans backend, DevOps, and performance tuning—often surfacing in open-source fixes that improve job runners, log parsing, and deployment reliability. Anthony holds an M.S. from Carnegie Mellon and a B.S. from Yale, blending rigorous academic training with a practical knack for productionizing complex data and ML workflows.
12 years of coding experience
10 years of employment as a software developer
B.S. cum laude with distinction in major Computer Science, B.S. cum laude with distinction in major Computer Science at Yale University
M.S. Computer Science, M.S. Computer Science at Carnegie Mellon University
TonY is a framework to natively run deep learning frameworks on Apache Hadoop.
Role in this project:
Back-end Developer & DevOps Engineer
Contributions:12 releases, 77 commits, 174 PRs in 9 months
Contributions summary:Anthony primarily focused on improving the build process and infrastructure of the TonY framework. Their contributions include running Play tests during the build, removing and refactoring registration timeout and retry logic, and injecting Azkaban metadata and TonY version into the configuration. They also addressed issues related to TensorBoard port management and other deployment aspects. Additionally, the user worked on resolving issues related to the distributed MNIST TensorFlow example and the TonY Portal.
Contributions:146 commits, 16 PRs, 7 pushes in 1 year 6 months
Contributions summary:Anthony primarily contributed to the Reportal plugins, focusing on enhancing and refining the Azkaban plugin ecosystem. They made improvements to the ReportalPigRunner, HiveRunner, and TeradataRunner job types. The user also implemented new features related to report email notifications, and adding functionality to the Reportal edit page.
jenkins-api-pluginpluginazkabanpluginsjava
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.