What I Actually Found Working for a Brazilian Tech Company

-

Before I moved to Brazil in December 2013, locals warned me that foreign workers struggled in Brazilian companies because they "don't understand the culture." I never quite grasped what that meant, but after working at a local tech company for nearly a year, I can share what the reality actually looked like.

I had lived in Brazil before and spoke fluent Portuguese, so the language barrier wasn't an issue. After months of job searching while teaching English to pay the bills, one of my students referred me to his company. The interview process itself was my first taste of cultural differences. The HR conversation lasted over 45 minutes and covered territory that would be off-limits in the United States. They asked about my church attendance, my family situation, and other personal topics that would send American HR departments running for their lawyers. But it felt natural enough in the context, more like getting to know a whole person rather than just a professional profile.

The biggest operational difference was the rigid time tracking. Everyone clocked in and out, and you had to hit your times within minutes or face penalties. Coming from New York tech companies where people drifted in between 9 and 10 AM and stayed as long as needed, this felt foreign at first. But it was clearly the legal standard there, and everyone operated within that framework without complaint.

Not everything was smooth. One coworker regularly told inappropriate jokes that were clearly designed to get a reaction from the rest of us. In most American tech companies today, that behavior would create serious legal liability and likely result in swift termination. Here, it was simply tolerated as part of his personality. I found it more puzzling than offensive, but it was the one aspect of office culture that genuinely surprised me.

On the positive side, the work-life balance was remarkable. We had an hour and a half lunch break, which gave me time to walk home, shower, eat a proper meal, and even nap before returning to work. There was also a regular afternoon coffee break around 3 PM where the entire team would gather in the kitchen for 15 minutes of coffee and snacks. These weren't rushed American-style "grab and go" moments but actual breaks where people connected.

The management style was collaborative and respectful. My colleagues were welcoming and professional. The work itself was engaging and challenging. I genuinely enjoyed my time there and would have stayed longer if family circumstances hadn't pulled us back to the United States.

Looking back, I wonder if the "cultural understanding" concern was more about communication style and social norms than actual work competency. The substantive differences were mostly structural: time tracking, break schedules, and workplace conversation boundaries. None of these felt insurmountable or particularly challenging once I understood the local expectations.

Perhaps the real cultural skill isn't some mystical understanding of Brazilian business practices, but simply the willingness to observe, adapt, and respect local norms while bringing your own professional expertise to the table.

Popular posts from this blog

The Dual Faces of Technology: Enhancing and Replacing Jobs

-
Image
Automation has been on my mind a lot lately, more immediately due to a book I read , but also because of the looming reality of artificial intelligence. To understand what's involved, making the distinction between replacing technologies and enabling technologies is crucial. As we traverse the timeline of the 20th century, we observe how each type of technology has distinctly influenced employment. Automated technologies have transformed industries by replacing manual labor with machines. Consider the automated switchboards introduced in the early 20th century. Previously, telephone operators manually connected calls using physical connectors on a switchboard. With the advent of automated switchboards in the 1920s and 1930s, many of these jobs were eliminated as calls were routed through electromechanical systems. Similarly, in agriculture, the introduction of mechanical harvesters like the combine harvester in the 1930s drastically reduced the need for manual labor. These machine...
Read more

The Technology Trap: Capital, Labor and Power in the Age of Automation (Book Review)

-
Image
In his compelling book, " The Technology Trap: Capital, Labor, and Power in the Age of Automation ," Carl Benedikt Frey offers a sweeping examination of the historical and ongoing impact of mechanization and automation on society. Starting with the onset of the first Industrial Revolution, Frey deftly navigates through the evolution of technology up to the modern age of artificial intelligence, presenting a nuanced view of how technological innovations have reshaped labor markets and power dynamics. Frey categorizes technological innovations into two types: enabling technologies, like the typewriter, which enhance worker productivity without displacing the labor force, and replacing technologies, such as robotic machinery in factories, which eliminate certain job roles altogether. This distinction forms the backbone of Frey’s analysis, as he explores the varying implications of each type of technology on different segments of the workforce. The book traces a historical patter...
Read more

Deputy Product Owners

-
Image
"The Product Owner is one person, not a committee. The Product Owner may represent the desires of a committee in the Product Backlog, but those wanting to change a Product Backlog item’s priority must address the Product Owner." - The Scrum Guide There are a lot of ways in which my approach to Scrum differs from what's in the official guide, and since that document refers to Scrum as 'immutable,' let's just call what I do 'Notscrum™.' In Scrum, there is only one product owner per team. That person is the sole person responsible for the product backlog, and the person who advocates for the work to be done. In Notscrum there is one product owner, but there can be multiple deputy product owners. Here's how it works. When my program at Viacom was first forming I met with the then-director of the Library & Archive group and learned that while he set the priorities on work done, the archivists were organized in three distinct areas with a team lead ...
Read more