About
Full-stack engineer and tech lead who loves platform work. I build software-delivery systems — and, along the way, study how those systems change the work of teams and markets.
Full command of the stack
Equally confident on backend (Node.js, Express, PostgreSQL) and frontend (React, Vue, TypeScript). I can design a service, take it to production and explain the decisions to the team.
Platform thinking
I design not single features but tools other teams rely on: feature-flag platforms, internal portals, CI/CD. I think about scalability, maintainability and a clean separation of concerns.
Technical leadership
I lead a direction and a team: set standards, run assessments and code review, mentor developers. I can explain complex decisions so people follow them, not just accept them.
Outcome-driven
I measure work by effect, not lines of code: −25% incidents, −30% release time, HSE portal load cut from 30 seconds to 1. I finish what I start — a habit from postgraduate years spent working and studying with no academic leave.
Legacy and migrations
Rewrote projects from JavaScript/Perl to TypeScript, bringing typing, shared standards and containerisation into live products — carefully, without pausing development.
My path into development began at Moscow State University — unexpectedly, out of research. I was processing text for grant applications, tried to automate the routine with code, and it grew into a profession. That is when I realised I wanted not just to use technology but to build it.
From academia I carried something more valuable than any framework: setting my own goals, decomposing large problems, discipline under uncertainty and the habit of finishing. For several years I combined work and study without a single academic leave.
Then came commercial development: a product team at Potok.io, enterprise scale on the HSE portal (40,000+ users) and, finally, fintech. At IT_One I went deep on feature toggles and developed the Unleash platform; at Alfa-Bank I grew from engineer to tech lead of the direction, owning feature-management practice at bank scale.
Today I am drawn to hard engineering problems at the intersection of platforms, release engineering and reliability — where good infrastructure directly affects the speed and calm of whole teams. I am looking for an environment that values both depth and ownership of outcomes.
How software-delivery tooling — feature flags, gradual rollouts, A/B — changes the way teams make decisions and how power over a product is distributed.
Beyond engineering I run applied research into the digital economy and write at the intersection of technology and the organisation of work. For me this is not abstract theory but a way to design more deliberately: understanding how infrastructure shapes team behaviour makes it easier to build tools people actually want to use.