Building backend systems, now with a focus on AI.
I'm a Backend Engineer with 7+ years building systems in e-commerce, banking, and payments. Now at Mercadona Tech. Focused on platform reliability and on the engineering practices that scale with the team.
Tools that survived production.
A senior engineer who treats reliability as a feature.
I like doing things properly. I care about documenting work, working closely with business and design, and proposing improvements when I see a better way forward. I stay involved across the full lifecycle of the software, because I like owning what I build and having real impact on the outcome.
I want code that is easy to read, easy to maintain, and easy to adapt without a meeting. I care a lot about testing too, but not just for coverage. I want tests that give real confidence and make change safe. I try to apply good practices consistently, but I also stay pragmatic and adaptable when the situation needs it. I especially like working on distributed systems, event-driven architectures, and systems that need to stay reliable as they grow.
Systems worth sharing about.
Open-source projects with the design decisions, the trade-offs, and the run-time numbers written out — not the resume version.
Fakes vs Mocks
When do you reach for a fake instead of a mock? Kotlin/Spring Boot project mapping the decision across five stages of growing complexity.
Notes on systems, performance, and engineering culture.
Long-form posts on the parts of backend work that don't fit in a PR description — the design decisions, the operational habits, and the small things that decide if a system survives its first launch year.
I'm currently focused on my work at Mercadona Tech, so I'm not looking to change roles.
But I'm always up for a good conversation about backend systems, reliability, or how teams build and run software in practice. And if something interesting comes out of that, even better.
I read everything, just can't promise I'll reply to generic messages.