whoami

Davide Imola

I'm a Tech Lead at RedCarbon, where I own the technical direction across the platform and build the AI agents that run on it. Before that, ten years of DevOps and platform engineering. What follows is how one turned into the other.

git log --oneline --reverse

5 commits, 2013 to today. The dated version is on /cv.

Portrait of Davide Imola

2013 – 2017

Where it started

During university I built websites for whoever would pay a student, because I wanted to know how the web actually worked and not just how to make a page load. Then an internship at EDALab turned into my first real job: embedded systems in C++ and Qt, and a Qt application I ported to iOS and shipped. Working inside a team taught me what no side project ever could, that readable code is not a nicety but the difference between a codebase that scales and one that breaks you. Clean Code and Clean Architecture landed at exactly the right moment, and they pushed me towards the part of the job nobody was looking after: how software gets built, tested and deployed.

What it left me with

  • C++ / Qt
  • Clean Code
  • Clean Architecture

2017 – 2022

Infrastructure is a product

At ASEM I containerized industrial automation software that had never seen a container and built the pipelines that shipped it. At Milkman Technologies I moved to a last-mile delivery platform, where reliability and observability on AWS were not a nice-to-have: when a delivery fails, someone is waiting at a door. Five years of pipelines, clusters and dashboards taught me that infrastructure is a product whose users are developers, and that every pipeline I built either gave the team back a day a week or quietly took one. It also taught me where I did not want to stop: I was moving a domain around for a living without ever getting to model it.

What it left me with

  • Docker
  • Kubernetes
  • Flux
  • Pulumi
  • GitOps
  • CI/CD
Open Source Day, Florence. This is what 500+ looks like.
Open Source Day, Florence. This is what 500+ looks like.

2019 – 2022

The work after hours

Alongside the day job I kept the infrastructure and the website of Si-Fa, a social cooperative, running until it closed, wrote and delivered the Infrastructure as Code, DevOps and Cloud Security modules of Codemotion's Cloud Engineer path, and moved a fantasy football platform onto Kubernetes for Sport Analytics because the project was fun and they asked. Teaching was the part that changed me: you cannot explain GitOps to a room of forty people without discovering the three things you only thought you understood. It is also where the idea that what you learn you must share stopped being a nice sentence and became the reason I speak at conferences, and then the reason I started organizing them.

What you learn, you must share.

Knowledge shared is not knowledge lost: it's knowledge multiplied.

2022 – 2025

Going deeper, not wider

I joined RedCarbon as a software engineer on a multi-tenant AI cybersecurity platform: Go microservices talking over gRPC, GCP and Kubernetes underneath, Next.js on the product side. This is where Domain-Driven Design landed, and software stopped being a set of instructions and became a language for a domain. Working inside a security company also changed how I read code, mine and everyone else's, because there a bug arrives with an attacker attached to it. By the third year the technical decisions were finding their way to me well before anyone made it official.

What it left me with

  • Go
  • gRPC
  • DDD
  • TDD
  • TypeScript / Next.js

2026 – Present · now

Where it took me

Today I own the technical direction across the platform, from the frontend to the infrastructure, and I build the AI agents that run on top of it, with the AI and security teams alongside me. I still write code every day: the job is technical direction, not stepping back from engineering. The shift changed something I did not expect, though. I care less about my own code and more about the team's trajectory, because if we do not all grow, the company does not either. And the two things I work on now are two sides of one question: AI that does real security work, and security for the code AI writes.

/uses for the hardware and software behind all of it

Off the clock

None of this is part of the story above, which is the point of putting it after it.

  • Football · I play futsal and follow Hellas Verona, home games included.
  • BBQ, low and slow · American-style long cooks, sous vide, and underrated cuts. Favourite: skirt steak. Cheap, flavourful, unbeatable.
  • Video games · RPGs and action-adventure. Loved: Clair Obscur Expedition 33, Baldur's Gate 3, Zelda BotW and TotK. Lifelong Pokémon fan.
  • Pokémon cards · Building the Pokédex in rare and full-art variants. An obsession disguised as a hobby.
  • Tabletop and D&D · Board game collector. Currently playing a campaign, and writing one to DM soon.
  • JuJutsu · Hontai Yōshin-ryū. Yellow belt; orange is the next milestone.
  • Music · Everything from Linkin Park to De André, Eminem to Hans Zimmer. Concerts whenever I can.
  • Travel · I travel to learn. Japan was a dream; I'll go back. Asia draws me most.
  • Film and series · Fantasy and action. Lord of the Rings is untouchable. The occasional anime binge.

Want to talk engineering, community, or collaboration? Get in touch →