Ozon – Frontend Engineer February 2022 – Present
● I came up with and implemented an approach that makes it easy to adapt product cards to a variety of designs without the use of additional flags and props. This adapted the code to the most unexpected requirements changes.
● The specifics of the project is that it has a lot of boilerplate code when creating new features. Implemented boilerplate code generation, which made it possible to significantly speed up the addition of new features. This system is currently being used in five other projects.
● I refactored the internal support chat solution, separating the presentation logic, business logic and api interaction logic, and put all the code in a separate package. Thereby simplifying the chat integration for other projects.


ZION Development – Frontend Engineer November 2020 – Feburary 2022
● I came up with a way to separate the presentation, presentation logic and business logic into isolated, testable parts of the code. This made it easier to add new features and run ab tests. And also made it very easy to switch to a new design system.
● I implemented the PageBlock component, which unified the design and accelerated the development of landing pages for a large number of devices. Later this component was used throughout the application.
● In the project, it was often necessary to replace the state of the application in several unrelated places directly in order to simulate the transaction. I have proposed and implemented a system that allows you to turn on mocks and api meshes without changing the program code. This made it possible to quickly make small and large edits in the project, and also accelerated the acquaintance with the product of new team members.
● I was responsible for the transition to the new support chat system. The challenge was to save all 15,000 call histories and add them to the history of the new system, given that the data formats were different.
● Developed a Google Chrome extension that allowed QA to easily find web application components covered by ui tests