Senior DevOps, Platform Architect & AI Adoption Lead

Job role

This is the role that defined my approach to engineering. This is the job where I co-own infrastructure end-to-end: Kubernetes on AWS, Terragrunt and OpenTofu for everything, service mesh with Kafka and Knative, CI/CD pipelines that actually made engineers faster instead of just adding ceremony. I designed it so engineers could ship without waiting on ops. Started as Senior DevOps, grew into Platform Architect and AI Adoption Lead. I started as DevOps and a right hand to Lead Platform Engineer, and now it grew up to own the cloud infrastructure, dev experience (internal tools) and platform security.

Ipsos Simstore is where I stopped thinking about what I could build alone and started designing systems that enable engineers to ship with confidence. Today I own the cloud infrastructure strategy, developer experience, and platform reliability across a multi-region, highly available Kubernetes cluster.

I designed and built the service mesh architecture based on Kafka and Knative, enabling event-driven communication with automatic scaling — replacing a monolithic deployment model and cutting deployment times by orders of magnitude. Every piece of infrastructure is defined as code: Terragrunt, and OpenTofu across AWS environments.

As a platform engineer, my focus is developer enablement: CI/CD pipelines, monitoring and observability, security guardrails, and documentation that lets engineers ship independently.

I lead AI adoption effort in tech department — defining guidelines, guardrails, and toolchains (agents, plugins, documentation) for safe and effective AI use. This was internal evangelism: building buy-in, demonstrating value through prototypes, and creating the governance that enables adoption without risk.

I was on-call rotation, monitoring and responding to incidents.

Personal development

This role marks the most significant personal and professional growth of my career. I transitioned from individual contributor solving discrete infrastructure problems, to platform architect designing the systems that multiply team output, to organizational catalyst shaping how an entire engineering organization works with technology. Learning to lead through trust rather than authority, to influence without a reporting line, and to drive change through advocacy and evidence rather than mandates — these are the capabilities that distinguish senior technical leadership and I developed them here.

The platform-building and developer relations dimensions of this role connect directly to who I am as an engineer. Every CI/CD pipeline I designed, every monitoring dashboard I built, every documentation page I wrote lowered the barrier for someone else to ship with confidence. That internal developer relations work — mentoring engineers, translating platform capabilities into team workflows, advocating for developer needs in architecture decisions — revealed that my impact compounds when I focus on enabling others rather than delivering solo. My identity as an engineer shifted here: from "what can I build?" to "how do I grow the people and systems around me?" That shift is Ipsos Simstore's lasting influence on my career.