Aldo Lushkja
Software Engineer · Milan

Hi, I’m Aldo.

I build backend systems that people rely on every day — payments, digital signatures, enterprise platforms — and I stay around after release to make sure they keep working.

Currently at Satispay ↗

Write to meRésumé (PDF)
About

A bit about me

I’ve spent the last eight years building backend systems for payments, digital signatures and large enterprises — first as a consultant, then inside product companies.

What I enjoy most is what happens after release: watching a system under real traffic, understanding why it behaves the way it does, and making it a little calmer every week. That’s why I like to own what I build in production, not just ship it.

More about me →

How I like to work

  1. 01

    Keep it understandable

    Clear boundaries and honest trade-offs help a team move faster than clever abstractions.

  2. 02

    Own what you ship

    Work isn’t done at merge. It’s done when it’s observable, safe to release and quiet in production.

  3. 03

    Automate with intent

    Tooling should remove repetitive work while keeping decisions and failure modes visible.

Away from the keyboard

  • Family

    Dad to a daughter who reminds me every day what actually matters.

  • Home

    Two cats and a dog. Never a quiet moment, never a dull one.

  • Karate

    I practise and teach. Patience, repetition, small improvements — not so different from engineering.

Experience

Where I’ve worked

Eight years across fintech, digital trust and enterprise consulting. Open any role for the full story.

  1. 2025 — present1 yr 1 mo

    SatispayCurrent

    Software Engineer · Milan

    I work on subscriptions and loyalty — building Spring Boot services deployed on AWS and React interfaces for customer-facing flows. My job is making sure nobody is charged twice and no point goes missing.

    The story behind it
    The situation
    Recurring payments were growing fast, and with them the risk of concurrency bugs and of loyalty balances drifting out of sync between services.
    The goal
    Rework how subscriptions and loyalty points are processed so the system stays correct and predictable under peak traffic.
    What I did
    Implemented Spring Boot services on AWS with CQRS separation, transactional outbox via SNS & SQS, and end-to-end idempotent flows connected to React frontends.
    The outcome
    99.99% availability, zero double charges, and 40% lower P99 latency at subscription checkout.

    AWS (SNS & SQS) · Spring Boot · React · Event-driven · Idempotency

  2. 2021 — 20254 yrs 2 mos

    Namirial

    Software Engineer — Digital Trust · Milan / Remote

    Four years on the systems behind legally valid digital signatures and timestamps (RFC 3161) used across Europe — software where “mostly correct” isn’t an option.

    The story behind it
    The situation
    The timestamp verification engine slowed down under load spikes, putting strict eIDAS compliance SLAs at risk.
    The goal
    Modernise the cryptographic pipeline and remove database contention — without ever taking the service offline.
    What I did
    Broke the monolithic bottlenecks into asynchronous event streams, introduced database sharding with no downtime, and tuned the signing threads.
    The outcome
    65% lower P99 verification latency, more than 10 million cryptographic operations a day, 100% audit compliance.

    Cryptography · High-volume pipelines · Database sharding · eIDAS

  3. 2022 — 20252 yrs 10 mos

    Digipax

    Software Architect — Identity & Logistics · Remote

    Alongside Namirial, I designed the authentication layer and backend-for-frontend gateways for a logistics platform running both in the cloud and on customers’ own servers.

    The story behind it
    The situation
    Enterprise logistics customers needed to deploy on-premise or in the cloud, with strict isolation between tenants.
    The goal
    Deliver one backend architecture that handled OAuth2/OIDC token exchange and edge security for every deployment model.
    What I did
    Designed a modular monolith with clear domain boundaries, mTLS at the edge and fully automated infrastructure as code.
    The outcome
    Onboarding a new enterprise tenant went from weeks to hours, and releases stopped being stressful.

    BFF pattern · Multi-tenancy · Modular monolith · OAuth2 / OIDC

  4. 2018 — 20212 yrs 8 mos

    Spindox

    Software Engineer — Enterprise Systems · Milan

    Where I learned the trade: modernising backend systems for large Italian clients such as SIAE, TIM, Intesa Sanpaolo and Fastweb.

    The story behind it
    The situation
    Legacy monoliths at big telecom and banking clients made every release slow and every deploy a risk.
    The goal
    Break the monoliths into services without ever interrupting a 24/7 service.
    What I did
    Migrated step by step with the strangler-fig pattern, added distributed tracing with OpenTelemetry and standardised the CI/CD pipelines.
    The outcome
    Releases went from monthly to daily, and critical rollbacks dropped to zero.

    Microservices migration · OpenTelemetry · CI/CD · Strangler-fig

Projects

Things I’ve built

Side projects where I get to own everything, from the code to the infrastructure.

See all projects →