I worked as part of the data acquisition and influencer metrics team, which involved working with various data providers. Our team's role was to develop and maintain software that facilitated communication with the providers, transforming JSON data into our own structure, and storing and indexing it in Elasticsearch. The software had features such as round-robin load balancing among different providers with priorities, sending metrics to Grafana, and an alert system to detect critical failures that required immediate attention. The system was built using Kotlin with a microservices architecture, running on Kubernetes, and communicating through RabbitMQ and Kafka queues.

Working on migrating a monolithic application to microservices, all done in spring boot running in AWS ECS, joining scrum meetings to organize work, technologies used: Java 13, spring boot, REST APIs, Mysql, Jira, Scrum, CI

Leading and assisting the Developers team to deliver best quality solutions in building APIs in with Java spring boot, node js, migrations from Webpshere to microservices, building containers for docker and collaborating with DevOps process, using AWS tools like ECR and ECS

As part of the global risk technology team, working in enhancement and migrations projects of risk applications interacting with many teams around the world. Some of tasks performed: ● Interface technology migration from APIs, Ibm MQ to Kakfa ● Separation of big application structure into Microservices ● Migration of Java Stándard to Srping ecosystem ● New functionalities development for the backend and the batch ● Research about tools to improve CI process ● Cloud adoption

For a risk management application running in 23 coutries of Latin America: -Analyzing issues in the application -Designing solutions and request the fix to the software factory -Coordinate the implementation process, ( tests in development, QA and production implementation) -Responsible of batch process control, ensuring performance and integrity, coordinating shifts between 8 people, weekly status meetings -Keeping the application architecture updated to ensure not to reach end of vendor support, this task involves: to analyze impact of new components versions, in case of any adjustment needed, project planning, requests to the software factory, user tests and perform all the coding cycle until the implementation