Full Stack Engineer · Bergamo, Italy
Ion Utale.
12 years building web applications, backend systems, and cloud infrastructure — most recently leading e-commerce replatforming at Gucci.
About
I'm a software engineer based in Bergamo, Italy. I've been writing production code since 2013 — starting with web and Java apps at Baker Hughes GE, picking up iOS development at Telepass and Ducati, then settling into full-stack and cloud engineering at Gucci, where I've been for the past six years.
Right now I'm a tech lead on the e-commerce replatforming at Gucci — taking a monolith apart and rebuilding it as microservices on AWS, with Terraform for infra, Jenkins for CI, and Next.js on the front end. Earlier at Gucci I was the integration engineer connecting their platforms via MuleSoft, Kubernetes, and the Elastic Stack.
I like systems that are observable, easy to deploy, and don't surprise you on a Friday.
Experience
Apr 2021 — Present
Gucci
Software Engineer · DevOps · Tech Lead
Leading replatforming of Gucci e-commerce from a monolithic architecture to microservices. Responsible for infrastructure-as-code with Terraform, CI/CD with Jenkins, and front-end delivery with Next.js and TypeScript.
Feb 2018 — Apr 2021
Gucci
Software Engineer · Integration Specialist
Built and monitored microservice integrations for a high-end fashion e-commerce platform. Handled messaging with AWS SNS/SQS, observability with the Elastic Stack, and deployment with Kubernetes.
Jan 2018
Ducati
Mobile Software Engineer
Built Ducati Youtech, an iOS app used by mechanics to manage repair tickets at Ducati service centres.
Oct — Dec 2017
Telepass
Mobile Software Engineer
Contributed to TelepassPay, an iOS app for tolls, parking, and mobility payments across Europe.
Oct 2013 — Oct 2017
Baker Hughes GE
Junior Software Engineer
Developed internal web applications for turbine and compressor manufacturing operations.
Skills
Frontend
Backend
DevOps
Database
Mobile
Suggested Apps & Tools
A few utilities worth keeping around.
These are practical tools I reach for regularly because they remove friction from debugging, monitoring, and managing runtimes.
Let's work together.
I'm open to conversations about interesting problems. If you have something in mind or just want to say hi, feel free to reach out on LinkedIn.