They have a thinking problem dressed as one. After 10 years in fintech and insurtech, I learned to ask the right question first.
I've spent 10 years inside financial and insurance systems. Payment card middleware, policy engines, financial integrations. That background shapes how I think about every technical decision.
Today I manage interdisciplinary teams, analyze problems, and make technical decisions. I also help teams work with AI well, not by chasing every trend, but by finding where the real value is.
10 years building systems where reliability isn't optional. Payment processing, policy engines, financial integrations, regulated environments.
Java, Kotlin and Groovy as primary languages. Spring Framework, Hibernate, Gradle. Backend architecture and microservices.
Leading interdisciplinary teams, designing systems, working directly with corporate clients from requirements to delivery. Technical decisions grounded in business context, not just engineering preference.
I work with AI hands-on. LLM agents, MCP servers, workflow automation, AI-assisted development. I know what delivers real value and what sounds good in a presentation.
I value a good question more than a ready recipe. After a long discussion, the best solution often turns out to be the simplest one. Sometimes that means no code at all.
Over 10 years in IT and I still feel more like an enthusiast than an expert. That's what drives me to keep looking for better solutions and to question what others take for granted.
I design architecture and lead teams, and I also work directly with clients from requirements to delivery. I speak both languages and know when to use which.
Years of work on a business rules engine used across insurance and financial systems. Speed wasn't a nice-to-have. When rules run at high volume, every millisecond compounds. Most of the interesting decisions happened at the architecture level, long before any code was written.
Built the layer connecting an internal platform with external banking integrations. RESTful and SOAP APIs, PCI-DSS constraints, high availability requirements. The kind of system where nothing can quietly fail.
Ran the technical side of an insurance project end to end. That meant working directly with the client from the first requirements conversation through to go-live, and keeping the team focused on the right things throughout. Scope held, timeline held.
I start every engagement with a conversation. No pitch. Just an honest look at your situation.