Product: Enterprise resource planning app for agencies. Features work planning, logging, calculations, offers/invoices generation, multi-database, calendars, Gantt charts, reports, mailings, and bookings. As a lead developer and team leader I was in charge of the following during my 14 years of cooperation with that company: Key Responsibility/Task 1: My main responsibility at first was to develop the core features of the application using the PHP/MySQL stack. As the team grew I also became a team leader and was responsible for the overview of the whole development process. The application started as an internal tool for the company but during my stay, it became widely used by more than 500 companies in the DACH region. Key Responsibility/Task 2: During the development process, I started with an in-house framework but after several years we decided to migrate to a public framework Symfony. Over the years, we've made several big modules like Calendar, Mailings, Bookkepings, Dashboards, Time Recordings, and so on. There, were several integrations made, notably with the Exchange, Google Drive, and FTP servers. Achievement: One of the challenging ventures was to design a complex approval system for documents to land a bigger client (over 5,000 users). The time constraints were challenging but the operation was a success. As a team leader, I was responsible for my team and I was handling the quarterly evaluations for them. Together we were able to pinpoint some strengths and interests which resulted in one person becoming DevOps and another one migrating towards automated testing. Technology/Tools Used: Worked initially with Kanban and then switched to Scrum with biweekly sprints. The product was dockerized, and the codebase was in GitLab.

Website

As a backend developer I was in charge of the following during my 2 years at the project managing online visitors registration Key Responsibility/Task 1: at first my main responsibility was to develop new features, refactor existing ones, and handle various data migrations (exports, imports) as well as prepare a multitude of statistics via complex SQL queries. During my tenure I experienced my work being heavily connected with database operations, I was working with triggers, procedures, and cursors. We used the Oracle Database. Key Responsibility/Task 2: I was also involved in creating the next version of the application that was made from scratch and in different technologies. We migrated from PHP to Java (using Spring Framework / Spring Web Flow). I was responsible for mail-sending logic and generation of the highly configurable mail templates using the Velocity engine. Achievement: The main goal was to make the application highly effective since it contained millions of entries and it operated in peak intervals (high usage before and during Fairs and lower usage normally) Technology/Tools Used: For codebase handling we used CVS initially but then migrated to SVN. We used an iterations-based approach in our work.

Website

Product: Application that allows easy exchange between fiat and cryptocurrencies in both directions. As a backend developer, I was in charge of the following during my 9 months at the project: Key Responsibility/Task 1: I was a member of the Compliance team that was responsible for all tasks related to Risk and Compliance topics. Those topics included integrations with several providers such as ChainAlysis, ComplyAdvantage, and SumSum. We've been responsible for handling KYT, KYC, and Name Screening processes required for proper transaction handling. Key Responsibility/Task 2: I was responsible for event-driven messaging and performed various improvements in that area (such as message versioning, migrations, etc.). We used RabbitMQ as our message broker. This also had to be compliant with our event sourcing. Since we were just one of many teams, our domain was providing contracts and integration events so that other parts of the system could easily connect and talk with our services. Achievement: The most challenging task was to perform migrations of events (hundreds of thousands) in a zero downtime environment (the application had to be always online). Technology/Tools Used: We worked here with Kanban. The codebase and all CI infrastructure were handled in GitHub. The project was fully dockerized. We used PostgreSQL and Redis.

Website

Using Django’s Plotly Dash to visualize certain data coming from machine learning models based on banking and macro data –visualization of possible correlations.

Website

Integrating FINGO website with PipeDrive and ClickMeeting. Migration of all Zapier flows into own codebase due to GDPR requirements.

Website