Four industries. One discipline: build for what breaks.

Leading the unification of 18+ external payment providers (Stripe, Redsys, Adyen, OpenPay, PlaceToPay and more) into one resilient flow, with database-level idempotency to eliminate duplicate transactions under concurrency.

Designed and built the loyalty program from scratch, and integrated multiple external Property Management Systems (PMS) to keep inventory and bookings in sync across the platform.

Contributed to splitting a legacy monolith into Payments, Loyalty and Inventory services through event storming, and mentors newer developers through onboarding and pair programming.

Worked within a distributed architecture where vehicle sensors sent data to backend services, which exposed it through APIs consumed by the mobile app. Focused on implementing business logic for vehicle status, remote actions and telemetry data.

Though the project was in a maintenance phase, it gave deep exposure to distributed system design, service communication and how domain boundaries emerge in real systems — foundational for the integration work that followed at Neobookings.

Took on a hybrid role combining development, technical decision-making and coordination, working within a legacy system used by farmers and livestock professionals to submit and manage fiscal declarations.

Participated directly in technical and functional requirement definition with stakeholders, and supported junior developers while contributing to solution design — strengthening the ability to navigate ambiguous, multi-stakeholder environments and turn business requirements into shipped technical decisions.

Two-month engagement combining backend development with hands-on Angular work for Catalana Occident, getting exposure to how insurance-sector platforms structure data and workflows between backend services and client-facing interfaces.

Joined the project as an external contractor placed through Tenea Tecnologías, working inside DXC Technology's team on a digital banking dashboard for business clients. After proving his work over several months, DXC brought him on directly as internal staff — continuing on the same project.

Focused on implementing UI components from design specs (JSP-based architecture), integrating frontend logic with backend APIs to display real-time financial data, and reducing friction in key operations — reinforcing how much backend data contracts shape frontend usability.

Worked on thick-client Java Swing interfaces connected directly to the database with no backend layer in between — a different paradigm from the API-first, service-oriented work that came both before and after in his career.

Operated within a Kanban-driven maintenance project, picking up tickets and resolving them independently, which sharpened the ability to work efficiently within tightly scoped, ticket-based workflows.

The starting point of a backend career: as a junior developer discovering the professional world, this is where fundamentals like Spring Boot, Liquibase-managed database migrations, testing tools and agile methodologies were first put into practice on real client work for VGED and Grupo Planeta.

Everything since — from legacy modernization to payment infrastructure — has built on what got picked up here first.