Pedro is a Senior Software Developer with over 7 years of experience designing and developing modern web applications. His experience has had a focus on the back end, using mostly Java and Spring / Boot. Recently, he decided to get more hands-on experience with Golang and enjoys learning new languages. Another trend in his recent roles has been to work with distributed, microservice-oriented architectures. Some key technologies in that context with which he has had experience are AWS (to name a few services: DynamoDB, ECS, Lambda), CI/CD tools (Drone, GoCD), relational (mostly PostgreSQL), and non-relational DBMS (Dynamo and Mongo), cache clusters (Redis), Docker, GraphQL.
Hire PedroBillups is a major company in the OOH (out of home) advertising business. They have an engineering team responsible for building their internal platform, which helps media planners plan campaigns and keep track of their advertising catalog. Responsibilities:
Technologies used:
Designed solutions for new features. The project followed Scrum guidelines coupled with other industry practices, such as sticking to a Git flow with a pull-request reviewing requisite, CI/CD, and a DevOps culture. The platform was launched in August 2018:
Technologies used:
Responsible for the back end of the integration with what is referred to as tier-2 devices, i.e. all Spotify clients that are not the Mobile or Desktop apps and range from Smart TV apps to Spotify’s SDK running on speakers such as Sonos or Amazon Echo devices. His squad owned a few services that were very central in the request chain related to tracking playback. The services interpret, translate and exert certain control over commands issued from/to devices, while also collecting playback activity data that is ultimately used for the calculation of royalties to the artists, and to generate key metrics on user activity. Activities included:
Technologies used:
His first professional experience working with Microservices architecture. He joined the project early on when the main discussions about the architecture and design of the initial backbone services took place. The project followed Scrum guidelines coupled with other industry practices, such as sticking to a Git flow with a pull-request reviewing requisite, CI/CD, and a DevOps culture. The platform was launched in August 2018, and his activities were:
Technologies used:
Acting as an external addition to the customer’s team, his role was to help with the design, implementation, and planning of the projects. The context of the projects lied within the product configuration department of a large enterprise, and the validation of their Product Lifecycle Management projects.
Technologies used:
Responsibilities: Implemented features, including modeling and design of new entities and defined new tasks, when appropriate.
Technologies used: