Rodrigo Junior - Senior fullstack engineer, ExxonMobil

Feedback from Rodrigo’s ex-colleagues

Let me see

Keep in touch with meI'm using Intch to connect with new people. Use this link to open chat with me via Intch app

Work Background

ExxonMobilSênior Full Stack Engineer

Apr. 2022EUAJava 8-17, Mongo, CometD, Routines, JUnit, Mokito Working as fullstack in an agile team in a sales application (Salesforce) I’m hired to keep and improve an application that needs listen messages from Salesforce (Orders) and send it to SAP, the issue is this application was built without good practices and no one unit tests so it’s hard improved changes without concerns, so I changed the architecture using Dependency injection, and cover the main flow of our application, document and update Java 8 to java 17, update some libs and help move it from OpenShift on prem to OpenShift cloud.

Cadmus Soluções em TIFull Stack Sr Software Engineer

Nov. 2021 - Apr. 2022São Paulo, BrasilJava 11, Spring, Oracle, Rabbit MQ, Routines, monolithic, Angular, Ionic, JUnit, Mokito, Jasmin, Cypress Working with FullStack in an agile team in a logistic application (Ionic, Angular and Java) Planning activities brought by the PO, and develop the solution after refining with the developer’s team, 100% coverage code by unit and integrations tests, communication between 2 apps using messaging with RabbitMQ, frontend interface and mobile with Ionic framework, code review and publishing with Azure.

TQISoftware engineer

Jan. 2021 - Nov. 2021Uberlândia, Minas Gerais, BrasilJava, Oracle, Kafka, New Relic, Nodejs, Routines and microservices and monolithic Working with Backend developer in an agile team of a digital bank Planning activities brought by the PO, and develop the solution after refining with the developers team, 100% coverage code by unit and integrations tests, communication between 8 apps using messaging with Kafka, could create dashboards with New RelicOne for the Product Owner can make decisions and offer new features for the client, these dashboards he could see how many transactions happens, how kind of transactions, and where state or product had less occurrence and offer special conditions for then, code review and publishing with AWS. Here the team had totally responsibility for the product since developer and published on AWS serve and monitoring specially using New RelicOne for that