Software Architect for the Checkout BackEnd team, responsible for orchestrating data from various sources and creating orders for millions of users worldwide, distributed across America, Africa, Europe, and Asia.The application is a microservice that utilizes Java and Spring Boot with Maven for dependency management. Unit tests are written using JUnit 5 and Mockito, while integration tests use Spring, RestAssured, Wiremock, TestContainer, and Cucumber. The entire infrastructure is hosted on Microsoft Azure, with various features of Azure DevOps, mainly Azure Repository, Azure Artifacts and Azure Pipelines. ArgoCD used for cluster management, while New Relic provides metrics, alerts, dashboards, and logging capabilities.Responsibility of representing the Checkout team in business meetings and providing general, with a key role in prioritization and work delegation within the team. Tech Lead capabilities serving as focal point for technical guidance, conducting code reviews and feedbacks.Led several significant business features, including onboarding of new partners, new delivery method and business rewards restructure. Migration of numerous duplicated features to other applications: collaborating with other architects, we devised a comprehensive migration plan, with a toggle fallback mechanism to ensure application stability during the migration process.I guided and planned a complete restructuring the project's internal architecture, focusing on the Chain of Responsibility design pattern, asynchronous code handling with Java's CompletableFuture, Domain Driven Design and Hexagonal Architecture. I created tasks, defined schedules, and presented to peers, engineering leaders, and project stakeholders, establishing a phased development approach. Participated in the creation and development of a new branching strategy for the team, transitioning from trunk-based development to environment branching.

Software BackEnd Engineer in a segment focused on facilitating the integration of new partners into the platform. I contributed to two teams, one that operated a microservice that connected to platform topics and external endpoints to update partner information, and other that developed several REST/RESTful API endpoints to validate and parse data related to product registration.Internally, the application used Java and Spring Boot, with Maven for dependency management. Kafka was employed for event handling, with additional features such as Confluent ksqlDB. File Management developed several endpoints to validate and parse data related to product registration. Azure Blob storage was employed for managing large data chunks and handling heavy file processing. NoSQL and MongoDB were utilized for resource management, and Kafka played a role in optimizing heavy workloads. Both applications used the hexagonal architecture pattern.Led an initiative to develop a mock application for the segment, that was built with Java and Spring Boot, PostgreSQL for database management and Flyway for schema creation. This application enabled flexible mocking and included a set of management endpoints for configuration. For documentation purposes, I implemented OpenAPI in a handful of projects to be stored in Stoplight, with dynamic creation of documentation into the pipeline, using scripts to orchestrate data using the Stoplight API.

Software BackEnd Engineer focused on the checkout process of an e-commerce platform. The platform is focused on small and medium consumers, such as bars and restaurants, and sells products from AB-Inbev and partners. The Checkout BackEnd team is responsible for orchestrating data from various sources, creating orders, and consuming necessary resources. The platform had millions of users worldwide, spanning America, Africa, Europe, and Asia.The application is developed Java and Spring Boot, with dependency management handled by Maven. Unit tests written using JUnit 5 and Mockito, while integration tests utilized Spring, RestAssured, Wiremock, TestContainer, and Cucumber. Integration tests written as use cases in Gherkin. Asynchronous code with Java's Future interface. Operated on a few secondary applications that used RabbitMQ to listen to events from other applications and NoSQL with MongoDB for database management, using Spring Data Mongo.The entire infrastructure is hosted on Microsoft Azure. Azure DevOps with Azure Repository, Azure Artifacts and Azure Pipelines. ArgoCD used for cluster management, while New Relic provides metrics, alerts, dashboards, and logging capabilities.Part of a major version release, necessitating adaptation across all the company. The core business strategy shifted towards multiple integrations per user and partner. As the Senior BackEnd Engineer, I took on the primary responsibility for driving this significant codebase change, alongside the Software Architect.

Software BackEnd Engineer for a multi-factor authentication (MFA) project focused on account security for PagSeguro PagBank, with over 20 million users. The project aimed to provide secure identity verification for various features such as password change and login.Microservice developed as a REST/RESTful API that used Java, Kotlin, and Spring Boot with Gradle for dependency management. SQL with Oracle was used for database management, while unit tests were conducted using JUnit 5, Mockito, and Wiremock. Kafka served as the message broker for sharing data from the MFA process with other applications, Jenkins was utilized as the CI/CD tool.The entire infrastructure was hosted on Amazon Web Services (AWS). Various AWS services were used, including Amazon SQS, Amazon RDS, Amazon EC2 and Amazon ECS. Monitoring was done through New Relic for dashboards and alerts, and Splunk for logging purposes.Tech Lead capabilities becoming the reference point for the team regarding production complaint analysis and participated in technical and business meetings with many other teams. Significant contribution leading the implementation of the QR Code authentication method that involved complex settings and integration between the mobile and web platforms.

Software BackEnd Engineers for many applications that belonged to the logistic solution company Trato, that dealt with the exportation of grains overseas. The product was distributed through many smaller components. Among the many products, the most notorious were a mobile app where the truck driver could control many features and web applications that allowed admins to schedule different actions.The project had a DevOps practice where the engineers were responsible for both development and infrastructure. For the development, they were microservices that worked as REST/RESTful APIs, using Kotlin and Spring Boot. Database management had both NoSQL with MongoDB and SQL with PostgreSQL. The applications were heavily focused on events for managing invoices, notifications and scheduling, using Spring Cloud with Google Pub/Sub.The infrastructure was initially built using Docker and Docker Swarm, entirely hosted by Google Cloud Platform. Machine provisioning using Ansible. Many Google Cloud Platform (GCP) features were used, including Google Stackdriver, where I was the main provider for the creation of alerts and dashboards, and Google Dataflows.Tests had different levels, using JUnit and Mockito for unit tests, Wiremock, Newman and Green Mail for integration tests. At one point, Keycloack was adopted to manage authentication, which previously was implemented with Spring Security. Helped replace Docker Swarm for Kubernetes being responsible for implementing replica sets for our MongoDB database within the cluster. Later we would use Google Kubernetes Engine. Contributed to a new product that demanded complex database management and a poor source of data. The application needed to integrate with emails, break data from spreadsheets and save it in a MongoDB database. Later, many complex queries were used to create dashboards upon this data, which required advanced usage of Spring MongoDB and MongoTemplate queries.

Software BackEnd Engineer for the digital bank Olé Consignado, that specialized in payroll loans through a long and complex simulation flow. Internally, the project utilized Java and Spring Boot, along Maven for dependency management, while Jenkins supported CI/CD workflows. MapStruct and Feign Client HTTP were employed for HTTP connections and business mapping, and AWS served as our cloud provider. Testing was done using JUnit and Mockito, and our team operated within the Scrum framework.I played a main role in a highly successful campaign launched by the company, leading the implementation of an evaluation feature that significantly boosted the app's presence in both the Android and iOS mobile stores. The feature's display was tied to strategic actions within the app's flow, such as successfully obtaining a loan or completing the simulation process.Also contributed to the implementation of biometric authentication for mobile users. This required making changes to the BackEnd, introducing new security checks, and orchestrating the use of special authentication tokens. Successfully deployed important loan-related changes independently, requiring a different resource orchestration approach from what had been previously done.

Intern for the digital bank Olé Consignado, that specialized in payroll loans through a long and complex simulation flow. I worked on a REST/RESTful API built with Java and Spring Boot, which integrated numerous resources from legacy bank systems and ensured functionality for both web and mobile FrontEnds.Maven was used for dependency management, Jenkins facilitated continuous integration and continuous deployment (CI/CD), while MapStruct and Feign Client HTTP were employed for HTTP connections and business mapping. Additionally, we relied on AWS as our cloud provider. Testing was conducted using JUnit and Mockito, and our team operated within the Scrum framework.Contributed to the implementation of the IN100 feature, which entailed authorization for data searching in Brazil. In addition to my project-specific responsibilities, I took the opportunity to study various concepts and prepare myself for the industry. This included delving into technologies such as Google Cloud Platform (GCP), Docker, Kubernetes, NoSQL, and other emerging technologies that held relevance beyond the scope of this particular project.