Peter Scholz is a freelance software engineer with 14 years of experience specializing in Ruby, APIs, and OpenAPI/Swagger tooling. Based in Leipzig/Lausitz, Germany, he combines hands‑on back-end development with open-source maintenance—contributing to projects like grape-entity and grape-swagger to improve API documentation, versioning, and response schemas. He is an OAPI enthusiast and gem maintainer who also enhanced NLP tooling by adding multilingual stop-word support and reducing dependencies in the treat library. Peter’s work shows attention to code quality and compatibility, from RuboCop fixes and dependency bumps to supporting multiple Ruby versions. Comfortable both shipping practical fixes and refactoring core logic, he excels at making libraries more robust and easier to integrate. An understated strength is his knack for improving developer experience in mature Ruby ecosystems while freelancing across varied projects.
Add OAPI/swagger v2.0 compliant documentation to your grape API
Role in this project:
Back-end Developer
Contributions:42 reviews, 257 commits, 440 PRs in 7 years
Contributions summary:Peter primarily contributed to upgrading the grape-swagger library, specifically focusing on supporting OpenAPI (Swagger 2.0) specifications. Their work included refactoring code, adding schemas to responses, handling nested parameters, documenting file responses, and improving how the library handles versions. These changes involved modifications to both the core library files, spec files and associated entities to ensure the generation of accurate and complete API documentation, significantly improving the library's ability to generate robust and accurate API documentation for Grape APIs.
An API focused facade that sits on top of an object model.
Role in this project:
Back-end Developer
Contributions:12 reviews, 31 commits, 107 PRs in 5 years 9 months
Contributions summary:Peter primarily contributed to the development and maintenance of the `grape-entity` library, which is focused on building APIs in Ruby. Their work involved version bumping, updating dependencies, and adding changelog entries. Furthermore, the user made changes to the core logic by adding support for Ruby versions, refactoring and improving the code structure, and fixing rubocop offenses. This user demonstrates proficiency in managing and maintaining a Ruby library focused on API development.
apirubygemsentityrubyfacade
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.