Skip to content

About

I am a Tech Lead and Backend/Platform Engineer. I design and build software for systems that need to work in real operational contexts, not only prove an idea.

At Vemar, I coordinated a 4-person technical team, personally designed and implemented the infrastructure for 80 trackers, and developed the framework on which delis.app is based. In other contexts, I worked on a fleet management platform used by Studio Lambda, isolated runtimes for Agenzia delle Entrate desktop applications, and open-source tooling such as ImportSpy.

I care about the point where code meets its environment: data, services, protocols, runtimes, deployment, dependencies, and the people who will maintain the system after release.

How I Approach Problems

I start from the context: which process must be supported, which constraints already exist, which parts cannot break, and which information is confirmed.

Then I work through diagnosis and boundaries:

  • separating application logic, persistence, and infrastructure when the system needs to last;
  • making contracts and expectations between modules explicit;
  • isolating dependencies when multiple runtimes need to coexist;
  • designing APIs and adapters with maintainability in mind;
  • verifying the effects of changes on the whole environment, not only on the modified point.

This approach appears across different projects: the telemetry backend for 80 trackers, the framework behind delis.app, the Studio Lambda platform deployed on AWS, and Windows environments with legacy desktop applications.

What I Am Looking For

I am interested in opportunities where direct engineering, architecture, and technical responsibility matter:

  • Python backends and APIs;
  • modular and plugin-based systems;
  • cloud platforms and AWS;
  • integrations with devices, protocols, or third-party software;
  • runtime governance and contract validation;
  • incompatibility diagnosis and maintainable evolution.

I am from Basilicata, Italy, and I am open to remote or hybrid collaborations.

Why This Portfolio Exists

This portfolio is not a list of technologies. It is meant to show what I built, which responsibilities I had, which technical decisions I made, and which limits are declared.

Each case study tries to distinguish observed facts, personal contribution, design goals, and architectural generalizations.