About
Who I am, what I work on
I've been a software engineer for over 7 years, mostly on the backend. Today I work remotely from Brazil for a U.S. company, where I take part in technical and architecture decisions and also write a good share of the code.
I like working on systems with some history: old code, parts nobody wants to touch, errors that show up for no clear reason. Figuring out how the system got there and making it easier to evolve is the part of the job I enjoy most.
I use AI every day, and it makes me faster. But deciding what to build, which trade-offs to accept and when to stop is still my job. The tool helps most in the hands of someone who already understands the problem.
Current
Senior Software Engineer
Languages
English C1 · Spanish B1
Philosophy
What guides me
Own the outcome
I don't wait for a ticket to show up fully specified. If I see something that could be better, I start the conversation, propose the fix and follow it until it's running in production. If the decision was mine, so is the result.
"If I'm not the one accountable for it, it isn't mine."
Understand the business
Before the code, I want to know who uses it, where the revenue comes from and what actually matters to the customer. The final test is always the same: did it solve the problem and move the business forward, or was it just a programmer's luxury?
"Code is a tool to solve problems and generate revenue, not a technical showcase."
Curiosity
When something doesn't make sense, I go after the why, whether it's in the code, the data or the process. And I change my mind without drama when the evidence shows I was wrong.
"I'd rather ask why than pretend I understood."
Straight communication
I speak up early and say it straight: the deadline that won't hold, the decision that will cause trouble, the topic nobody wants to bring up in the meeting. A decision the team doesn't understand ends up being redone.
"If nobody understood it, it wasn't communicated."