Pavel Kleisner
I build and steady the backend systems that keep real businesses moving.
Nine years across Kotlin, Java, Spring and PostgreSQL — from full-stack delivery to leading production rollouts, integrations and incident analysis. I like precise changes, honest communication and software that still makes sense two years later. I'd rather fix production than be right about it.

What I bring to the table
Usually the value isn't another abstraction layer. It's a change that survives real data, integrations, support and the next release.
The UUID that wasn't a UUID
When we rolled out the first platform version, the integration spec said themessageId would be a UUID. One partner started failing immediately. Their system was quietly parsing the ticket ID out of the oldticketId_timestamp format — even though the ticket ID sat right there in the message body.
The clean fix was on their side, but in a corporate setting that change would take months. So I adapted our side back to the old shape and kept production running. Sometimes the right call isn't the pure one — it's the one that doesn't break someone else at 2 a.m.
Core stack
Experience snapshot
A quick map of the systems I've worked on. The longer version — including what I actually owned on each — lives on the projects page.
MNCP
ZIS
Interested in collaboration?
If you need a senior engineer for backend systems, integrations, production releases or long-term product development, email is the fastest channel.