
Aldo Lushkja
Architecture, backend engineering, and production ownership
- Domain
- Fintech and digital trust
- Systems
- High-throughput, distributed, cloud-native
- Approach
- Clear boundaries, observability, safe delivery
Senior backend engineer · fintech · Milan
I work across architecture and delivery: shaping service boundaries, building critical backend flows, and operating cloud platforms in regulated environments.

Architecture, backend engineering, and production ownership
Reliable subscription and loyalty flows, with automation that removes repetitive operational work.
02 · Experience
From consulting and legacy systems to digital trust, fintech and platform work.
Software Engineer working on loyalty and subscription ecosystems.
Architecting scalable backend components for subscription lifecycle and loyalty point logic.
Software Developer focused on digital trust systems.
Worked on timestamping flows, CRL management, secure signing infrastructure, and Java 7 to 21 migrations.
Software Engineer delivering logistics and digital identity projects.
Built three-layer solutions with Angular, Java / Spring Boot BFFs and on-premise deployment models.
Software Developer for enterprise clients including SIAE, TIM, Intesa Sanpaolo and Fastweb.
Modernized legacy systems and supported production release cycles for high-stakes environments.
03 · Expertise
I combine system design with hands-on delivery. The goal is not a clever diagram, but a system teams can understand, operate, and change safely.
Clear contracts, authentication, routing, and sensible caching.
Business boundaries, consistency, resilience, and observable behaviour.
Storage and integration patterns matched to real access requirements.
Service design, critical business flows, APIs, concurrency, and performance.
Infrastructure as code, deployment pipelines, observability, and safe releases.
Storage and integration patterns chosen around consistency, access, and operating cost.
Focused automation and AI tooling that reduce toil without hiding system behaviour.
04 · Selected work
A focused selection of public products, automation tools, and technical writing.
Personal site and portfolio infrastructure.
Utility surface for small automation tools and developer workflows.
Writing space for technical notes and architecture decisions.
Public API surface for docs and tooling, built around stability and clear contracts.
05 · About
Engineering matters most to me when it combines sound judgment, shared understanding, and responsibility for what happens after release.
Clear boundaries and explicit trade-offs help teams move faster than clever abstractions.
Delivery includes observability, safe releases, and staying close to real operational behaviour.
Tooling should remove repetitive work while keeping decisions and failure modes visible.
My daughter brings perspective, energy, and purpose to every day.
A lively household with no shortage of interruptions or character.
A long-term discipline built on patience, repetition, and continuous refinement.
06 · Contact
Available for roles and collaborations where backend depth, platform ownership and clean execution matter.
For roles, partnerships, or work that needs strong backend engineering.
Press CMD+K or tap the palette button to jump around, toggle the theme reboot, or launch the easter egg.
npx run-briefing --with=your-problem
// Expected output:
// precise context
// no waste
// a well-structured solution