We build various applications in fintech. The one I'm proud of most is "Базис.Документы" (doc.basis.center). It is a HITL software for semi-automated document recognition.My personal achievements in historical order:- acted as an architect, devops engineer, developer at the same time to build the first version from zero to production- hired key developers- initiated the AI department by hiring its head and defining its strategy- created a DSL for faster implementation of complex document flows- moved from bare docker to kubernetes- initiated the infrastracture department by hiring its head- in cooperation with the PM built a BI system (based on metabase) which allowed to analyze and monitor the key metrics of the business and helped to define vectors of improvement- realized we needed to improve our processes and hired an agile expert - initiated the Information Security department by hiring its head- initiated the introduction of MLops practices, found an expert and defined the strategy- did a research of SOTA LLM / vLLM models that can bring the business to the new level, successfully built a proof of concept model in the related domainApart from the key things mentioned above, my daily responsibilities include:- controlling the budget for infrastructure and software- communicating with the clients at the pre-sale and integration stages- making sure the technical departments achieve their goals- making sure the engineers are happy with what they work on and how- helping my teammates to make reasonable technical decisions- solving unusual problems- sometimes coding

The company consisted of many teams, building many products related to blockchain or financial technologies. It was like a startup accelerator.My responsibilities included:- defining the company-level technology stack- conducting interviews for senior and lead positions- organising CI/CD and other DevOps practices- consulting engineers from the teams when it was neededAlso, I contributed to one of the products personally. It was a digital office for mortgage clients of banks, that allowed applying for and getting mortgage loan online. My contribution included:- making decisions on the architecture- coding the key parts of the application- when we decided to sell the product, I took part actively in the integration and adaptation process, solving all the technical problems so that the deal was successful.

At this company I led a team of 5 developers. We successfully built an API providing real estate data for the classified advertisements website youla.ru.The personal challenges for me were:- entering an existing team as a leader- working with a completely remote team- learning a new technology stackI was able to study the code and the infrastructure of the high-loaded web-site youla.ru, learning some tricks from it.stack:PHP, Yii2, mysql, rabbitmq, docker, ansible

I was invited by my ex-boss to join a new company as a CTO. Although I hadn't had an according experience, it seemed like a challenge for me, which I accepted with pleasure.The task was to build a web application for making mortgage deals online in the US. We also wanted to take advantage of the blockchain technology to grab more attention from investors. Blockchain was hyping back then.I decided to choose a stack that was new for me. There were a few reasons for that decision:-- I was sure ASP.NET for Windows had no future (and it didn't, indeed)-- .NET Core (which is cross-platform) hadn't been ready for production yet-- Personally I got tired of Windows, Visual Studio and other products of MicrosoftSo I took a risk and switched to Java stack. But java language seemed too verbose and noisy, so I opted for Kotlin. Although the community had had very little experience using Kotlin in server applications, it had proved itself good at Android platform. And I expected it to grow as a server-side language as well.For the framework I chose Spring Boot, which had already been the standard for server applications in java.For the frontend part I chose React, which I also had to learn on fly. The framework seemed promising.At BuyTheWhale I got my first experience of hiring people completely by myself. I found a frontend developer and a QA engineer.Working on the project, I learned a lot about blockchains in general and Ethereum specifically. I run a private Ethereum blockchain, wrote smart contracts, worked on tuning its performance.We successfully built a working version of the app in time. Unfortunately, the priorities of our management changed, so they decided to put the product on hold.stack:Kotlin, Spring Boot, postgres, redis, rabbitmq, docker, ethereum-parity, solidity, react, redux, webpack, go, ansible

Regardless the title, the things I was responsible for included:- making decisions on the architecture (in general and feature-specific as well). We started with a classical 3-layered architecture and later evolved to CQRS- making decisions on infrastructure, achieving the desired fault tolerance metrics- hiring new developers (screening CVs, conducting interviews, onboarding)- building and maintaining the production environment and the QA environments- building and maintaining the CI process- conducting code review- implementing new features A big part of work was related to performance optimisation, fault tolerance and improving scalability. At least a year I devoted to the following tasks:- writing load tests using jMeter- profiling and optimizing SQL queries (rewriting, adding and removing indices, utilizing materialized views)- tweaking the ASP.NET MVC framework to make it run much faster than out-of-the-box- introducing Elasticsearch to switch the searching load from SQL Server- implementing caching of many kinds: caching results of sql queries, donut and donut-hole caching of rendered pages. I made caching part of the framework so that it would require very little code to use it in new features.- making sure the app and all its dependencies would scale horizontally - setting up monitoring (new relic), reacting on accidentsThe nightmare part of it was setting up mirroring for SQL server. It need Active Directory to run, so I had to setup that too. That experience contributed to my decision to switch away from Windows-related stack later.stack:C#, ASP.NET MVC, js, jQuery, Websockets, SQL Server, Elasticsearch, Couchbase, rabbitmq, Windows Server

I developed, deployed and maintained various web applications (mostly social networks) for our clients. When I joined the company, all its projects had been using an outdated technology: ASP.NET WebForms. I took the initiative and introduced the ASP.NET MVC framework. First I learned it myself and then made it the new standard in the company.After succeeding in maintenance and enhancement of the existing apps, I was allowed to start a new one from scratch (workle.ru). I was responsible for choosing the stack, the architecture, the infrastructure, organising the CI process. When other developers joined the project, I organised Code Review as well. I configured the servers myself, wrote scripts for deployment. In October 2011 I was transferred from Ingenious Systems to Workle along with the whole engineering team of workle.ru.stack:C#, ASP.NET WebForms, ASP.NET MVC, js, jQuery, SQL Server, Windows Server, IIS, debian, nginx