Diego Krupitza is a Quantitative Developer at G-Research with eight years of engineering experience spanning high-performance data systems, distributed AI tooling, and production trading infrastructure. He holds a BSc and MSc in Computer Science from TU Vienna with multiple merit scholarships and has published academic research related to his work. Proficient in Python and experienced with JVM languages, C# and modern data formats (Parquet/Arrow), he has driven measurable performance gains—e.g., accelerating data delivery to live trading by 25% during an internship. An active open-source contributor, he’s improved core Spring Data projects by adding features like specification-based existence checks and pessimistic locking support, demonstrating attention to maintainability and SQL generation across dialects. Based in London, he combines research rigour with hands-on systems engineering and prefers written contact over unsolicited calls or texts.
Simplifies the development of creating a JPA-based data access layer.
Role in this project:
Backend Developer
Contributions:13 reviews, 34 commits, 15 PRs in 11 months
Contributions summary:Diego primarily contributed to the Spring Data JPA project by addressing bug fixes, code improvements, and implementing new features. Their work involved fixing typos, removing deprecated function calls, and removing unnecessary code, contributing to code readability and maintainability. They also added functionality to the JpaSpecificationExecutor interface, enabling existence checks based on specifications, thus enhancing the flexibility of data access. Additionally, the user's work included incorporating a JSqlParser for native queries and improving the count query generation.
Spring Data Relational. Home of Spring Data JDBC and Spring Data R2DBC.
Role in this project:
Back-end Developer
Contributions:12 commits, 5 PRs, 21 comments in 1 month
Contributions summary:Diego contributed significantly to the Spring Data Relational project by implementing and refining features related to derived queries and pessimistic locking. Their work included introducing the `@Lock` annotation for methods to manage locking modes and generating the appropriate SQL for different database dialects. The user also addressed code readability by replacing `StringBuilder` with simple string concatenation and removing unnecessary `toString()` calls. Furthermore, they added support for Query by Example functionalities.
spring-bootspring-datarelationaldddr2dbc
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.