What have I done so far?

I have picked a few projects whose stories I would like to share. Don’t get me wrong: these are not the easiest or most trouble-free projects. Each has a complicated history, which is why I think it is worth telling.

• ProfMaster

  Website / CMS

  Roles: Development, Architecture, Customer support

  The brief was simple: build a website. But the real goal was a system that would not depend on its developers. I designed the structure, built a site-builder admin panel and trained the client to work independently. Years later the project is still relevant, thanks to an architecture designed with the future in mind.

  • Ruby/Rails
  • UI/UX
  • CMS
  • JavaScript

• Teratek

  E-commerce

  Roles: Crisis management, DevOps, Support

  The store was on the verge of closing: outages, errors, zero documentation. Together with the team we quickly ran an audit, fixed the critical bugs, set up CI/CD and began to win back customers’ trust. A month later sales had stabilised. This project became an excellent example of crisis management under pressure.

  • PHP
  • CI/CD
  • Docker
  • Observability

• Golden Digit

  CRM (Custom)

  Roles: Analysis, Architecture, Development

  While I was working as a freelancer, a colleague and I were asked: “Can you build a CRM?” Alexander and I started with in-depth analysis and even worked “in the field” to understand the processes. The architecture, the decisions and the UX grew essentially out of real tasks and conversations with prospective users. The result was not just a CRM but a tool that the company’s employees really wanted to use.

  • Freelance
  • Backend
  • UX
  • PHP / Go

• PriceHouse

  SaaS CRM

  Roles: Architecture, Team formation, CI/CD

  After the success of the previous project, the client wanted the product to work not only for their own company but also to earn money for them by being rented out to other companies. Together with a colleague, we designed a SaaS architecture with configurable, independent modules. It took a lot of refactoring and migration support. But in the end it became the first product in my practice with a scalable deployment model.

  • SaaS
  • Multi-Tenant
  • DevOps
  • Observability

• InTelCom / FiberSide

  Platform services

  Roles: Architecture, Backend, Network stack

  The company was launching Wi-Fi hotspots in public places, together with user authentication as required by Russian law, and everything had to work 24/7. Together with the team, I developed the key services, integrated with the billing system and introduced monitoring and logging. It was my first production experience with technologies that were new to me, and it accelerated my growth.

  • Networking
  • Audit
  • Microservices
  • Golang

• StartBase

  Frontend platform

  Roles: Tech lead, Architecture, Infrastructure

  After working at the company for a long time as a senior developer, I was finally promoted. As it happened, my manager could not find anyone to trust with the architecture of the frontend platform. A new task, an interesting challenge. I took time out to complete a number of professional development courses, and later, together with a designer, we built a UI kit and introduced Storybook. Then came painstaking work on CI/CD and the rules for PR review. At first I had to make many decisions personally, but then I scaled the approach across the team. As a result, feature development became twice as fast without a loss of quality.

  • React
  • Headless UI
  • CI/CD
  • UI Design

• DevHub Platform

  Internal portal

  Roles: Architecture, Backend, Frontend

  The company was in chaos: metrics, code and documentation were scattered. I proposed an architecture that brings everything together in a single portal. Integrations with Sentry, Git and Grafana, project cards, an internal API. This gave engineers transparency and saved them time on routine work.

  • Clean Architecture
  • Monitoring
  • Frontend
  • API

• Refactorium

  Technical audit

  Roles: Audit, Architecture, Development

  The project had stalled: bugs, a fear of touching the code, the business at a dead end. I ran an audit, rewrote the architectural core and introduced documentation. We held workshops with the team and cleared the technical debt. After two months the project came back to life, and the team felt in control and confident.

  • SOLID
  • KISS
  • Code Review
  • Golang

• Golang Tooling Contributions

  Open Source

  Roles: Contributor, Issue Hunter

  Working with various Go projects, I began sending pull requests to Golang, Echo, TiDB and other open-source projects. I wrote utilities, generators and wrappers. This gave me an understanding of how to design libraries and what value a community brings. I still follow their development.

  • Open Source
  • Golang
  • Community
  • CLI Tools

• NetBox Wrapper

  Network utilities

  Roles: Systems developer

  I had to integrate network information from NetBox and other sources. I wrote a Go wrapper with a convenient API, asynchronous processing and logging. My colleagues quickly adopted the project. Thanks to it, network tasks became reproducible and scalable.

  • Networking
  • Golang
  • Async
  • Integration

• TeamRadar

  Internal processes

  Roles: Team lead, Mentor, Processes

  As the team grew, developing people and processes became a priority. I introduced regular reviews, career tracks, documentation standards and CI. I held dozens of 1:1s and mentoring sessions. Thanks to this we reduced turnover and raised the team’s engagement.

  • Team Management
  • CI/CD
  • Docs-as-Code
  • Growth

• FinchPay

  Microservice platform

  Roles: Architect, Developer

  As part of a payment microservices platform, I created a service bootstrap architecture: graceful shutdown, middleware, observability and standard modules. It cut the time for new teams to get started threefold and made it possible to maintain code quality regardless of the project.

  • Platform Engineering
  • Golang
  • Clean Architecture

• DevPortal Platform

  Internal Developer Platform

  Roles: Architecture, Development, Integrations

  The company lacked a single source of truth about its services: information was scattered across wikis, dashboards and employees’ memory. I proposed and built an internal portal for engineers that brought together service search, documentation, test coverage, contracts and e2e tests. We introduced sign-in through Keycloak and built dashboards and project cards. The solution improved transparency, sped up onboarding and reduced the number of unnecessary questions in the engineering team.

  • Docs
  • Golang
  • VueJS
  • Keycloak
  • CI/CD