Skip to content

Luca Atella — Tech Lead, Backend & Platform Engineer

I design and build backends, APIs, and software platforms for products that need to remain understandable, verifiable, and maintainable over time.

At Vemar, from April 2021 to October 2024, I worked as Tech Lead with continuous technical coordination responsibility for a 4-person team. In that context, I personally designed and implemented the infrastructure for 80 trackers and developed the framework on which delis.app is based.

My work tends to focus on boundaries: where application logic ends, where infrastructure begins, how components and services communicate, which dependencies may change, and what effects a change can have on the whole system.

I am based in Basilicata, Italy, and I am open to remote or hybrid collaborations where backend engineering, platform engineering, AWS deployment, runtime validation, or integration-heavy systems are central to the work.

LinkedIn · GitHub · Email

Main Evidence

  • Tech Lead at Vemar: continuous technical coordination of a 4-person team.
  • Real-Time Fleet Telemetry Backend: infrastructure for 80 trackers, personally designed and implemented with socket communication, CAN bus data, persistence, and REST APIs.
  • Unified Backend for Heterogeneous Data Sources: framework developed at Vemar and used as the foundation for delis.app, with separated integrations and explicit contracts.
  • Cloud-Portable Fleet Management Platform: Fleet Management System used by Studio Lambda for vehicle turnover management for 50 employees, deployed on AWS.
  • ImportSpy: open-source policy-as-code admission for Python, with static preflight and structured decisions before explicit execution.
  • Agenzia delle Entrate applications: Java runtime isolation and coexistence of legacy desktop tools in an accounting firm.

What I Work On

  • Backend architecture and platform design
  • Modular and plugin-based systems
  • Runtime validation and contract enforcement
  • Cloud-portable backend architectures
  • AWS serverless and managed services
  • Integration-heavy backends, APIs, protocols and devices
  • IoT, telemetry, edge/cloud computing
  • Diagnosis of incompatibilities and dependency isolation
  • Geospatial pipelines and 3D terrain model generation

Method

I approach problems from the operational context first: who uses the system, which process it must support, which parts cannot break, and which technical constraints are already present.

From there I move through diagnosis, boundary definition, explicit contracts, implementation, and verification. The same method appears in modular backends, device infrastructure, AWS platforms, and legacy-environment interventions.

The common thread is governing the relationships between components, data, and environments while considering the effects of changes on the whole system.

How to Read This Portfolio

Start from the home page for the positioning, then use case studies as technical evidence.

The most representative examples are:

For a compact professional summary, see the CV. For project or architecture conversations, use Contact.