Product architecture
Turn ambiguous requirements into technical direction, clear boundaries and delivery plans.
Software engineer working across product, architecture and complex backend systems.
Valencia, Spain
Turn ambiguous requirements into technical direction, clear boundaries and delivery plans.
Design and evolve APIs, services and data flows that remain understandable as products grow.
Improve observability, failure handling and the parts of a system that cause trouble in production.
Use LLMs and automation when they remove real work or unlock a useful product capability.
A healthcare operations team relied on spreadsheets and email for a business-critical workflow. The key was turning that informal process into a product with clear data, architectural and operational boundaries that could evolve safely.
A consent-management browser extension had to evolve under CSP, storage and cross-browser constraints. The key was separating product architecture from platform limitations so the system could keep changing without stalling delivery.
Customer issues in a high-usage crawling product often came from inconsistent execution and limited observability rather than isolated bugs. The focus became making failures visible and execution predictable enough for the product to evolve safely.
Leading the technical evolution of a web crawling product used daily by thousands of customers.
Led a five-person team evolving a consent-management browser extension into a more robust product prepared for cross-browser expansion.
Designed and developed a healthcare automation platform that replaced spreadsheet- and email-based operational workflows.
Contributed to the evolution of a monolithic platform into roughly ten services within a cross-functional engineering team.
Developed web applications and technical tools for national and European R&D projects across AI, IoT and blockchain.
Based in Valencia.
Usually somewhere around a piano
or underwater.