Matteo BocchiaBackend Developer · AI & ML
English
EnglishItalianoFrançaisEspañol
MenuClose

Today.

Two parallel tracks

Work · Since 2024

Backend Developer

Zeratech S.r.l.

Backend services and data workflows for industrial operations.

HTTP/gRPC · Kafka · Helm · Kubernetes

Experience in my CV

Koomy · Since 2023

Co-founder & Backend Engineer

A legal digital-comics platform.

12,000+ registered usersProduct metric · reported by Koomy, Nov 2025 · source

See the product

Earlier chapters

Work, study, and Koomy

These paths overlap. Open any chapter to read more.

Show chapters

  1. Now

    1. Work · Zeratech

      Present

      Zeratech S.r.l.

      Backend Developer

      I work across the path from second-resolution plant readings to backend services in a distributed industrial platform.

      How I work across the data path

      I design and develop HTTP/gRPC services, Kafka workflows and asynchronous workers for second-resolution plant data. I also build Helm environments and troubleshoot routing, service discovery and storage across Kubernetes.

      See the full experience in my CV

    2. Koomy · Product and backend

      Present

      Koomy

      Co-founder & Backend Engineer

      I designed and built the production backend for a legal digital-comics platform in Italy.

      How the idea became a product
      1. I continue to develop and maintain Koomy’s production backend.
      2. Koomy launched publicly. Read the team’s launch story.
      3. My role as Co-founder & Backend Engineer began.
      4. In Kristian Lentino’s public account of the team’s origin, three developers meet at a Burger King and talk about a legal digital-comics platform for Italy. Read the origin story.
      See the Koomy case study

  2. 2019–2024

    1. Work · Co-brains

      Co-brains S.r.l.

      Backend Developer

      In a four-developer team, I built backend software across industrial data and engineering projects.

      For much of 2019–2024, I combined the Co-brains role with Computer Science studies.

      • WorkCo-brains · later in this chapter, working from PoliHub
      • StudiesComputer Science · Milano-Bicocca
      From a small team to PoliHub
      1. Energy dataI built backend and data-processing software for industrial energy monitoring. Its telemetry arrived every second; I worked across MQTT ingestion and MongoDB/PostgreSQL storage.
      2. Connected plantsI also worked on software connecting plant systems to edge and cloud services for live production monitoring.
      3. EngineeringSome projects were closer to engineering and multiphysics software. The variety was part of the role: in a four-developer team, I worked across what each product needed.
      4. Product workThe team delivered cloud document workflows, order management, product configurators and links between production systems and business software. I also contributed to projects in online comparison and social media analytics, and to software work for business associations and industrial manufacturers.
      5. PoliHubLater in this chapter, I worked from PoliHub, alongside many early-stage teams. It gave me a close view of the different problems startups were trying to solve and the software they needed to move forward.
      6. StudiesAt the same time, I was studying Computer Science at Milano-Bicocca. Work and university were parallel parts of these years.
      See the full experience in my CV

    2. Studies · Milano-Bicocca

      M.Sc. in Computer Science

      AI & Software Development · University of Milano-Bicocca

      My thesis asked whether a sales-forecasting model could generalise to municipalities it had never seen.

      Question and method

      I combined sales, daily weather and municipal socioeconomic data, then built a hybrid LSTM–MLP model. I evaluated geographic generalisation by holding out municipalities during training. Sparse sales data limited the evaluation.

      Read the thesis notes

  3. Origin

    1. Prologue · Studies

      Choosing an IT school

      I was curious about science and at home with logic, so I chose an IT technical school. Computer science felt direct: work out the problem, build an answer, then see if it holds up.