Oliver Heeg is a Development Engineer with six years of experience building reliable back-end systems at Bosch and its subsidiaries, grounded in a Master’s in Wirtschaftsinformatik. He focuses on practical, maintainable refactors and API improvements—examples include creating robust DELETE endpoints and integration tests for SW360 and simplifying Maven Plexus container access in the widely used OSS Review Toolkit (ORT). Comfortable navigating enterprise codebases, he pairs careful testing and bug fixes (e.g., proxy handling for Maven repos) with modularizing parsing logic for clearer responsibilities. Based in Untergruppenbach, Germany, he brings steady delivery from prototyping to production in compliance and component-management tooling. Colleagues rely on him for pragmatic solutions that reduce developer friction and improve system observability.
6 years of coding experience
4 years of employment as a software developer
Bachelor of Science - BS, Wirtschaftsinformatik, Bachelor of Science - BS, Wirtschaftsinformatik at Hochschule für angewandte Wissenschaften Würzburg-Schweinfurt
Master of Science - MS, Wirtschaftsinformatik, Master of Science - MS, Wirtschaftsinformatik at Julius-Maximilians-Universität Würzburg
A suite of tools to automate software compliance checks.
Role in this project:
Back-end Developer
Contributions:1522 reviews, 313 commits, 237 PRs in 2 years 5 months
Contributions summary:Oliver primarily focused on simplifying and improving access to objects within the Maven Plexus container, which involved refactoring and implementing a new `containerLookup()` function. This resulted in more streamlined code for querying objects by class. The user also addressed a bug related to ensuring proxy settings were correctly applied to Maven repositories. Furthermore, they refactored the logic for parsing ScanCode results into a separate file.
Contributions:15 commits, 3 PRs, 14 comments in 2 months
Contributions summary:Oliver focused on enhancing the SW360 project by implementing functionality for deleting attachments within both the Component and Release controllers. Their work involved creating new DELETE endpoints and modifying existing services to handle the removal of attachments. Additionally, the user contributed to the testing suite by writing integration tests to ensure the successful deletion of attachments and to verify proper error handling. The changes involved modifications across multiple files, including controller and test class.
javasw360
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.