Distributed systems architecture and technical leadership
Across Software Architect and Tech Lead roles, Thiago focused on turning complex requirements into sustainable architectures and raising engineering practice across teams.
Problem
Organizations juggling legacy systems and new initiatives often suffer from unclear guidelines, manual integrations, and disorderly service growth.
Without explicit architecture and mature delivery processes, quality erodes and apparent speed turns into rework.
Role
As Software Architect (Globalweb) and in technical leadership roles (Hepta, FIRECODE, and others), Thiago defined architectures, set guidelines, and stayed hands-on when design needed to prove value in code.
At Hepta he led CI/CD adoption and technical mentoring. At FIRECODE he architected a scalable, mission-critical data processing platform.
Architecture and approach
The approach combines clear domain boundaries, a preference for decoupling (messaging and services), and patterns teams can operate day to day.
CI/CD and architectural reviews land early to reduce manual bottlenecks and align code quality with technical strategy.
Mentoring and shared standards turn architecture decisions into living practice—not dead documents.
Impact
These initiatives produced clearer technical guidelines, less manual delivery pipelines, and teams with greater autonomy and code quality.
Data platforms and enterprise systems gained an architectural foundation to evolve with less friction and better alignment to business needs.
Stack and themes
This case ties together the through-line of Thiago’s career: distributed systems architecture with hands-on technical leadership and continuous engineering improvement.