Curiosity, Architecture, and Decisions That Shape Real Systems
Throughout my career, one question has always accompanied me:
How to transform technology into solutions that actually work in the real world?
This question arose long before titles, roles, or specializations. It was born from curiosity — that genuine restlessness to understand how things work on the inside — and evolved with me, becoming the common thread of my work as an AI & Systems Architect Engineer.
This article is not a technical resume, nor a tool manual. It is a strategic snapshot of my trajectory, the decisions I made, and how I came to view technology as living systems, not just code.
The Context: Technology Beyond Code
From an early age, I had practical contact with technology. While still very young, I was already exploring computers, systems, and structures that sparked more questions than answers. Over time, it became clear to me that writing code was only part of the problem.
The real challenge has always been to understand the whole:
- How systems connect
- How technical decisions impact business
- How to scale without losing control
- How to balance security, cost, and governance
This vision strengthened throughout college, when I already had a foundation in web development, and especially through professional experience in real corporate environments, with legacy systems, budget constraints, and clear business expectations.
Why Artificial Intelligence Crossed My Path
Artificial Intelligence always caught my attention. Since my academic days, it was evident that there was transformative potential there. But from the start, it was clear to me that AI is not magic — and certainly not an end in itself.
What really interested me was not "using AI," but answering questions like:
- Where does AI truly add value?
- What is the real cost of this decision?
- Is the system sustainable 2 or 5 years from now?
- Are we solving a problem or just creating complexity?
It was at this point that my journey began to consolidate: AI always as part of a larger architecture, integrated with products, workflows, data, people, and strategic decisions.
Architecture as the Career Thread
Over more than a decade of work, I have gone through projects in different segments — finance, health, home care, pharmaceutical industry, government systems, and complex corporate environments.
Regardless of the domain, one thing always repeated itself:
Architectural decisions mattered more than the tools chosen.
That's where I learned, in practice, that:
- Reinventing the wheel is not always a good idea
- Scale without governance becomes chaos
- Performance without observability is an illusion
- AI without integration becomes a cost, not a solution
My role became less about "building everything from scratch" and more about orchestrating solutions, evaluating trade-offs, conscious risks, technical limits, and business impact.
Experience Beyond Technology: Business Vision and People
Before consolidating my career in IT, I had a strong background in sales. This experience deeply shaped my way of thinking about systems and products.
It taught me to:
- Understand customer behavior
- Translate needs into practical solutions
- Communicate technology clearly
- Connect technical decisions to perceived value
This combination — technology + business + people — was essential for me to evolve into positions of technical leadership, architecture, and strategic decision-making.
Risks, Continuous Learning, and Technical Maturity
No consistent journey is made without risks. Along the way, I made difficult decisions, learned from mistakes, and refined my way of thinking about architecture.
Learning never stopped. Post-graduations, MBAs, specializations, and international courses always had a clear objective: to broaden the vision, not just accumulate titles.
Today, my work as an AI & Systems Architect Engineer is the result of this sum:
- Practical experience
- Systemic vision
- Focus on architecture
- Awareness of cost, risk, and governance
- Ability to connect technology to strategy
Final Reflection
If there is something I have learned along this trajectory, it is that good systems are not born from fads, but from well-thought-out, contextualized, and sustainable decisions.
AI is powerful, yes. But its true value only appears when it is part of a solid architecture, integrated into the business, and prepared to evolve.
This is the lens through which I continue to view technology — and it is this vision that I share here.
What Comes Next
In the next articles, I will delve into topics such as:
- AI systems architecture in corporate environments
- Real decisions, trade-offs, and conscious risks
- Integrating AI with legacy systems
- Governance, cost, and scalability in modern solutions
If you are interested in architecture, strategy, and systems that work in the real world, stay tuned.
AI & Systems Architect. A new article every 15 days.
Continue this reading in your inbox
Join the newsletter and receive new articles every 15 days on architecture, AI, governance, and the decisions that connect technology to business.