01
Live systems
Feature work and support on platforms where every change has operational impact.
Projects
Cases where the technical work is visible
These cases show the concrete zones where I have worked: production, checkout, pricing, stock, integrations, support, and incident investigation.
What to look for in each case
What you will find
The value is not the broad narrative, but which system area was at stake, which backend decision I made, and what technical signal each case leaves behind.
- Which part of the system was at stake
- What I did with Java, Spring, SAP Commerce Cloud, SQL, or APIs
- What it shows about analysis, support, integrations, or delivery
Case map
Where the technical work is visible
Each case combines a system area, a backend decision, and a concrete way to protect delivery.
02
Business flows
Checkout, pricing, stock, and product logic connected to real business needs.
03
Technical investigation
Symptoms, logs, SQL, and contrasted hypotheses leading to actionable causes.
04
Safe delivery
Local testing, standard review, and validation before handing work to QA.
Real cases
Problem, contribution, and backend signal
Each case keeps the problem, backend contribution, and technical signal visible enough to evaluate quickly.
JavaSpringSAP Commerce Cloud
Stratesys · CaixaBank Tech · 2025
BuildingCenter: production backend on SAP Commerce Cloud
Context
E-commerce and service platform with production support, complex business logic, and direct client visibility
Problem
Keeping a business-critical platform stable while shipping backend changes and investigating production issues with clear functional context.
What I did
I worked across backend features, technical analysis, incident ownership, and collaboration with client, QA, and functional teams to keep delivery and stability moving together.
Outcome
The platform could continue evolving with safer impact analysis and a more structured response to incidents.
JavaSpringSAP Commerce CloudSQLFlexibleSearch
Backend signal
ProductionIntegrationsSQL
JavaSpringSAP Commerce Cloud
Minsait · Claro Perú · 2024
Claro Perú: backend work across checkout, pricing, and stock
Context
B2B telco e-commerce with business-critical standard flows
Problem
Implementing changes in checkout, pricing, stock, and integrations without degrading baseline platform behavior.
What I did
I worked on backend customizations tied to core commerce flows and integrations, strengthening both my execution capacity and my judgment around when and how to extend the platform standard.
Outcome
Core flows kept a stable baseline while specific B2B business needs were incorporated.
JavaSpringSAP Commerce CloudIntegration ObjectsFlexibleSearch
Backend signal
CheckoutPricingIntegrations
JavaSpringSAP Commerce Cloud
Accenture · Airbus · 2023
Airbus: backend foundation in a B2B SAP and SAP Commerce project
Context
Greenfield B2B project in a structured and demanding environment
Problem
Contributing to a project being built from scratch while learning fast enough to deliver inside a demanding context.
What I did
I supported backend development and SAP-side implementation work, gaining the technical base that later helped me grow into more complex backend, support, and production-facing responsibilities.
Outcome
I built the technical and domain foundation that later enabled me to take on more complex backend responsibilities.
JavaSpringSAP Commerce CloudSAP ABAPB2B Commerce
Backend signal
ProductionGreenfield