Idriss El Ouazzani, between engineering and product

My degree deals with signals, data, electronics and systems where a misunderstood measurement can change the whole conclusion. Programming lets me carry that way of thinking into an interface, API or database that someone can actually use.

That is why I am drawn to healthtech, biomedical informatics and applied AI. Code matters in those fields, but so do the source of the data, its limitations and the person making a decision with it.

I enjoy following the whole product: clarifying the problem, drawing the flow, choosing the architecture and building frontend, backend, authentication, data, integrations and deployment. I usually work with Next.js, React, TypeScript, Node.js, NestJS, PostgreSQL, Prisma and Docker.

The technology list is not the project. What matters is whether the person who was losing time, information or context can now do the work with fewer steps and fewer doubts.

I worked as a waiter and crew member while studying. I saw how quickly a process breaks when demand spikes, information is missing or a tool adds steps at exactly the wrong time.

Orquesta Labs starts from that experience. I do not have to imagine service from the outside, but I still test those observations with the people doing the work before deciding what to build.

AI interests me when it answers a concrete question: which incident comes first, how to organize a plan or what repetitive task can be reduced. Etecnic Plus, first-prize winner at the URV SmAIrt Mobility Hackathon, applied that idea to charging-point maintenance.

We had incidents, available technicians, routes and priorities. Before thinking about a model, we had to understand how those variables affected one another. I try to keep that rule in every AI project.

I want to keep building health tools, SaaS platforms, automation and internal systems that solve a specific piece of work, not just produce a convincing demo.

I am based in Tarragona and can collaborate locally or remotely. I fit best where a challenge needs business context, product decisions and then architecture and code.