« Back to articles

2013 - Working on a Micro-service Culture

In 2013 was the year I worked for Globo.com, one of the biggest media companies in Latin America, and as you can image by the title, there was a lot of APIs.

How everything started

After people living my last team, I decided to leave it as well and join a bigger challenge, work in one of the most prestigious technology companies of Brazil.

A friend of my who worked there has recommended me to his manager, and then I had a very long and hard hiring process ahead.

I had a phone call interview, and several other technical interviews, including a challenging project that would have to process millions of requests per second as a requirement.

I was joining a new team, that would be responsible for creating internal products that would be consumed by other developers, allowing them to release final projects faster.

First impressions

I had an initial shock about the company's culture. After working on a fast-paced environment, I got very pragmatic and I remember we had several long meeting to make sure the everything was being well thought out.

It took me a while but I got used to it.

Technical aspects

Everything was done using micro-service architecture, and we had several projects in several different technology stacks. That was great because I had the opportunity to work on several codebases, with several different people.

I grew a lot having to work with so many other highly talented developers. And engirding in high-level architectural decisions that would impact several other developers as well.

Thinking about scale

Everything that we had to do needed to be able to scale tremendously and also be very performant. A had the opportunity to work on several phases of optimization and polish all my skill about high-performance and high-availability software working on these products.

Cross team collaboration

When our projects were getting mature, and while they were being developed as well, we had to work close to our future clients, helping them to use what was build and also understanding better our use cases.

At this point, we have several other teams to talk to, to collect feedback, to understand use-cases, to discuss ideas. It was the most collaborative work I've done so far.

Management style

At this company, the team played a really big role in what and how things would be built.

We have enough autonomy to decide technologies, patterns, frameworks, and agile methodologies.

The company also provided in-company training, for both technical and non-technical to ensure people are getting evolved so they can tell people what needs to be done and not how to do things.

Being part of a family

The company culture really stood out. People were very friendly, and that was the company where people would work for decades, literally.

The company uses to hire the best people anywhere in the country and I was lucky to meet so many nice people.

Wrapping up

Working on a very large company with the most talented developers in the country was an honor. I had the opportunity to shape my skill about development high-performance, high-scalable and hi-available software as well as understand better about different management styles diving into a huge agile company.

Regards,
Renan de Azevedo

Updated at 2020/06/26 12:53.

Recent publications: