Pavel Kleisner
Backend, integration and release work for systems where production mistakes are expensive.
I mainly work with Kotlin, Java, Spring and PostgreSQL. In recent years my focus has been TSM/CETIN production flow: B2B behavior, data compatibility, incident analysis, new version rollout and the places where business rules meet runtime reality.
I am not a “full-stack generalist for everything”. I am a backend-heavy programmer who can still read the frontend, database and operational logs when the real cause is spread across the system.
Where I fit best
The value is usually not another abstraction layer. It is a change that survives real data, integrations, support and the next release.
- IntegrationsB2B APIs, process flows, message behavior, retries, logs and failure modes that only become visible after deployment.
- ReleasesRolling new versions into real environments while watching compatibility, old data and operational risk.
- ArchitectureSmall safe changes, clearly named rules and service boundaries. No ceremony around patterns.
- DebuggingIncidents through logs, metrics, databases and domain context. Not random patches around symptoms.
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.
ZIS
MNCP
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.