- Development of new features and maintenance of existing applications using Vue 3 + TypeScript + Pinia + Corporate UI library (utilizes Tailwind and DaisyUI under the hood).- Development of components for the corporate UI library, the library is used in all applications across the platform.- Collaboration with a QA team and providing the guidance on how the code works & the data flows for a better understanding.- Collaboration with a design team in terms of development of components for the corporate UI library & new design concepts for the upcoming features.- Built from the ground an admin-like app (as part of other apps in microfrontend project) for setting up different client configurations for marketing campaigns. I developed the UI part and cloud function handlers that provide the data to the UI.- As part of a team migrated an existing Vue application (that wasn't a part of microfrontend project) to microfrontend project. Application was migrated to use the following tech stack: Vue 3 + Pinia + TypeScript + Corporate UI library. My part was the setting up the global store management and its architecture, refactoring of existing components, refactoring of a vue-router config and adding missing type declarations to provide the type-safe code.

- Successfully mentored 2 students during the 'HTML & CSS. Professional Website Coding' course.- Ran mentoring sessions with students to discuss their questions and complex concepts.- Did code reviews, provided a feedback.

- The main goal of my team was to develop a new version of web app using a new tech stack: Nuxt + TypeScript + Tailwind. - I have built a lot of components for the corporate component library, reusable composables and util functions.- At some point we found ourselves not possible to leverage all advantages of TypeScript because of issues in Vuex state manager. I offered and implemented the migration of the whole project from Vuex to Pinia. As a result we got the full TypeScript support and more convenient functional way of using / building stores.- Implemented a complex validation for the checkout form, that also includes api requests for checking seats availability and coupons valitidy.- Being a big fan of clean and accessible mark up I managed to bring accessibility of our app to green zone in Lighthouse.

In this role I mostly worked on these projects:1) Web app with multiple landing pages with coupons, offers and discounts (Nuxt 2 + TypeScript + Scss + Buefy + Vuex).2) Admin panel for creating add campaigns, retailers, coupons for the app from #1 (Vue 2 + TypeScript + Vuex).3) Widget web application that was embedded via iframe on clients's web sites (Nuxt 2 + TypeScript + Scss + Buefy).4) Web app for choosing the best loan deals, credit cards, debit cards (JavaScript + Pug).Web app with multiple landing pages with coupons, offers and discounts: - Given that we had multiple landing pages and their number was growing, it was necessary to scale fast and reuse UI components as much as possible. So I implemented a lot of components for the corporate UI library and tested them with Vue Test Utils. All components were built with 'mobile-first' approach in mind.- Implemented different themes for the app (Halloween, Christmas sale, St.Valentine's Day, etc). Theming was based on css variables and was applied specifically per landing page. Admin panel for creating add campaigns, retailers, coupons:- Initially the app was not used by client managers because the dev team was out of time to work on the app. Once I joined the development, the admin app became my №1 priority. When I picked the app it was built using domain driven design pattern. I reworked each domain according to new requirements from the product team and the app became fully running and started being used by client managers. Widget web application: - Migrated the app from Vue 2 + JavaScript + Buefy + Bulma tech stack to Nuxt 2 + TypeScript + Buefy tech stack. Migration to Nuxt allowed to enable SSR and boost the app from SEO perspective. - I maintained the widget app during its lifecycle, added themes and new features.Web app for choosing the best loan deals, credit cards, debit cards:- Created PWA from the app.- Covered PUG templates with tests.

- Implemented around 100 end-to-end tests in order to maintain the 90% test coverage (there were always new test scenarios being developed by the other QA team in parallel, so my team aimed to have at least 90% of them automated).- Moved the existing code base from JavaScript's ES5 standard to the newest (back then) ES6. That not only let us use new language's features, but also helped to make the code more declarative and more friendly to new colleagues who were not familiar with the ES5 standard.- Given that my team got the newest version of TestComplete, I managed to set up an integration between TestComplete and TestRail without a middleware Java server.- Set up a Gitlab pipeline to run automated tests according to a schedule. Automated tests ran on virtual machines with TestExecute software as a test runner.- As a lead QA engineer of the product, I onboarded and mentored three automation engineers from the outsource organization. During the time of their contract (3 months) I did code reviews for their automated tests in order to keep the codebase maintainable and scalable in future.

- We had a kind of a unique web application, it was built with Microsoft Silverlight platform. Our QA team contained of me and one Senior QA Engineer, we spent a lot of time to find the best tool that can recognize Silverlight's objects on the page. Me myself tried TestComplete, Ranorex Studio and UiPath. And the best job was done by TestComplete, so TestComplete was picked.- Our automation testing framework was built on TestComplete + JavaScript (ES5) + Page Object pattern. Most of the time I was writing automated tests (implemented around 100 automated tests) to ensure the best test coverage (the team aimed for 80% coverage at that time), also I created a lot of classes-pages to use in future tests.- Given that the testing was the end-to-end one, I also implemented a lot of sql scripts for inserting and removing test data per each automated test.- In the company the TestRail software was used for storing test scenarios and test protocols, so we needed a way to pass test results from TestComplete to TestRail. Given that I had some background in Java development, I set up a server, that passes test results from TestComplete directly to TestRail.