Software Developer in Zagreb, Croatia

I upgraded and improved an existing React/Node.js microservice which acted as a front end for a third-party system. It was part of a microservice system running on Kubernetes.

The code was built and deployed using a CI/CD pipeline based on Docker containers.

The app was communicating with another microservice and had realtime updates with UI refreshing when data in the back end changes.

My responsibilities were to improve existing system design, fix a number of issues, and take the app out of a legacy state into a more modern system to work with. I also proposed a number of changes to improve UX and fix eventual consistency issues that might occur in the system.

I was working as a full stack developer on their React/Redux based frontend app with Elixir microservices in the backend, it used GraphQL for client-server communication.
I was leading the frontend development, rewrote and simplified their frontend implementation, fixed the redux usage patterns and introduced testing.
I've created an automated CI/CD pipeline based on GitHub actions which would run checks and deploy the app if it passed the linting & tests.
I was also doing integrations in the backend, mostly GraphQL/client app facing ones.

I also dockerized some of the backend apps and wrote docker-compose scripts to simplify development. Developers needed to run a docker-compose up and then start their apps instead of installing and managing all the required infrastructure.

A knowledge-brokering platform used across the world in the client's offices (China, Pakistan, Germany, UK, US, and Chile), the idea is to connect clients (people who need a job done) and experts (people who have the knowledge) and the platform has a vast base of engineers worldwide, all experts within their fields.

The platform was built using React, Node.js, MySQL (in a master-slave configuration), ElasticSearch, Redis, and had a custom Chrome plugin.

In production, three instances of the app were load-balanced to properly handle the load.

It has three different "sub-apps" - for company's employees, for clients, and for experts which were organized in a "micro-frontend" kind of way.

The app was running almost 24/7, with super short deployment downtimes, sometimes deployments were handled with no downtime whatsoever.

A CMS system and a tablet app that enabled the Allianz insurance sales to digitalize all their documents, charts, tables, etc. via the CMS and have it online and change it as needed.

The app on the tablet was highly animated and eye-candy focused, it would cache the content locally and sync when connected online.

By relying on MS installers and automation we enabled the client to install the app to thousands of tablets in a single click.

React native app (iOS and Android) for a real estate company that rents apartments and objects, it has a number of functionalities to offer their tenants easier apartment maintenance, have access to emergency contacts, rent-paying, track updates in their neighborhood area, new apartment search, etc.

The backend was a Node app with MySQL, it was using client's Odoo platform to sync up data between the systems.

A platform that is an abstraction of an old legacy system for field service management. It's a part of the initiative to reduce maintenance costs for the company since it has a 20-year-old legacy system that it looks to retire.

It was decided to split the monolith platform into microservices (what's called "strangling the monolith") so we created two microservices written in Elixir and using PostgreSQL which communicated with the old platform and extracted core pieces of functionality to it.

The app has a CI pipeline to automatically build docker images when new code is pushed. The cloud servers were linked to the docker repository and were automatically redeployed when new versions of images tagged as "stable" would be created.

Tweaks were made so the microservices could run both on cloud (using Azure App Service) and on-premise (on Windows Server and leveraging IIS).

For Windows Server, it was integrated with a custom made installer so system admins can just run the installer and click through it to set up their whole system without much manual intervention needed on their side.

A countrywide game with prizes where, on bottle caps, you would find codes and enter them in the web app and could win different prizes. There were millions of codes generated and printed on bottle caps as a part of the promotion.

The app was based on React, Node.js, MongoDB, and SASS for styling. It was running for a few months.