About me

Trusting someone with the success of your project is no small ask. Before diving into technical details and architectural diagrams, I believe it’s important to understand the person and philosophy behind the work. This post is a brief introduction to my background, approach, and how I think about solving problems both in technology and beyond.

How this started

My fascination with technology began with robotics. Watching industrial robots build products in perfect synchronicity was mesmerizing, like a beautiful dance of precision and power. However, what truly captivated me was everything happening behind the scenes: the meticulous floor planning, product design optimized for manufacturing, and the deep understanding of each system's capabilities and limitations.

That world taught me the importance of designing for the unexpected. This includes planning for wear and tear, breakdowns, and human safety. Today, implementing complex digital systems is about mimicking that same holistic approach. An autonomous, self-running cloud service should be as thoughtfully designed as a physical assembly line, with a focus on resilience, efficiency, and quality.

From data work to architecture

With a degree in Robotics and a master's in Autonomous Systems Engineering, I began my career focused on automation and analytics. I worked on identifying areas where technology could have the biggest impact, which led me deeper into the world of data. As a data engineer, I built end-to-end pipelines to handle data at scale. Working with user data, I learned to design systems that are efficient, secure, and compliant with regulations like GDPR.

However, I realized that many data products are flawed from the start. A purely technical solution isn't enough. I saw the need to engage with stakeholders early in the planning phases, where critical decisions are made. This shift brought me closer to the business side, ensuring the systems I build solve fundamental business problems. Over time, this approach naturally led me to cloud architecture.

What this looks like in practice

Being a Cloud Architect is about translating business goals, user needs, and compliance constraints into secure, scalable, and cost-effective technical solutions.

I’ve worked on projects across verticals like e-commerce, telecommunications, and green energy. One example involved designing a GDPR-compliant analytics data collection platform. Balancing the business's need for data, the constraints of the existing tech stack, dependencies on integrated tools, strict legal requirements, and the technical challenges of implementation made this a complex but rewarding project. It required thoughtful trade-offs at every step and ensuring that every component, from infrastructure to business logic, aligned with the larger strategic goals.

My goal isn’t just to design architectures but to pioneer patterns that empower teams, mentor junior members, and provide the strategic guidance needed to bring visions to life.

Since my time at Denmark’s leading data analytics agency, I’ve focused on building AI systems that contribute to the green transition. This is a topic I’m deeply passionate about. Like many other domains I’ve worked in, this requires balancing technical challenges, business needs, compliance requirements, and paying close attention to the ever-evolving landscape of energy markets.

How I work

My professional philosophy is built on a few core principles:

• Look beyond the code: I believe in understanding the business context. This means not just addressing the immediate need, but also considering the broader strategy and first principles driving it.
• Build for the future: I design systems that are scalable, resilient, and adaptable to changing needs.
• Empower teams: I focus on clear documentation and mentorship to ensure teams can confidently own and evolve the solutions we build. This includes both technical teams and broader business stakeholders.
• Practical innovation: I ground my work in proven technologies while adopting cutting-edge solutions when they offer the best outcomes. This ensures systems are robust and maintainable.

My primary toolkit includes Google Cloud Platform (GCP). I write most code in Python and TypeScript/JavaScript, build infrastructure as code with Terraform, and use GitHub Actions and Cloud Build for CI/CD. I leverage tools like BigQuery, Cloud Run, and Pub/Sub to create efficient, event-driven architectures.

I’m a double-certified Google Cloud Architect and Data Engineer.

Outside work

When I’m not designing systems, you’ll often find me climbing. I love the physical and mental challenge of mapping out a route on a seemingly impossible wall. Figuring out how to use small edges to move upwards, sometimes upside down or over water, is a different kind of problem-solving. It requires the same mix of planning, adaptability, and focus.

Work with me

If you are looking for help building and maintining reliable data and AI systems, get in touch.

If you're interested in discussing AI, data engineering, or cloud architecture, or simply want to exchange ideas about technology’s next frontier, I’d love to connect. In the coming weeks, I’ll share more in-depth articles on specific technical topics.

Until then, let’s explore how we can build smarter systems together.