Open to senior backend and full-stack roles · Munich · hybrid/remote
Senior software engineer with 11+ years across backend, web, and mobile products. My focus is APIs, data flows, and maintainable cloud architecture with TypeScript/Node.js, Python, PostgreSQL, and AWS.
Ticketing and event operations, a 2026 mobile-commerce platform, live IoT telemetry, and regulated clinical data — what I owned, what shipped, and the trade-offs behind it.
Production
Delivered core mobile-commerce journeys end to end across German and Austrian markets, from customer state and cart logic to checkout, CMS, and loyalty flows.
Senior Software Engineer
Open case study
Production
Shipped a production event platform where organizers could publish ticket shops, track sales, and run entry from the same system across web and mobile.
Full-Stack Engineer
Open case study
Production
Replaced 30-second refreshes with live telemetry and explicit stale-state handling, so operators could act on the dashboard instead of walking to the machine.
Lead Full-Stack Engineer
Open case study
Production
Replaced manual spreadsheet analysis with reproducible pipelines and audit-ready reports that clinicians could regenerate and defend later.
Backend & Data Engineer
Open case study
Production
Gave the product a data model that could represent partnered users, group consent, and matching rules without piling on special cases.
Full-Stack Engineer
Open case study
Kept late-wave simulation smooth by removing GC churn and bounding the work inside the hottest update paths.
Gameplay & Systems Programmer
Open case studyThree production decisions — the constraint, the alternative I rejected, and the consequence of the choice.
When a cart behaves differently by market, the rule belongs in the API, not in whichever screen happens to need it first.
Kept business rules in shared APIs and query orchestration rather than duplicating market logic in the app, which made releases safer and behavior easier to trace.
Mobile Commerce Platform
Read the full decisionTicket phases, scanner validation, and payouts are not three features; they are one inventory system seen from three different screens.
Kept ticket phases, admission validation, and organizer state in Rails domain models and APIs rather than duplicating business rules separately in React and Flutter clients.
NIGHTOWL
Read the full decisionOperators tolerate a dashboard that admits it is behind. They stop trusting one that silently shows old numbers as though they were current.
Kept D3 for scales and time-axis math, but moved chart rendering from SVG to canvas to preserve 60fps on low-power tablets.
IoT Telemetry Platform
Read the full decisionMarco Casanova
Senior Backend & Full-Stack Engineer
I am Marco Casanova, a senior software engineer based in Munich. For more than eleven years I have built production software, mostly systems where data, reliability, and clear interfaces matter. I take work from technical discovery through implementation and operations.
Worked with
Open to senior backend and full-stack roles; selective consulting is still possible.
Notes on performance, runtime internals, and the trade-offs behind the frameworks we lean on.
A practical look at where React spends time, why re-renders get expensive, and when optimisation is worth the complexity.
How Node.js handles thousands of concurrent connections on a single thread, the phases callbacks actually run in, and the mistakes that stall the whole process.
The vulnerability classes that actually cause breaches, why they survive code review, and the structural defences that make them hard to reintroduce.
Selected teams
Depth of use is in the case studies — every choice there has a trade-off attached.