The story behind the CV.

01 · roots

I started a long way from a data center.

My background is Economics. A straight degree, nothing technical about it, and not the obvious route into cloud engineering. Four years of studying how markets move under pressure, and how the smaller details usually end up deciding the outcome. That mattered more later than I expected at the time.

I still think about infrastructure the way I was trained to think about markets: cost and risk in the same breath, resilience never far behind. Different vocabulary. Same instincts.

02 · builder

Running my own platform taught me what I actually cared about.

From 2018 to 2021 I founded and ran my own e-commerce platform. To make it work I had to learn everything myself: frontend, backend logic, payment integrations, shipping APIs. Enough to ship features. Enough to fix bugs at midnight when something broke.

The more I built, the more I noticed where my attention kept drifting: away from the UI, toward what sat underneath. DNS routing and CDN configuration, tuning a Cloudflare setup so it didn't buckle under load. That was the part I actually wanted to go deeper on.

When checkout breaks at 2 a.m. and customers are waiting, you stop theorizing and start measuring. That habit followed me out of e-commerce and into every infrastructure decision I have made since.

03 · the pivot

I chose infrastructure over development. On purpose.

By 2022 the picture was clear. I could write code, frontend and backend both, but the cloud infrastructure layer was where I wanted to build a career. Infrastructure as the main job. Development as a backup skill.

So I made the call: closed the platform and cleared my schedule for a full year of cloud engineering. Six months of it went to an AWS bootcamp and hands-on labs across AWS and Azure. The rest went to evenings building environments and then breaking them on purpose, to see how they failed. I stuck with each topic, from networking through IAM to platform administration, until it felt like second nature rather than exam material.

I came out of it certified in AWS Cloud Practitioner and Azure Fundamentals, plus Azure Administrator. What mattered more than the badges was the direction it gave me, and knowing I'd picked the right one.

04 · today

Now I build cloud infrastructure that holds.

Since May 2026 I've been on contract with a Fortune Global 500 technology consulting firm, doing Cloud & DevOps engineering on a large-scale enterprise project. I can't go into specifics, that part stays confidential.

That runs alongside work I've been doing since 2023 as a Cloud & DevOps Engineer at an Amazon Advanced Partner in Italy, working across 30+ enterprise customers. Migrations that couldn't afford to stumble, plus cross-platform integration work and on-premise systems making their first move to the cloud.

Day to day that means Terraform and Terragrunt for environments held to 99.9% uptime SLAs, plus CI/CD pipelines that don't need babysitting. Manual work used to eat hours every week. Automation handles that now. The certifications (AWS DevOps Professional, CKA, CKAD, Terraform Associate) back that up, but so do the production systems still running without me watching them.