Philip Moltmann is a Staff Software Engineer with a decade of experience building embedded and OS-level software, currently working on in-car systems at Waymo after a long tenure on Android frameworks at Google. He combines deep kernel and hardware-facing expertise—from VMkernel memory management at VMware to Android printing, USB, and package installation—with higher-level API and system app development. As Google's Android privacy lead he balanced platform stability and feature work, and his open-source contributions include practical fixes to core Android tools like Monkey and enhancements to Mockito and dexmaker for better testing on Dalvik/ART. Philip is comfortable across the stack, shipping reliability-sensitive features that touch boot, drivers, and user-facing services. Based in Menlo Park, he brings a pragmatic engineering style focused on compatibility, testability, and maintainability in complex, safety-critical environments. An understated strength is his knack for navigating presubmit test and API migration pain points to keep large platform codebases healthy.
10 years of coding experience
12 years of employment as a software developer
Diplom-Informatiker (Master's), Computer Science, Diplom-Informatiker (Master's), Computer Science at Universität Karlsruhe (TH)
A utility for doing compile or runtime code generation targeting Android's Dalvik VM
Role in this project:
Back-end Developer
Contributions:56 commits, 26 PRs, 54 comments in 11 months
Contributions summary:Philip's primary contribution involved enhancing the `dexmaker` library, which is a utility for code generation on Android's Dalvik VM. They added support for mocking final classes and methods on Android by integrating `dexmaker-mockito-inline` using a JVMTI agent. The user also updated the project to Mockito 2.12.0 and addressed stack trace cleaning. Furthermore, they modified the build system to use newer gradle versions and upgraded the API level.
Contributions:9 commits, 6 PRs, 45 comments in 1 month
Contributions summary:Philip primarily contributed to the testing framework, focusing on enhancing the capabilities of the Mockito library. Their work involved addressing issues related to exception handling within real method invocations, and refactoring parts of the internal API, specifically the InstantiatorProvider, as part of a migration to fully public APIs. They also added new tests for the InstantiatorProvider2 to ensure proper plugin selection and correct mock initialization and exception handling within a testing context.
test-automationjava-librarytestingmockitounit
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.