Pavel Kleisner
Backend, integrations and releases — the unglamorous part where systems meet real data and have to stay up.
I work on Kotlin/Java/Spring services and PostgreSQL, mostly around TSM/CETIN production flow: B2B behaviour, data compatibility, incident analysis and rolling out new platform versions. I'd rather fix production than be right about it.
Where I fit best
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 the
messageId would be a UUID. One partner started failing immediately.
Their system was quietly parsing the ticket ID out of the old
ticketId_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
Most of my professional work is internal or client-owned, so I describe responsibility and production context rather than exposing code.
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.