I’m building my career around designing and improving software systems. The short version is in my CV, but the longer story is in the projects that shaped how I think about this work.
From my work so far, I have learned that every project starts with its own problem. Many of those problems are exactly the kind I enjoy helping design and build for. Because computing is used across so many industries, it can scale solutions around the world. What makes those systems valuable is understanding the problem at hand and the role software can play in solving it.
My career started at PosAm, where software became a practical industry problem rather than just theory from academia. Since then, I have learned that every serious project comes with its own constraints, trade-offs, and messy reality. Solving those problems and managing that complexity is part of what makes the work interesting to me.
After I moved to the Netherlands, I worked at ASML for a course internship, which taught me another valuable lesson: it is difficult to change a complex system, and choosing what to change and how is as much of a design and change management problem as it is a technical one.
Most interestingly, I took up a research opportunity at TNO, looking into the use of language models for sustainable software engineering. AI has completely transformed the software industry, and getting under the hood to analyze its use for improving software at scale made the work incredibly interesting.
Across these experiences, I keep coming back to the same idea: understand the problem behind the software and help shape systems that are practical, maintainable, and worth using.