The story behind the CV.

01 · roots

My degree is in economics, not computer science.

I studied Economics from 2016 to 2020. Nothing technical about it, and not the usual route into cloud engineering. What I took from it was how markets behave under pressure, and how often small details decide the outcome. That turned out to matter more than I expected.

I still look at infrastructure the way I learned to look at markets: cost and risk together, with resilience close behind. The vocabulary changed, but the instincts didn't.

02 · builder

Running my own platform showed me what I enjoyed most.

From 2018 to 2021 I ran my own e-commerce platform. I had to learn everything myself: frontend, backend logic, payment integrations and shipping APIs. I learned enough to ship features, and enough to fix them when they broke.

Over time my attention kept drifting away from the user interface and toward what sat underneath it: DNS routing, CDN configuration, and tuning Cloudflare so the site held up under load. That was the part I wanted to go deeper on.

When checkout breaks at 2 a.m. and customers are waiting, you stop guessing and start measuring. I've kept that habit in every infrastructure decision since.

03 · the pivot

I chose infrastructure over development, on purpose.

By 2022 I knew where I was heading. I could write frontend and backend code, but I wanted my career in cloud infrastructure, with development as a skill I keep in reserve.

So I closed the platform and gave a full year to cloud engineering. Six months went to an AWS bootcamp and hands-on labs on AWS and Azure. Evenings went to building environments and breaking them on purpose to see how they failed. I stayed with each topic, from networking through IAM to platform administration, until it felt natural rather than like exam material.

I finished with three certifications: AWS Cloud Practitioner, Azure Fundamentals and Azure Administrator. They mattered less than the direction they gave me, and knowing I'd picked the right one.

04 · today

Today: cloud infrastructure for enterprise AWS customers.

Since May 2026 I've been on contract with a Fortune Global 500 technology consulting firm, doing Cloud & DevOps engineering on a large enterprise project. The details are confidential.

Alongside that, since 2023 I've been a Cloud DevOps Engineer at an Amazon Advanced Partner in Italy. There I've worked with more than 30 enterprise customers on cloud migrations, cross-platform integrations, and on-premise systems moving to the cloud for the first time.

Day to day, I define environments in code with Terraform and Terragrunt, so they can be reviewed and rebuilt like software, and they run under 99.9% uptime SLAs. I build CI/CD pipelines that release software automatically, and I automate repetitive tasks that used to cost the team hours every week. My certifications (AWS DevOps Professional, CKA, CKAD, Terraform Associate) back this up, but I'd rather point to the systems still running in production.