most read
Software Engineering
Why We Killed Our End-to-End Test Suite Sep 24
Product
Product Managers: what they do and why we need them Feb 15
Software Engineering
The value of canonicity Oct 30
Careers
We bring together great minds from diverse backgrounds who enable discussion and debate and enhance problem-solving.
Learn more about our careers



It is common that, as companies grow, some of their values are lost. Success is great, but maintaining the values of that small team that started the business is essential for its future.
It was with this scenario in mind that Nubank’s Analytics Engineering chapter decided early on that it needed to create a ritual – which would end up becoming one of the most important events of the team to date.
TGIF from Brazil
Pepijn Looije, one of the pioneers in the chapter, says that when they were just four professionals, they already wondered how they could ensure healthy growth without letting connections and knowledge exchange get lost.
After researching solutions to be implemented from the beginning, the engineers realized that Nubank’s Design team was already facing the same problem, and found a solution that could be adapted to other chapters’ contexts. The inspiration came from a letter from Google’s founders at the time of the company’s IPO in 2004.
That is how TGIF was born, an acronym for Thank God It’s Friday – the good old Sextou for Brazilians. So the team had 20% of their time set aside for these interactions and ideas, intended to make these exchanges and to maintain the connection.
And now? See, below, how was the process to make TGIF a continuous and productive practice.
First of all: the hires
The first complementary measure to the ritual was to define criteria for future selections and hires. In other words: the only way to ensure that the culture would be maintained would be if the team hired people aligned with the thinking of the Nubank’s Analytics Engineering chapter.
For this, they defined the questions that would be asked to the candidates, which technical skills were expected, and which behavioral parameters would be indispensable.
Even so, how to maintain this culture created by four people? How to group multidisciplinary and physically distant teams even before the pandemic? How to be sure that everyone would grow together and share the necessary knowledge to perform their role?
For these questions, the evolution of TGIF has provided some answers.
Check our job opportunities
TGIF: from genesis to the future
Every project beginning is full of opportunities and learning, and with TGIF it would be no different. Observing the three moments of the presentations used in the meetings, it is possible to notice an evolution that goes beyond the most obvious aspects of design and visual identity.
At first, the topics were just discussed as part of an agenda for the day. But the meeting quickly evolved into something bigger, a moment for the team to give opportunity for exchanges and celebrations. You had to start by breaking the ice, introducing newbies, or just chatting over coffee.
From the debate of ideas and exposure of problems, or even requests for tips emerged the TGIF Projects. These were projects guided by two of Nubank’s core values:
“We think and act like owners” and “We build strong diverse teams.”
With that in mind, the team managed to awaken ideas that had not yet been considered or even new adaptations for solutions with a little bit of the prior knowledge of one team member or another. Thus, Analytics Engineers were able to learn and share knowledge more effectively.
Some of the projects developed from TGIF meetings:
Tools
Research on topics and concepts
Chapter governance and maintenance-oriented activities:
How to implement a ritual like TGIF?
To all teams that intend to create a space for meeting and maintaining culture as Nubank’s Analytics Engineers did, it is worth paying attention to the four golden tips that can help in the process.
Nubank’s Analytics Engineering actions
Currently, the AE team has 115 members and has already tried several options to maintain the relevance of the meeting and continue connecting so many people even in a fully remote work scenario, after the beginning of the pandemic, in March 2020. Some examples of actions:
Use the time for Happy Hour and integration
Meetings:
Knowledge sharing
Challenging projects that allow you to practice different skills such as Agile, Product Management, Software Architecture, etc.:
Check our job opportunities