David Baker is a Staff Software Engineer and seasoned architect based in New York with over two decades of experience designing and delivering enterprise-grade systems across server-side web applications and GUI tools. At Google since 2007 he leads Java/Kotlin foundations work and is an active maintainer and contributor to high-profile open-source projects such as Dagger, Guava, and Error Prone, where his changes improved dependency injection, static analysis, and code-generation tooling. He combines deep language fluency (Java, Kotlin, C/C++, Perl, Objective-C, SQL and more) with a pragmatic focus on maintainability and design patterns, regularly refactoring for clearer structure and better DI practices. Previously he held senior technical and leadership roles spanning consulting, product engineering, and CTO-level architecture, bringing business analysis into technical decisions. Notably, his open-source contributions include enhancements to compile-time checks and Kotlin analysis that help prevent common Java mistakes before they reach production. He pairs rigorous academic roots from Harvard with a hands-on engineering style that prefers robust, cost-effective solutions.
Contributions:3 releases, 1 review, 26 commits in 5 years 6 months
Contributions summary:David primarily contributed to the development of testing tools for Java and annotation processors within the `compile-testing` repository. Their work included enhancements to the testing framework to allow for more comprehensive diagnostic checks, such as warnings and notes. The user refactored and updated the testing API, introducing new classes and subjects to streamline and improve the compilation testing process. They also addressed several bugs, ensuring consistency and improved error messages in the testing framework.
Contributions:241 commits, 65 PRs, 29 pushes in 5 years 8 months
Contributions summary:David focused on improving the Dagger library by extracting common code and refactoring the codebase. They extracted code from classes to promote code reuse and created a base class, demonstrating a clear understanding of design principles. They also implemented support for @Reusable annotations, and fixed bugs related to handling of `@Binds` methods. This indicates that the user has experience with the internal workings of Dagger, suggesting the library maintainer role and a back-end developer role.
injectorandroidkotlindependency-injectionjava
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.