Nenad Misić

I worked on a project for Microsoft called Microsoft Connectors. A connector is a proxy or a wrapper around an API that allows the underlying service to talk to Microsoft Power Automate, Microsoft Power Apps, and Azure Logic Apps. It provides a way for users to connect their accounts and leverage a set of pre-built actions and triggers to build their apps and workflows.

Back End:
I also created, tested, and maintained dozens of connectors and occasionally worked on investigating customer-reported issues.

My tasks included creating new connector actions, updating existing connectors to have more intuitive behavior and/or to use new technologies to improve performance, fixing major build pipeline issues to increase development speed and even minor tasks like bug-fixing and documentation updates.

Being a part of a fully remote team of self-employed contractors and having flexible working time meant that it was my responsibility to self-organize, which included:
• Prioritizing when and which task to work on.
• Communicating and coordinating daily with my teammates to solve the tasks.
• Coordinating with the client (i.e., Microsoft) on the current status of various tasks and assignments.

FlexxPay is an online fintech platform for employers whose employees can instantly access their earned salaries before the regular payday; the business model consisted of acquiring employers in various worldwide locations using a simple, easy-and-free onboarding process.

I was a part of the core team that built the app's finance engine and the notification service that supported email, SMS, and push notifications and was used by every microservice in the system.

This being a financial platform, reporting capabilities were a must, so I spent a lot of time creating algorithms for extracting relevant data from the database into SQL views and then creating a mechanism for easy retrieval and display. For the robustness of the system, we employed agile and test-driven development from the start to respond quickly to our client's changing requirements.

Every developer on the project was a full-stack developer, so I helped with developing the front-end pages and components and optimizing data transfers to and from the back end.

Five Degrees is a digital banking technology provider. The service they provide is a next-generation digital banking platform, empowering financial institutions to enter the era of modern digital banking. It was designed to provide a fully automated banking services platform. There came a need for a rewrite of the old system using cutting-edge cloud-based technologies.

This was a multi-team project where many of the developers hadn't previously worked with the project's architecture. One of my responsibilities was to introduce my team to this new architecture design approach and get them up to speed.

As a part of the back-end team, I was involved in developing back-end functionalities ranging from RESTful endpoints to message handling logic, configuring communication with the database, Azure services, third-party services, and other system’s microservices.

Since this was a "cloud-native" platform, I worked extensively with a range of cloud services that handle messages, events, authentication/authorization, and storage. I even worked on a couple of assignments related to setting up the build and deployment pipeline.

Valitor provides tailor-made acquiring solutions with an adaptable pricing structure, efficient chargeback management services, and extensive merchant support and training.

I worked on updating the Valitor's multi-solution system to process American Express (Amex) payments. To accomplish that, it was necessary to enable Amex as a payment option in the Valitor's boarding system, to integrate it with the Amex API and their SFTP server, and to update the Valitor's system to be able to process Amex payment files.

It was important to Valitor this was done as soon as possible since Amex was planning on halting all pending integrations for a couple of months. For Valitor, this would have meant a potential loss of revenue.

After introducing myself to the Valitor's existing system and the requirements, I designed and developed Amex-compatible file generation and processing services and an appropriate database schema, which I integrated into the system. Together with a teammate and Amex technicians, I coordinated a successful integration between Amex's and Valitor's system.

All of this was done much sooner than Valitor expected and turned out to be one of the fastest integrations in entire Amex's history.

ToPyString is a .NET system designed as a collection extension that converts collections into strings formatted in Python style.

I single-handedly designed and implemented the library to be lightweight, simple, and intuitive to use and be compatible with both the .NET Framework and .NET Core.

I also created the build and release pipelines using Git workflows to automatically add necessary tags, convert the project to a NuGet package, and deploy it to the NuGet Gallery.

The library is also optimized and covered with unit tests.

I focused on providing a good user experience with this library, so I created simple yet detailed documentation with rich examples.

I also ran a small-scale marketing campaign to advertise the newly created library, which resulted in more than 4,500 NuGet downloads.

I developed and launched a language track on Exercism for learning Cairo through engaging programming challenges. I single-handedly created the track, and as the owner and maintainer, I ensure that the code remains open-source.

A web application for simplified donating, where donations are invested on behalf of dozens of endowments, thus enabling the original donation to grow over time. As a full-stack developer, I worked on every aspect of the app, from React on the front end to JavaScript for AWS Lambdas on the back end, and even used Solidity to create smart contracts needed for the project.