I help fintech companies turn complex requirements into systems that actually ship — writing specs developers can build from, managing API integrations that hold up in production, and turning raw data into decisions.
End-to-end ownership of API ecosystems — versioning strategy, partner onboarding, breaking change analysis, and phased rollouts.
Implementation-ready specs with user stories, acceptance criteria, exact API field mappings, and compliance requirements.
Systematic comparison of what exists vs. what's needed — across system versions, regulatory requirements, or competing vendors.
Managing integrations with multiple external parties simultaneously — setting expectations, tracking commitments, identifying delivery risks.
Custom pipelines from raw API responses to structured reports and dashboards — including automated reconciliation.
Hands-on configuration of Kafka, Keycloak OAuth2, and API gateways — bridging infrastructure teams and business requirements.
Long-term collaborations, consulting engagements, and projects where a vague brief needs to become a spec, a working integration, or a decision someone can act on.
Yes — I'm based between Prague and Dubai and work fully remotely with clients across Europe and the Middle East.
Absolutely. I often work directly with product owners or founders to translate business needs into specs that can then be handed to any development team.
Both. I write the specs and, where useful, build the tooling in Python — data pipelines, automation scripts, API testing tools. I stop at production engineering.
Practical articles on business analysis, AI workflows, and what it actually takes to deliver complex integrations.
Great software requires crystal-clear specifications. A complete guide to using Python to level up your API documentation from scratch.
Have you ever tried to follow instructions in a language you don't understand? That's what developers face with a weak API spec. Here's how to fix it.