We can organize an interview with Aldin or any of our 25,000 available candidates within 48 hours. How would you like to proceed?
Schedule Interview NowBeing part of Softaims has allowed me to see the full spectrum of what technology can achieve when guided by empathy, discipline, and creativity. Each assignment, regardless of size, represents an opportunity to bring clarity to complexity and to turn ambitious ideas into tangible outcomes. I’ve come to realize that successful development isn’t just about writing code—it’s about listening carefully, understanding deeply, and designing thoughtfully. Every client brings unique challenges, and I make it a priority to align my work with their goals, ensuring that the end result is both effective and lasting. Softaims fosters an environment where collaboration is not optional—it’s essential. The collective expertise within the team pushes me to think beyond conventional boundaries, to question, refine, and innovate. I believe that this process of shared learning and experimentation is what makes our solutions resilient and impactful. My ultimate goal is to build technology that feels effortless to use yet powerful in function. I approach every task with the mindset that small details can make a big difference. Through continuous refinement and dedication, I aim to contribute to the kind of work that not only serves today’s needs but anticipates tomorrow’s possibilities.
Main technologies
4 years
2 Years
2 Years
2 Years
Potentially possible
This project focuses on upgrading legacy Java applications by migrating from Spring Boot 1 to Spring Boot 3 and updating Java from version 8 to 21. The transition aims to modernize application architecture, improve performance, and leverage new features and security enhancements in both Spring Boot and Java. The project involves refactoring code, updating dependencies, and addressing compatibility issues, ensuring that the upgraded system is stable, efficient, and future-ready for continued development.
Resolved critical issues for a Self-Service Kiosk by implementing a centralized logging mechanism for better error tracking. Fixed a memory leak related to Java Rx by unsubscribing event listeners before removing them from the UI, preventing further leaks. Improved UI task handling with exception management to prevent app freezes. The result was a more stable, responsive application with improved memory management and smoother user experience.
I developed a Jenkins plugin for a cloud hosting service specializing in the Apple platform using Java. The plugin dynamically provisions macOS build agents, executes jobs, and discards agents post-build. I improved Java code quality using tools like SonarQube, Checkstyle, and PMD. Critical bugs were fixed, and the code was refactored using Java best practices such as SOLID principles. I also wrote extensive unit tests with JUnit, Mockito, and JaCoCo to ensure the stability and maintainability of the Java-based solution for users.
👨💻 Client Our client is an innovative global company from the Fortune 500. Consumer Goods Producer and Retailer with headquarters in Switzerland that sells its products in 130 countries. A newly conceptualized Digital Eco System is comprised of a set of capabilities including an online shop & website, linking online & offline, customization & personalization, engagement & membership, and digital product & services main differences. The project is built on microservices architecture and all communication between services is made through API calls. ❓ Challenge The customer needed to decrease time to market, cut costs of development and enhance the quality of APIs. 🎯 Solution Implementation of the API first approach has enabled us to solve all the challenges. In order to speed up the development (which naturally led to a decrease in time to market and cut in development costs) we made the following: 1. For the new API we have Introduced contract testing. It enabled us to first define the contract that back and front had to follow. So here we can say that they have already “integrated” their solutions with each other in the very beginning. After they created the contract they could come and implement it in parallel. This way teams that work on dependent APIs got an opportunity to work independently. Also, contract testing helped us to get rid of expensive and brittle integration tests. 2. Applied OpenAPI Specification. API documentation made it possible to add new services and technologies to applications without having to re-architect the entire system. Also, developers didn’t need to spend time on creating mock services or clients to test their API independently - SDKs and mock APIs were now auto-generated. 3. Integration-first approach was applied to the design of new APIs. Frontend and Backend teams were now determining the specification of API together and writing it down into a contract. And then used that contract in contract testing. It led to a much decrease in the number of bugs located in back-front integration functionality. Improvements also led to enhancements in the quality of APIs. API functionality specification was derived from the actual needs of back-end and front-end teams rather than assuming how it could be used on a wider basis. The implemented solution was solid and reliable enough to decrease the number of bugs found by QA by 34%. Mainly it happened because the UI team didn’t need to make sophisticated workarounds to interact with API logic.
We are a cloud hosting company in Switzerland with specialization on the Apple platform. Flow stands for quality cloud services, operated with passion by people who care
Master of Computer Applications (MCA) in Computer science
2006-01-01-2012-01-01