Experience
I had to solve the same problem in every place I worked
A system built for a reality that had stopped existing, and a business that moved on faster than it did. Another industry, the same shape. Again.
Senior Software Engineer
I joined a platform serving millions of users and spent six months on two different kinds of ownership: the technical kind (multitenant features and a performance fix I pushed through as a proper ADR instead of shipping it quietly) and the people kind, mentoring the junior half of the backend team and building the agentic AI tooling that's now part of how we review code.
The platform is a globally distributed enterprise CX product: legacy PHP and vanilla JavaScript running next to a modern .NET stack, the same "make the old and the new talk to each other" problem at a different scale. Working for customers across US and EU jurisdictions meant designing around how their data-protection regimes actually differ, not just checking a compliance box.
Backend Developer → Solution Architect in practice
As a developer at Banco Solidario S.A. I worked on the bank's mobile banking transformation, taking it from a third-party vendor product to an in-house platform used by millions of people. My title stayed developer, but my scope kept growing until I was making architecture calls of my own: I designed the identity and payments architecture, we decoupled the OTP service that had become a critical dependency, and I migrated the payment history off the legacy platform without losing a record. I also owned the design and development of the QR Business module, an extension of the app that lets someone else collect payments on your behalf without holding an account at the bank. From nothing to production, and to more than a hundred thousand users in three months. I implemented TOTP-signed transfers and built APIs and distributed services on .NET, the whole AWS ecosystem, RabbitMQ and asynchronous messaging architectures.
- →Taking second-factor authentication back from a vendor
- →Letting business owners delegate collection to people without bank accounts
- →Migrating payment data out of a system nobody understood
Systems Analyst
The systems team from my previous role spun out into this company, and I went with it. Same problem, different company: integrating satellite systems into an ERP core, and evaluating the vendors on the other side of those integrations. I also got my first look at low-code platforms.
The work had the same shape it had before the spin-out and the core was literally the same one, except that now I was integrating satellite systems into it from the other side of a corporate boundary instead of from the inside.
Trainee → Systems Analyst
My first real system, end to end: a multitenant attendance platform tying biometric terminals across several industrial plants back into the company's HR system. It started as an improvement to the HRMS integration modules already in use, replacing narrower processes with something we owned, that scaled, and that fit an operation spread across the country. Shipped to production while I was still learning what "production" actually meant.
I also built integrations between the production systems and Oracle EBS, working on the systems that carried the business's critical processes. That gap between what the system knew how to do and what the business needed is the one I have been working in ever since.