Jordão Beghetto Massariol

I provide technical leadership for the team, serving as the architectural reference point and decision-maker on stack, design patterns, and the structure of new systems. I led two simultaneous rebuilds of state government systems, modernizing Groovy/Grails applications into React, TypeScript, and Java Spring Boot, and I own the definition of the REST contracts between frontend and backend. Day to day, my responsibilities mean I write somewhat less code than before, since I increasingly coordinate the process itself — writing and refining tasks, running daily standups, sprint planning, refinements, and retrospectives, aligning estimates and scope with the team, talking directly with clients about deadlines, deliveries, and staging approvals, reviewing code, and keeping the CI/CD pipelines and the development, staging, and production environments always running. I also onboard new developers to the team and take part in the company's strategic decisions.

This is where I went from executing to deciding. I architected the company's first rebuild projects, defining the stack and repository structure for teams that would grow in the years ahead. I ran technical hiring interviews, reviewed other developers' code, and started writing and refining tasks for the team, while also expanding into the Angular framework on corporate projects. The work started splitting between code and process — and process increasingly became part of my day to day. Strategic decisions from the company combined with my own professional alignment pushed me to keep growing in seniority. In parallel, I worked on a few smaller internal projects where we automated processes that would later benefit my own management work.

I started stepping away from the keyboard for a few moments: I joined my first architectural decision meetings, still as a contributor rather than a decision-maker. In parallel, I deepened my knowledge of the stack we were using for projects at the time (React/Angular on the frontend; Java Spring Boot/Quarkus on the backend; PostgreSQL, MySQL, MongoDB, and Redis for databases). The goal was to execute tasks faster without compromising the final result. I began following the full cycle of agile ceremonies — daily standups, sprint planning, refinements, reviews, and retrospectives — as an active participant, not just a task executor.

At this stage, I started earning the trust of more experienced developers and was assigned to a CRM project a bit more complex than usual — a system that already existed and was already a proven success story before I arrived. I became a key part of implementing entire features, integrating authentication via LDAP/Active Directory, writing stored procedures in SQL Server, and building reusable React components in TypeScript, always in direct contact with the Node.js and Java Spring Boot backend. I worked side by side with the QA team fixing bugs, bugfixes, and hotfixes as tickets came straight from production — spotting N+1 queries that were freezing entire screens and writing unit tests to prevent regressions. I also took my first steps into mobile development with React Native. I was still early in my career, but I was already showing the team and management my potential within the projects and my drive to solve problems.

I started at the company from the basics, working on just one or two projects at a time and focused on simpler tasks: fixing visual bugs, adjusting simple endpoints, straightforward CRUDs, and one-off screens. I attended daily standups mostly as a listener, reporting my status to more experienced developers. At times during the day, I paired with colleagues who had been there longer — that's how I learned the system's business rules and got a hands-on understanding of a developer's day-to-day routine.