Jakub Pilimon
Software Engineer at Pivotal Software Inc
Warsaw, Masovian Voivodeship, Poland
Summary
🤩
RockstarJakub Pilimon is a seasoned software engineer with 11 years of hands-on experience focused on backend systems and Domain-Driven Design, based in Warsaw, Poland. He contributes actively to notable DDD example projects using the Spring stack, implementing REST endpoints, domain logic, and integration tests that bridge business rules with persistence and prediction features. Jakub has demonstrated strengths in refactoring core domain models, event handling, and adapting architectures to evolving requirements—skills reflected in work on circulation and demand-forecasting domains. He combines pragmatic engineering with attention to testability and integration, often working on shortage prediction and demand-level adjustments that show an eye for operational impact. Colleagues can expect a developer who prefers shaping the heart of applications—domain logic and backend integrations—rather than surface UI work.
11 years of coding experience
Polish, English, Japanese
Github Skills (21)
domain-driven-design10
api-rest10
cqrs10
api-design10
restful-api10
testing10
java10
javas10
spock10
spring-boot10
rest-api10
ddd10
integration-testing10
event-sourcing9
event-emitter9
Programming languages (7)
Github contributions (5)
ddd-by-examples/library
Dec 2018 - May 2022
A comprehensive Domain-Driven Design example with problem space strategic analysis and various tactical patterns.
Role in this project:
Back-end Developer
Back-end DeveloperContributions:126 commits, 31 PRs, 33 pushes in 3 years 5 months
Contributions summary:Jakub's primary focus was on implementing and refining domain logic, specifically within the context of a Domain-Driven Design (DDD) project, as evidenced by their work on test fixtures, and core domain classes. They refactored existing code to align with DDD principles by renaming regular resources to circulating and adding patron id. This indicates a strong understanding of the project's architecture and the ability to modify core functionality and adapt to evolving requirements. The changes demonstrate a focus on core domain functionality, including placing books on hold, collecting, and returning books, as well as the domain event handling.
archunitcqrscrudpatternsdomain-driven
ddd-by-examples/factory
Mar 2018 - Jul 2018
The missing, complete example of Domain-Driven Design enterprise application backed by Spring stack
Role in this project:Back-end Developer
Back-end DeveloperContributions:18 commits, 12 PRs, 9 pushes in 3 months
Contributions summary:Jakub contributed to the development of a domain-driven design enterprise application using the Spring stack. Their work involved implementing REST endpoints for pushing documents, creating and modifying entities for demand forecasting, and writing integration tests. The commits show the user's focus on the back-end logic, including interactions with a database and adjustments to demand levels. They also worked on shortage prediction integrations.
domain-modelcqrsmissingcrudbacked
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.