About
I started in 2018 on financial systems in Java, moved through distributed backends and marketplaces, and now build products end to end, with AI where it genuinely helps. I have stayed responsible for systems after release in every role, which changes how you build them.
My first years were finance software at Crossinx, where a wrong number is a real problem. That is where I learned to design the schema before writing the feature, to treat a migration as something that has to be reversible, and to test the paths nobody clicks. Java and Spring Boot were the tools; care with data was the lesson.
Amdaris moved me into distributed systems: Kafka, GraphQL, services owned by different teams, and deployments to Azure. At FeelIT I worked closer to the product itself, including the first language model features I put into production. Today I am the only developer on three products at once, which means the design, the code, the releases and the support are all mine.
Most of the hard problems in a product live in its data, not in its screens. I spend the early part of a project on the schema, the states a record can be in, and what happens when two people change the same thing at once. That is what makes later features cheap instead of painful.
I have been the only developer on three products at once: writing the features, running the builds, publishing the releases and answering the problems afterwards. That removes the gap where something counts as done but does not actually work, and it is why I care about release pipelines as much as about code.
A model call is a dependency with unpredictable latency, real cost and a habit of being confidently wrong. So I put timeouts, output validation, a token budget and a fallback in front of every integration, and I measure what it costs before it has to scale.
Documentation, tests and a deployment another engineer can repeat are not extras. They are the difference between a project you can continue without me and one you cannot, and you should be able to leave whenever you want.
Grouped by what it is for, because a list of names says nothing about how they get used.
Sole developer of three GlavUpDK products: the offline-first «Gosti» Android app for tracking guests and cars at protocol events, the «Avto» suite for the vehicle service center, and the native OTRS agent client for the internal helpdesk.
read more →Node.js/Express backend with OpenAI integrations for transcription and emotional detection; React frontend features.
read more →Microservices with Java/Spring Boot and Node.js: REST & GraphQL APIs, Kafka, SQL and MongoDB; Azure deployment on an internal project.
read more →Java/Spring Boot microservices on the backend; Android app with OpenCV document detection and Kotlin multiplatform library.
read more →The CV is available in English, Russian, Romanian and Spanish. Or skip it and tell me what you are trying to build.