About Me
Web and software developer based in Italy (Lazio): websites, e-commerce, web apps, mobile apps and interactive products. Remote work across Italy and internationally, with a focus on performance and high-performing solutions.
I'm Matteo Santoro, a web and game developer. I work on the whole product: UI, APIs and server-side services, data, deployment and whatever it takes to hold up in production. Over the years I've worked with startups, from small and mid-sized businesses up to large enterprises and high-profile groups, and on large-scale projects.
I've shipped marketing sites, web apps, mobile apps, B2B dashboards, stores, backends, APIs and interactive or AI-backed products. On delivery I care that the outcome can be exercised and checked for real.
When an estimate is needed, I prefer real numbers, access and observed system behaviour, not guesswork. If something can't be measured yet, I treat it as open risk and we address it before locking hard dates.
Based around Frosinone and Rome. The introductory meeting can be in person nearby if you ask for it, otherwise on a call. From there, work is remote in Italy and abroad.
My Story
Curiosity about how software, networks and games are actually built got me into programming. Then came real deliveries and hours on production stack traces. That's still how I learn.
I've worked across landing pages, mobile apps, web apps, dashboards, e-commerce, advergames and gamification with explicit business goals (leads, retention, data capture). Every engagement showed where software breaks after go-live, and how not to repeat the same failure mode.
I still run side projects when I need to understand a protocol or a new constraint, alongside client work. I'm interested in where web UI, games and data meet without blowing scope past what's needed. Beyond that: honest estimates, code review, post go-live support when we've agreed it.
Discover Services and Projects
Two ways to see how I work: what I offer and what I've already delivered.
Let's talk about your project
Send a couple of lines of context (URL, symptom, numeric goal if any). I'll reply with pointed questions or a rough scope. A call only if it earns its place, not a generic pitch.