My career has evolved step by step through the full spectrum of IT — from frontline support to mission-critical data operations, cloud architecture, DevOps and AI foundations. Each stage shaped how I think about technology today.
From support to responsibility
I started in customer-facing support, working directly with users. That experience taught me something fundamental: technology only matters if it helps people solve real problems.
Understanding support calls, user frustration and operational reality gave me a practical lens that still guides my decisions.
Mission-critical data environments
I then spent a decade working with enterprise database systems, operating and maintaining large-scale production environments with 24/7 responsibility.
When you carry production duty for core business data, resilience is not a buzzword — it is operational reality. Downtime is not theoretical. Architecture decisions have consequences. Discipline and recovery matter.
From infrastructure to architecture
As cloud computing matured, I moved into architecture and migration work — helping organizations transition systems into public cloud and hybrid environments.
Later, I worked hands-on in DevOps roles, designing and implementing modern delivery pipelines, containerized environments and scalable infrastructure models.
Eventually, I led cloud architecture initiatives, shaping hybrid and multi-cloud solutions and productizing Kubernetes-based platforms into structured service models.
Hybrid architecture, when done correctly, is not about complexity. It is about placing the right workload in the right environment — balancing cost, control, scalability and sovereignty.
Data & AI: back to fundamentals
Today my focus is on data and AI — but through the lens of everything that came before.
AI is not a standalone capability. It depends on clear data ownership, structured data models, governance and access control, process alignment and resilient architecture.
Without these foundations, AI amplifies confusion instead of value. With them, it becomes transformative.
How I think
I always start with the bigger picture:
- What outcome are we trying to achieve?
- How do processes actually work?
- Where are the risks?
- What creates measurable value?
Only after that comes technology selection.
I favor solutions that scale without unnecessary complexity, avoid fragile vendor lock-in, support sovereign and resilient design, and minimize waste — financially and environmentally.
Sustainability is not a separate initiative. Often the most efficient solution is also the most responsible one — in terms of cost, resources and emissions.
Today
I combine deep operational database experience with cloud and hybrid architecture design, DevOps and Kubernetes-based platforms, data product thinking and AI foundations aligned with real processes.
I work across presales, architectural design and hands-on implementation — helping organizations move from scattered systems to structured capability.