Experience and projects

Prior professional experience
Experience summary

Supplier integration for a marketplace

Integrating catalogue and order data with external suppliers in a marketplace without its own stock.

Situation

The marketplace needed to onboard suppliers and keep its catalogue, orders and availability up to date.

Role

Product engineering and integration architecture in a marketplace environment.

What needed to be addressed

Poor synchronisation could cause manual work, incorrect stock information and errors that were difficult to trace.

Technical decision

Separate catalogue and order workflows, process them asynchronously and define ownership of operational issues.

Intervention

Designing dropshipping and crossdocking workflows, synchronising catalogue and orders, and integrating supplier APIs.

What the solution supports

The integration supports centralised supplier information and tracking of data exchanges.

Note: Professional experience summary; internal implementation details are omitted.

02 / Inditex

Prior professional experience
Experience summary

Modernising a platform in stages

Evolving interconnected systems with traffic peaks and teams that needed to release changes independently.

Situation

A high-traffic digital platform had to evolve without pausing product delivery.

Role

Backend architecture, domain modeling and incremental modernization.

What needed to be addressed

Replacing the entire system at once would increase risk, while existing dependencies made delivery difficult.

Technical decision

Separate responsibilities gradually, define service contracts and use events where appropriate.

Intervention

Progressive domain separation, hexagonal architecture, Kafka events, asynchronous processing and clear contracts between services.

What the solution supports

Clearer service responsibilities and a basis for releasing changes with fewer dependencies.

Note: Technical description of prior experience, without implying an endorsement by the company.

Prior professional experience
Project-pattern summary

Demand forecasting for inventory planning

Using data and forecasting models to support inventory decisions, with review by the people responsible for operations.

Situation

Operations needed to anticipate demand and review replenishment proposals using accessible information.

Role

Developing data pipelines, integrating models and building review tools.

What needed to be addressed

Incomplete data and manual analysis made it difficult to anticipate needs and understand forecasts.

Technical decision

Connect forecasting models to operational systems and present the information in a review dashboard.

Intervention

Developing a forecasting pipeline connected to operational data, replenishment alerts and a dashboard for human review.

What the solution supports

Forecasts and replenishment proposals available for review before decisions are made.

Note: Impact described as a qualitative signal of the improvement targeted.

04 / Mapfre

Prior professional experience
Project-pattern summary

Automating insurance workflows

Integrating internal workflows to classify requests and track their status.

Situation

Insurance operations involved repeated decisions across systems and actors.

Role

Process automation, backend integration and operational flow design.

What needed to be addressed

Manual routing and dispersed criteria made priority, state and ownership harder to audit.

Technical decision

Use rules, classification and traceable approval flows to make operations more explicit.

Intervention

Rules engine, classification by type and risk, APIs with external systems and an approval flow with traceability.

What the solution supports

Request classification and routing with status tracking.

Note: Business details simplified for confidentiality.

05 / Orange Bank

Prior professional experience
Experience summary

Services for banking operations

Developing financial services where availability, traceability and regulatory requirements shape implementation.

Situation

Regulated banking flows required resilient services around sensitive operations.

Role

Developing banking services, integrating external systems and preparing for production.

What needed to be addressed

Fragile integrations or insufficient monitoring made incident handling and compliance reviews more difficult.

Technical decision

Design services with asynchronous processing, traceability and production security controls.

Intervention

Microservice with asynchronous processing, event sourcing, external network integration, automated tests and observability.

What the solution supports

Operation tracking and traceability to investigate incidents and review system behaviour.

Note: Regulatory requirements and internal details are described at a high level.

06 / Adevinta

Prior professional experience
Experience summary

Verification and payments for a marketplace

Integrating identity verification, payments and issue tracking for transactions between users.

Situation

Marketplace trust depended on identity checks, payments and traceable resolution flows.

Role

Trust engineering, verification, payments and marketplace integration.

What needed to be addressed

Increasing control could add friction, while weak verification could damage safety and conversion.

Technical decision

Organise verification and payments around defined controls and tools for handling issues.

Intervention

Multi-factor verification, document validation, integrated payments, ratings and traceable resolution flows.

What the solution supports

Document verification and transactions supported by controls and operational tracking.

Note: Product details summarized to focus on the engineering pattern.