Timeline
- 01before 2021
Frontend developer in startups
First steps — at home and in small rented offices, in little teams of enthusiasts with startups of their own. I learned frontend on real tasks: markup, JavaScript, my first projects in React. And I learned the main thing: a product is made by a team, not by one developer.
- 02March 2021 — January 2022
Junior Frontend Developer
A first job at an IT company and a new stack: I learned Vue from scratch and still write in it. I took on projects of every kind, including on technologies I had never touched — PHP and Yii2, WordPress, Shopify. I learned from the experienced developers in the team: their reviews quickly turned tasks done by the book into tasks done on my own.
- 03February 2022 — February 2023
Middle Frontend Developer
From doing tasks to owning modules: I carried them whole, from the brief to the release, and agreed the decisions with the team and the backend. I often worked as an outstaffed developer — joining other teams, finding my way through heavy legacy and systems like 1C-Bitrix, where part of the server logic had to live on the frontend. I learned to find a way within any limits. On one project, still a middle developer, I led a frontend team of four.
- 04June — November 2024, March — November 2025
Senior Frontend Developer / Team Lead
Now I answered not for modules but for a whole product: I started it from scratch, later moved its architecture to FSD, and laid down the rules the team writes code by. I broke the work down, ran code review and did the mentoring of junior developers — that is how the shared standards formed that projects stand on for years.
- 05December 2025 — February 2026
Senior Frontend Developer / Team Lead
I led two teams at once: launching a new platform while still developing the earlier one. I answered for the architecture of the key processes, the deadlines and the quality of releases, and through code review and mentoring kept one level of code across both teams.
- 06March 2026 — present
Fullstack / DevOps Developer
Closed the loop: I take a product from the idea to production — the frontend, the backend and a CMS, Docker, CI/CD and deployments. In the team I answer for the technical decisions and the release cycle, from the first line of code to a running service.
Selected work
Things I've built
The projects are under NDA, so instead of screenshots there are paintings, each a nod to its product. Everything behind them is my real work. Click a sheet to learn more about the project.
Worldwide · hybrid / remote
About
I turn complex ideas into living interfaces
For more than 5 years I have been designing and launching high-load corporate and government platforms where a mistake is costly: electronic signatures, role-based access, multi-step forms, heavy dashboards and data visualisation. I also build online stores and landing pages, where load speed, motion and SEO decide the outcome. I take a product from the idea to production — with an architecture (DDD, FSD) that holds up as it grows — and as a Team Lead I answer not only for my own code but for deadlines, reviews and the team.
I am as much at home on a blank page as in someone else's code: I have launched products from scratch — from the architecture to the release — and as an outstaffed developer joined other teams, old codebases and systems boxed in on every side. Whatever the conditions, I found a way: not a single contract ended early, I saw every project through to the end and left with the client's thanks.
I started before AI assistants existed and learned to design clean, fast and reliable solutions with my own hands. Today AI is part of every stage of my work, and I move many times faster. But it does not think for me — it helps: the architecture, the quality of the code and every decision stay under my control. AI brings the speed; the quality is on me.
Skills
Where I am strong
- Vue / NuxtMy main stack since 2021: from a fast SSR site to an enterprise system of dozens of modules. I know not just the API but where the framework saves months and where it starts to get in the way.
- TypeScriptStrict types from the API to the button: they are generated from OpenAPI, so a broken contract is caught at build time, not by a user.
- Complex interfaces and dataDashboards, charts and large tables that do not lag; multi-step forms where not a single field gets lost.
- Architecture and teamI lay down an architecture that grows without a rewrite from scratch, and I lead the team: breaking work down, reviews, releases on schedule.
- React / Next.jsMy second stack, also in production: fast landing pages with motion, SEO and a headless CMS.
Filled: my core stack, what I work with all the time Outlined: used in projects when needed
Frameworks
State and data
Forms and editors
Markup, styles and UI
Charts
Motion and sliders
Analytics
Performance and SEO
Contact
Write me a letter
