From Developer to Technology Leader: Lessons Across Telecom, PropTech, Fintech, and eCommerce
What two decades and several industries taught me about the shift from writing code to leading the work.
I started as an engineer. These days the most valuable thing I do barely touches code. The road from one to the other ran through a handful of very different industries, and each of them taught me a different piece of the same lesson.
Telecom taught me adoption is not a technical problem
At Smart, being part of the mobile internet push, including Facebook Piso, showed me that getting people to actually use something is a question of product, partnerships, and price long before it is a question of engineering. You can build the best thing in the country and it means nothing if people will not or cannot pick it up. That reframed how I have thought about every product since.
PropTech taught me scaling is a people problem
At Hoppler, helping build a real estate platform from almost nothing taught me that growing a technical organization is mostly about people, clarity, and process. The code is what everyone talks about. The team and the system you build around it are what actually decide whether you make it to the next stage.
Fintech taught me what discipline buys you
At Finastra, running distributed mobile banking delivery taught me governance and stakeholder management, and the specific kind of discipline that lets a large team ship reliably with real compliance pressure overhead. I used to think structure and freedom were opposites. At that scale, structure is the thing that makes the freedom safe to give.
eCommerce taught me operations are the product
Running technical operations for an eCommerce business taught me that stability and small operational wins compound in a way big rewrites rarely do. It is also where I got clear about AI: it earns its keep as a multiplier on operations that already work, not as a rescue for ones that do not.
What stayed constant
Underneath all of it the shift was always the same. I stopped trying to maximize my own output and started trying to build the conditions where teams, systems, and products could perform. Understand the business and the people first, and the technology tends to follow.
If you are somewhere on this path yourself, the hardest lesson is also the simplest one. Stop measuring yourself by what you can build, and start measuring yourself by what you make possible for everyone around you.
Written by Ronald Patrick G. Wenceslao — Engineering & Technology Leader. Open to leadership, advisory, and AI-enabled operations conversations.