Aleksandr E.

Aleksandr E.

Node.js | Vue.js developer

Gomel ,

Experience: 12 Years

Aleksandr

Gomel ,

Node.js | Vue.js developer

60000 USD / Year

  • Immediate: Available

12 Years

Now you can Instantly Chat with Aleksandr!

About Me

I’m a lead developer of the professional web developer's team specializing in the back-end. But we are not ordinary developers. We have extensive experience in developing the back-end for mobile applications, simple and complex structured we...

Show More

Portfolio Projects

The public API for customer’s web-sites

Company

The public API for customer’s web-sites

Role

Full-Stack Developer

Description

What had to be done:

It was necessary to integrate three customer’s web-sites (on CMS) into his CRM-system.

How did I solve this problem:

I developed modular check-outs (a check-out page with SMS-authorization and thankyou-page) with user’s personal accounts for these web-sites and connected them with the client’s CRM. All this was done on NuxtJS.

Thus, the web-sites were still working on the CMS, but you could no longer check-out there, they acted as a shop window only. Moreover, user’s check-out and information reception through personal accounts became faster and safer than before. Also, all the information about a new order from the web-site instantly got into CRM-system and was immediately processed by managers.

What the client received as a result:

The client received not only a new secure way to check-out on the web-site, where the order immediately fells into CRM-system, but, due to the fact, that the solution has a modular structure, the customer is able to quickly integrate any of his other web-sites into CRM-system, that reduced his expenses for IT in future.

Show More Show Less

Tools

Git

The mobile application API for a healthy food delivery online store

Company

The mobile application API for a healthy food delivery online store

Role

Backend Developer

Description

I developed the API by which the application receives the catalog, news, customer data, orders, etc. I also created a large number of public routes for receiving data from the back-end and documented everything in Swagger.

The work has been done in cooperation together with the developer of the mobile application. As a result, the Customer received a ready-made API for the successful operation of a healthy food delivery online-store mobile application.

Show More Show Less

Tools

Git

Media

The public API for exchanging orders with an external trading platform

Company

The public API for exchanging orders with an external trading platform

Role

Software Architect

Description

What had to be done:

The customer wanted to sell his goods at the “Delivery club” platform, which is a marketplace for restaurants.

How did I solve this problem:

I created the public routes for the delivery of the customer’s catalog of goods by the “Delivery club” platform, routes for creating a check-out from the "Delivery club" store into the client’s CRM, routes for "Delivery club" order's statuses exchanging.

In the process, I interacted a lot with the technical support of the “Delivery club” platform, studied their documentation.

As a result, the client received an uninterrupted connection of his CRM with the “Delivery club” marketplace.

Show More Show Less

Tools

Git

Media

The API for the mobile application "MoreThanPlanner" - the digital diary.

Company

The API for the mobile application "MoreThanPlanner" - the digital diary.

Role

Backend Developer

Description

I developed an API by which the application synchronizes the user's data with the server. It is necessary so that the user can restore their data through a backup copy.

Also, were made preparations for the subsequent scaling of the application to the desktop version and the ability of application's work on several devices at the same time.

Show More Show Less

Tools

Git

Media

The Back-end for the customer’s CRM-system (extremely large and continuous project)

Company

The Back-end for the customer’s CRM-system (extremely large and continuous project)

Role

Backend Developer

Description

The active phase of this project lasted for 12 months. I worked for 10 hours a day on this project, without days off, as the project was extremely large. Now the active phase of the project is over, and I am carrying out its technical support.

And now I want to give you some more information about the project. At first, the customer didn't have any CRM-system.

Their business grew in an avalanche, and orders have been processing on their sites’ administrative panels. There were 3 sales departments (for each direction), and one more for each region, where they were represented.

The customer had no idea what type of CRM-system was needed by its functionality. There was only an understanding that we should develop a new CRM-system from scratch and don’t take as a basis for any existing boxed solutions.

I had been helping my customer to think through his CRM-system structure and its functionality. Then, when the CRM-system's MVP-version was fully designed, we moved to its development. In this project, I was responsible for back-end development. In general, we used the following techniques in this project:

Front-end: VueJS (Nuxt.js)

Back-end: NodeJS (Express.js)

NodeJS (Express.js)

There were three stages in the development of my client’s CRM system. As I worked in a team together with the other specialists, I will use We instead of I, because it greatly cooperated team-work during the 12 months.

The 1st stage. Just in 4 months, we released the CRM-system's MVP-version. Before this, a great job on the analysis of the business processes of the company, prototyping was done. To the MVP, the check-out, orders and deliveries management, the integration with payment systems, the public API development, and, of course, the creation of a selling website, was included.

The customer had limited timing, so as in a fast-growing sector, every month of delay is equal to a missed percentage in terms of future market share. That’s why we were working extremely actively. One day, in agreement with the customer, we transferred all orders in the main direction to CRM. Sometimes after that, we worked at nights to consult managers and solve urgent problems if they suddenly arose. Probably if everything was at a more relaxed pace, night work would not be necessary, since we would have managed to do a detailed wiki on the project. But time had decided everything.

The 2nd stage. The second stage can be described as the attachment of the MVP's skeleton to the content from various kinds of integrations, features, and tools. This stage is also characterized by the transition of all areas of the company to the new CRM-system. Many external services have been integrated: for analytics, advertising, entity components management, attracting orders, etc. As a part of the second stage, massive data migration from old databases to the new CRM-system database was performed. At this stage, all sales departments were optimized and combined into a single department. The second stage lasted for 9 months.

The 3rd stage. On the third stage, the rapid growth of the system slowed down and became more deliberate. We continue to develop the project and provide the customer with technical support.

Show More Show Less

Tools

Git

Media