Eduard – Python, Node.js, Django

The client, a product company allowing designers and developers to quickly iterate over their application design, was not able to deliver on their mission due to lacking a custom-tailored backend server.

• created backend architecture
• created AWS infrastructure architecture for all services and multiple environments
• created database schema and integration
• enabled the seed funding round by designing and implementing 100% of the required backend functionality through a web server, which provides a reliable API
• enabled continuous integration and delivery by setting up the GitHub pipelines and designing the infrastructure powering both the development and production environments

The application is used by non-profit healthcare organizations who want to help patients suffering from a certain condition by hosting various types of events.

Eduard worked on the entire back-end, including user management, permissions, events with recurrences, testing, and CI/CD.

The company is operating in different cities across Europe and Africa. Local regulations state that some areas are available for business within those cities only within specific time frames. We could define those geo-areas, but operations people had to change their state to active or inactive manually.

• Implemented a robust system that allowed to pre-program the schedules for each geo-area, and would automatically become active and inactive
• Designed architecture
• Implemented design, testing, launched to live, and monitored that it works according to specification
• Created a UI that allowed the operations people to create, view, update, or delete (soft-delete) the scheduling rules

The company had a large analytics team that would write Python notebooks scattered across their computers, which we called "reports." The team wanted to centralize this work, version it, and provide a way to run it on a cluster.

• Took over the project and brought it to production
• Implemented a decorator-based method of defining the capabilities of the "report," which would be dynamically discovered by the UI through the provided HTTP API
• Worked with the front-end engineer to design the API, which made the most sense from a conceptual perspective and was as close to REST as possible

Inherited a flimsy phone system that had performance and reliability issues. A fintech company used this to connect customers with the customer support (CS) department. The customers would use their mobile phones, and CS would use a Chrome extension connected to this phone system.

• Started analyzing how the code worked and suggested areas of improvement to the manager
• Solved problems with asynchronous code
• Code readability was improved, and the workflows became clearer for the more junior developers who started working on this after

The company had a business line of automated sports trading and one of the sportsbooks. The events presented in these two scenarios were sometimes identical, but the profit and loss were tracked independently. It meant that changing the position in any of them would not impact the other, but, in reality, it should have as it referred to the overall company position in that market.

• Created a service that would be able to aggregate these changes and distribute them to any listeners, so everyone is kept in sync
• Designed the architecture of the service, discussed it with a manager, and continued to implement it after agreeing on the specifics