Philip Peterson is a versatile software engineer with 14 years of experience spanning game development, startups, and enterprise SaaS analytics, currently based in San Francisco. He has held roles from co-founding a major fan-driven remake of Riven to shaping reservation systems as a software architect at Hilton, demonstrating both product intuition and system-level design. Philip ships front-end and full-stack solutions—contributing to projects like Yew (Rust/Wasm) and improving test infrastructure for Plotly's Dash—reflecting strong cross-language fluency and commitment to quality. His work blends pragmatic engineering with user advocacy ("Fighting for the user!!"), favoring reliable, testable systems and clear developer experience. Notably, he led community-driven game development that culminated in a commercial release, an uncommon bridge between hobbyist OSS and commercial IP. He holds a CS degree from the University of Florida and a track record of moving projects from prototypes to production at scale.
14 years of coding experience
15 years of employment as a software developer
Bachelor of Science (B.S.) Computer Science, Bachelor of Science (B.S.) Computer Science at University of Florida
Rust / Wasm framework for creating reliable and efficient web applications
Role in this project:
Full-stack Developer
Contributions:5 reviews, 9 commits, 20 PRs in 1 year 11 months
Contributions summary:Philip made several contributions, primarily focused on updating the `yew` framework's examples and core code. These changes involved refactoring code, renaming methods, and removing unused components. The user also added a new example for password strength and updated the build and server infrastructure. These actions suggest a focus on improving the project's functionality and usability.
OBSOLETE: now part of https://github.com/plotly/dash
Role in this project:
QA Engineer / Test Automation Engineer
Contributions:7 commits, 1 PR, 3 comments in 1 day
Contributions summary:Philip primarily focused on enhancing the testing infrastructure of the `dash-core-components` repository. Their contributions included adding new tests, refining existing ones, and addressing test-related issues. The changes involved creating and modifying test files to ensure the component's functionality and behavior were thoroughly tested. This involved writing and updating test cases to cover various scenarios and edge cases.
dashpythonplotly-dashplotlydata-visualization
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.