The project enables collective receipt of SMS messages to a US number under the company's name, rather than a specific individual.

The company used several services that required 2FA via SMS, and it was impossible to share such an account among multiple employees located in different time zones around the world.

Thanks to my implementation, the team had a unified number to receive SMS messages from shared accounts, and everyone (who needed it) could see them in Slack.

The number was provided by the Plivo service, and there was no direct integration into Slack, hence the need for this micro-project.

To improve the user experience for visitors and content managers, I proposed and developed a file uploader and CDN for the OTC project, allowing users to upload product images to an S3 server and receive a link to the file in the cloud.

The CDN provides fast access to files, as well as caching for improved performance.

Prior to the implementation of the project, product image files were loaded from Mediafire, leading to slow image loading times and upload failures.

A mini-project that implements the distribution of an up-to-date product catalog in PDF format.

The main purpose of the project is to provide the ability to always receive an up-to-date PDF catalog via a direct link. It also allows for publishing a new catalog using the same link (which may be widely distributed, including offline in print materials, and cannot afford to change with each new version of the catalog).

The project was implemented on AWS using Serverless technologies.

For the convenience of debugging and testing functions related to sending SMS messages, I took the initiative to create a script and Slack application.

While working on the local project and on the test server, instead of real SMS sending, the messages are sent to a Slack channel along with the recipient's number.

It became much easier to test everything related to SMS, including logging in with a code from an SMS, notifications, etc.

Before developing this tool for debugging messages and logging in with a code, it was necessary to check the logs, which took a lot of time and was inconvenient.

I have developed a specialized web service for processing cryptocurrency payments. The service allows for integrating the acceptance of such payments into projects that do not have their own infrastructure for working with cryptocurrencies.

This is achieved by issuing "invoices" for subsequent payment, tracking payment statuses, and webhook notifications when a payment for an invoice is detected.

The project started as a utility for merging contacts from different sources into one file. During development, the client decided to expand the functionality and turn the utility into a full-fledged web service for storing and managing information about donors and donations for NGOs.