After discussions with the business stakeholders, I developed:

• Technical requirements for the project, user roles, key usage scenarios
• Formulated requirements for updating the proprietary API
• Application tech draft, including authentication, routing, error handling, overall styling

Web application for tracking inventory and sales in a mobile sales point.

Within the project, I have developed:

• Technical requirements and design mockups
• New API methods for CRM
• SPA application with a small backend on Vue 3 (Nuxt) interacting with the proprietary CRM API and SkuVault API (inventory system)
• Adaptive design using Tailwind CSS

I developed and launched a modern e-commerce website for the company Metro OTC.

The project involved creating a customizable core that allows for the creation of stores for different brands under exclusive contracts with insurance companies.

To achieve this, I utilized the new Layers technology that debuted in Nuxt 3.

Readonly proxy for the SkuVault production server. If you send it any get request, it will redirect that request to the actual API server and return the response.

Any other request that involves the internal state of the SkuVault server will not be executed. Instead, the proxy sends the data it received to a Slack channel.

I developed a browser extension that semi-automates the payment process in an insurance affiliate system that did not have an API. The implementation of the project resulted in speeding up transaction processing and minimizing human error.

The extension works by automatically filling out the payment form on the insurance company's website using data from the CRM:

• Customer information
• Insurance card details
• Order details

I played a key role in the development and implementation of a new CRM system using Vue.js and Quasar, which completely replaced the previous outdated system. I independently developed around 70% of the functionality, including:

• The framework and overall application architecture
• The authentication system with automatic token refresh
• Key components and pages: task system, client sections, orders, returns, and some reports
• On the Symfony side: API, services, controllers, entities, and migrations, Swagger documentation was implemented