Piotr Rżysko
Software Engineer at Starburst
Warsaw, Masovian Voivodeship, Poland
Summary
🤩
Rockstar🎓
Top SchoolPiotr Rżysko is a software engineer with 10+ years of experience specializing in the JVM ecosystem, distributed systems, and performance engineering, currently building at Starburst. He has a strong track record at Allegro delivering measurable efficiency gains—reducing CPU use by 40% in a Kafka broker, slashing ML model rollout time from days to hours, and stabilizing Java services at 200k+ RPS with p99 improvements. Piotr contributes to prominent open-source data projects (CrateDB, Trino, QuestDB, QuestDB/Trino/Crate-adjacent work) where he’s implemented core SQL/database features, interval arithmetic, and EXPLAIN VERBOSE support, reflecting deep expertise in query engines and time-series systems. Comfortable across production code, platform engineering and performance tuning, he also brings practical deployment experience with Kubernetes and cross-datacenter replication. A Warsaw University of Technology MSc graduate, he combines academic grounding with hands-on impact in both enterprise and open-source data infrastructure.
10 years of coding experience
10 years of employment as a software developer
Master of Science (MSc) Computer Science, Master of Science (MSc) Computer Science at Warsaw University of Technology
Polish, English
Github Skills (40)
timeseries-database10
monitoring10
api-rest10
query-builder10
messaging10
catalog10
back-end-development10
api-design10
restful-api10
cratedb10
testing10
databases10
query-optimization10
kafka10
time-series10
Programming languages (4)
Github contributions (5)
allegro/hermes
Jan 2019 - Dec 2022
Fast and reliable message broker built on top of Kafka.
Role in this project:
Back-end Developer
Back-end DeveloperContributions:1 release, 354 reviews, 83 commits in 3 years 11 months
Contributions summary:Piotr primarily focused on updating and improving the Hermes message broker. They updated the Kafka version in the Vagrant provisioning, indicating familiarity with the deployment environment. Key contributions include adding endpoints for monitoring, fixing metrics for batch and filtered subscriptions, and handling deprecated owner sources, which reflects work across different aspects of the project, including monitoring, and management. Additionally, they added the functionality to attach HTTP headers with the subscription identity, showing their involvement in improving subscription configurations.
brokermessage-queuehermesmessage-brokerreliable
trinodb/trino
Jul 2024 - Mar 2025
Official repository of Trino, the distributed SQL query engine for big data, formerly known as PrestoSQL (https://trino.io)
Role in this project:Back-end Developer
Back-end DeveloperContributions:37 reviews, 19 PRs, 58 comments in 8 months
Contributions summary:Piotr primarily contributed to the Trino query engine's core functionality. Their work involved making catalog management configurable within the testing server and refactoring related test code. They also updated the `CatalogVersion` contract and fixed issues related to catalog creation failures. Additional contributions focused on resource group management, including changes to handle disabled groups and prevent configuration update losses within the resource group manager.
prestodbdbmsindexingjdbcbigdata
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.