Jerry Pham is a Principal Product Designer with 13 years of experience crafting end-to-end UX, UI and interaction designs for web and mobile across B2B and B2C products. Based in San Jose, he has led design efforts at companies from startups to Rivian, launching core platform tools that power enterprise fleet operations, self-service reporting, and sensitive-record discovery. He combines full-stack product design ownership—user research, IA, prototyping, design systems and QA—with close collaboration across PM, engineering and stakeholders to drive measurable product impact. Unusually for a designer, Jerry also contributes to back-end open-source projects like Apache Spark, Iceberg and Livy, improving stability, security and performance. He is a co-inventor on a granted US patent and has a track record of scaling design practices and mentoring teams during rapid growth and acquisitions.
13 years of coding experience
6 years of employment as a software developer
Bachelor of Fine Arts Digital Media, Bachelor of Fine Arts Digital Media at San José State University
Apache Livy is an open source REST interface for interacting with Apache Spark from anywhere.
Role in this project:
Back-end Developer & DevOps Engineer
Contributions:79 commits, 345 PRs, 66 pushes in 3 years 7 months
Contributions summary:Jerry primarily contributed to the development and maintenance of the Apache Livy project. Their work involved creating and improving scripts related to build and release processes, including scripts for merging pull requests and handling the Apache release process. Furthermore, the user addressed security vulnerabilities and package name updates. They demonstrated skills in scripting and managing the project's build infrastructure.
Livy is an open source REST interface for interacting with Apache Spark from anywhere
Role in this project:
Back-end Developer & DevOps Engineer
Contributions:56 commits, 143 PRs, 458 comments in 8 months
Contributions summary:Jerry primarily focused on improving the Livy server's functionality and maintainability. They fixed a bug in the `getRequestPathInfo` method, preventing "null" values from appearing in request paths. Additionally, the user addressed security concerns by preventing internal configurations from being exposed to Spark and improving the security around the recovery state store folder. They also added support for statement canceling in interactive sessions.
emrapacheanywheresparkscala
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.
Request Free Trial
Jerry Pham - Principal Product Designer at On The Stage