01.1
Cloud architecture
AWS serverless and event-driven platforms, integrations, observability, and operationally clean backend systems.
- Lambda
- SQS
- DynamoDB
- CloudWatch
Italian software engineer · Technical lead · 15+ years
From game systems to cloud systems.
Same mindset, different scale.
I design and ship production software across cloud architecture, backend systems, applied AI, and gameplay engineering.
01
Three areas, connected by the same systems mindset.
01.1
AWS serverless and event-driven platforms, integrations, observability, and operationally clean backend systems.
01.2
LLM assistants, RAG systems, workflow automation, copilots, orchestration, and practical AI tools.
01.3
Gameplay architecture, mobile performance, creative mechanics, production delivery, and technical leadership.
02
A career across interactive and distributed systems.
Current work
Designing cloud and software architectures with AWS, serverless systems, distributed backends, integrations, CI/CD, and observability.
Building applied AI systems with LLMs, RAG, OpenAI APIs, n8n, knowledge bases, and workflow automation.
Rovio Entertainment
Worked on Angry Birds Classic, Angry Birds Seasons, Angry Birds Rio, and Bad Piggies, contributing gameplay systems, core architecture, performance optimization, and technical leadership.
Chestnut Games
Created original mobile games and experimental mechanics, keeping the creative side of software close to the engineering craft.
03
Representative work across AI, cloud, and game development.
BLOOM
Assistants, orchestration, automation, and practical AI workflows for business processes.
AI customer care
Knowledge bases, LLM assistants, operator copilots, ticket triage, and workflow automation.
AWS messaging
Lambda, SQS, SNS, priority queues, multi-channel notifications, and scalable backend workflows.
Bad Piggies
Core architecture and gameplay systems work from the early phases of a physics-driven mobile game production.
04
Tools I use to take systems from design to production.
05
Principles carried from game development into cloud and AI systems.
I like software that remains understandable after launch: clear interfaces, observable behavior, useful defaults, and teams that can operate what they build.
Game development taught me to care about performance, feedback loops, constraints, and user-facing quality. Cloud and AI work use the same instincts at a different scale.
05.1
Clear interfaces and useful defaults make a system easier to use, change, and extend after launch.
05.2
Logs, metrics, and traces should make system behavior visible when it matters: in production.
05.3
Architecture should remain clear enough for teams to understand and operate what they build.
05.4
Performance, feedback loops, constraints, and user-facing quality are part of the engineering work.
06
Open to cloud architecture, backend engineering, applied AI, and technical consulting.
06.1
For project inquiries and professional collaboration, email is the most direct channel.