Maikon Will

I started in enterprise Java and systems that moved a lot of data. Over the next decade I moved from IC work into tech lead and team lead roles, in Brazil and with global teams. I spent time at a growing fintech, then at a maritime operations platform where I eventually took on product management too. Today I'm a Senior Product Engineer: still close to the code, still involved in what we build and why.

The systems I trust are the boring ones in production. Clear boundaries, workflows you can follow, decisions you can explain to an engineer and to whoever runs the business. I prefer fewer moving parts and releases that work with real operational data, not a polished demo. When we add AI, it should stay on the customer's side, keep people in the loop, and remove tedious work. It should not be making demurrage or chartering calls for you.

I usually start with how things actually run: who touches the data, what fails on a bad day, what done means for the business. Then we shape the architecture, cut work into pieces we can ship, and make sure someone owns it after I step back. Reviewing a design, pairing on an integration, helping a distributed team get unstuck: the point is the same. Something shipped that you can point to.