Software Engineering at BTG Pactual

Professional

I ship foreign-exchange software at BTG Pactual with domain experts, across frontend and backend.

Where the problem gets real

I work on foreign-exchange software where a feature rarely stops at a screen or an endpoint. The interesting problems sit between product rules, integrations, persistence, and validation, and they have to behave correctly under real operational pressure.

That means the first version of a requirement is usually not ready to become code. I have to understand what traders and domain experts actually need, where the constraints come from, and what the system should do when the happy path stops being happy.

What I own end to end

I sit with the full path of a feature: shaping its behavior with the people who own the domain, writing code across frontend and backend, validating the edge cases, and helping take the change to production.

My official title is IT Assistant. I joined as a Software Engineer Intern in May 2023 and moved into this role in May 2025. Software engineering is still the craft I practice every day, but I keep the official title clear.

Turning domain rules into software

I spend a lot of time turning business behavior into rules the system can enforce consistently. We discuss expected behavior early, expose the awkward cases, and only then carry the decision through APIs, persistence, interfaces, and automated validation.

I have taken an external integration and an FX workflow through that full path. I have also helped move backend responsibilities toward clearer service-oriented boundaries and worked with concurrent processing where timing and validation need to agree.

What careful delivery looks like

The visible outcome is software that reaches production with its rules made explicit enough to review, test, and operate safely. That is less dramatic than a single architecture reveal, but it is the part of the work I value most: reducing ambiguity before it becomes an expensive mistake.

I cannot publish internal topology, counterparties, or operational metrics. The useful claim I can stand behind is the engineering discipline behind what I ship, not a number I cannot defend publicly.

Built with

C# / .NET / React / REST APIs