Pedro

Billups 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:

• Design and development of new features
• Bug fixes
• Projects:
  • Exposure Dashboard: the dashboard displays exposure reports to customers. This brings in some extra revenue to the company and helps to alleviate a bottleneck where media planners have to generate the reports manually. The back end is written in Go using Timescale as the main database, while the front end is being developed in React (TS).
  • GraphQL BFF: due to the small size of the team, contracts between the FE and the BE teams tend to be defined in a less structured way, which sometimes results in blockers. To address this issue, a new project was proposed to serve as an interface between the FE and the BE services, following a BFF pattern. The team chose to explore GraphQL as an alternative due to its flexibility and the possibility to have a single entry point to the APIs.

Technologies used:

• Golang
• Git / GitHub
• Drone
• Rancher
• Kubernetes
• PostgreSQL
• Docker
• React (TS)
• GraphQL
• Elasticsearch

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:

• Design and development of microservices.
• Research and implementation of integration with external systems.
• Mentoring new colleagues.
• Project:  SDP; a service delivery platform, acting as a subscription manager and a payment gateway. Users subscribe to services provided by external partners, and the payment is done through our major clients, currently telephone companies (the user is either billed or has his pre-paid credits charged for the services). Currently, the subscriber base is at roughly 50 million subscriptions.

Technologies used:

• Spring Boot
• Java 8
• GoLang
• Angular
• Git
• GoCD
• Sonar
• AWS: ECS, EC2, SQS, DynamoDB, RDS (PostgreSQL), Lambda, Kinesis
• Docker
• Microservices integration: Feign, Camel components, Kinesis
• New Relic
• Documentation: Swagger

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:

• Design, implementation, and debugging of integration with partners’ systems (e.g. Amazon Alexa).
• Maintenance and bug fixing.
• Major refactoring of the existing projects.
• Project:  TrackPlayback: a service that has been in production for a few years. It plays a central role in the control and logging of user activity regarding tier-2 devices. Developed in Java, using Spotify’s Apollo framework, its main responsibility was to transport and transform state machines representing playback contexts.

Technologies used:

• Apollo (Spotify’s Java framework)
• gRPC / Protobuf
• ABBA / Remote Config (Spotify’s feature flag / AB testing platforms)
• Git
• Tingle (Spotify’s CI/CD platform) ● GCP: Bigtable, BigQuery

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:

• Design and development of microservices.
• Research and implementation of integration with external systems.
• Migration of user database onto our platform, after going into production.
• Mentoring new colleagues.
• Project:  SDP, a service delivery platform, acting as a subscription manager and a payment gateway. Users subscribe to services provided by external partners, and the payment is done through our major clients, currently telephone companies (the user is either billed or has his pre-paid credits charged for the services). So far, the subscriber base is at 14 million subscriptions, with an estimate of roughly 40 million subscribers by the end of the migration phase.

Technologies used:

• Spring Boot
• Java 8
• GoLang
• Angular (not my focus, I would help when needed)
• Git
• GoCD
• Sonar
• AWS: ECS, EC2, SQS, DynamoDB, RDS (PostgreSQL), Lambda, Kinesis
• Docker
• Microservices integration: Feign, Camel components, Kinesis
• New Relic
• Documentation: Swagger

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.

• Implementation and design of Software, under the Scrum Agile framework.
• Customization of a large third-party PLM system.
• Client is a large company in the automotive industry.
• Projects:
  • Windchill: PLM platform used in several departments of the customer. My task is to help customize it to allow for some specific reports to be generated by the MANCoRE project.
  • MANCoRE: Web application that serves as an interface between the PLM software and the company’s validation service. Validation reports for parts of Windchill projects are generated and displayed to the users.

Technologies used:

• Spring / Spring Boot
• Thymeleaf
• JavaScript / jQuery
• Git and SVN
• Continuous Integration: Jenkins
• Oracle
• Maven
• TDD: JUnit, Mockito
• Antlr

Responsibilities:  Implemented features, including modeling and design of new entities and defined new tasks, when appropriate.

• Implementation and design of Software; definition of new tasks for the backlog.
• Small team of 7 professionals.
• Project: Simulation Resource Planning: SRP allows users to keep a database of resources related to the field of Modelling and Simulation, such as models, scenarios, and services.

Technologies used:

• JSF
• WildFly
• JavaScript / jQuery
• Git
• Continuous Integration: Bamboo
• PostgreSQL
• Maven
• TDD: JUnit, Arquillian
• IntelliJ IDEA
• Flyway

• Sabbatical: public exams preparations in Brazilian Public Sector (2014-2015)
• Junior Java Developer at Mobicare (2013)
• Java Developer Intern at COPPETEC Foundation (2011-2012)