It started at a call center desk, answering phones. Not as an engineer, not as a leader, just someone learning, one step at a time, how a large organization actually works.
Each position taught me something valuable:
-
Customer support taught me to listen to the person feeling the pain before I ever touched the system causing it.
-
Operations taught me that a process nobody can repeat isn’t a process, it’s a liability waiting for its next incident.
-
Systems administration taught me that infrastructure is invisible until it fails, and by then it’s already expensive.
-
Software engineering taught me to build the thing that solves the problem, not the thing that’s interesting to build.
-
Architecture taught me that today’s shortcut is next year’s outage and someone else’s 2am page.
-
Leadership taught me that none of the above matters if the team can’t execute on it without me in the room.
Twenty years later, I’ve carried that same progression across telecommunications, fintech, logistics, AI, e-commerce, and enterprise software; building backend platforms, cloud infrastructure, developer tooling, integrations, APIs, microservices, internal platforms, automation systems, and the engineering organizations that keep all of it running.
I still measure the work the same way I did at that call center desk, by answering the question: did it solve a real problem?
That’s what I bring into every engagement, deep technical expertise, applied with business judgment.