Pablo Crivella is a Senior Software Engineer with 12 years of experience building and scaling reliable distributed systems, currently driving platform work at Creative Fabrica from Utrecht. He has strong backend expertise across Ruby, Go, Elixir and Node.js, shipping cloud-native services for file storage, uploads/downloads, search ETL, and vendor pricing systems. At WeTransfer he contributed to platform-level services and application security workflows for CSAM detection, and at bol.com and other firms he helped migrate legacy systems to resilient Go services on Kubernetes. Pablo is an active open-source contributor in the Ruby ecosystemโhis improvements to pundit and devise-jwt show a pragmatic emphasis on flexibility, authorization, and secure JWT revocation. He pairs hands-on implementation with mentoring and hiring experience, regularly improving code maintainability through DDD and testable architectures. Colleagues describe him as a pragmatic engineer who balances performance optimizations with long-term maintainability.
12 years of coding experience
11 years of employment as a software developer
Bachelor of Engineering - BE Systems Engineering, Bachelor of Engineering - BE Systems Engineering at Universidad Privada de Santa Cruz de la Sierra - UPSA
Minimal authorization through OO design and pure Ruby classes
Role in this project:
Back-end Developer
Contributions:7 commits, 2 PRs, 35 comments in 1 year 6 months
Contributions summary:Pablo primarily focused on enhancing the `pundit` library's functionality. They implemented features such as allowing override of the policy class and policy scope class in authorize and policy_scope methods, respectively. The user refactored the permitted_attributes method and improved documentation for the `pundit_params_for` method. These changes show a focus on improving the library's flexibility and usability for authorization in Ruby applications.
Contributions:9 commits, 1 PR, 20 comments in 1 day
Contributions summary:Pablo focused on enhancing the devise-jwt gem by implementing a whitelist-based JWT revocation strategy. They modified the database schema, created migrations, and updated the application's configuration for this new feature. Additionally, the user added and modified specs to ensure the whitelist revocation strategy functioned correctly. This work involved modifying core libraries and dependencies related to user authentication and JWT token management.
ruby-gemrailstokenauthenticationruby
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.