Resources list
Outsystems
Interview

Interview with Elyes Gazbour, Outsystems solution architect

Team Rokodo
5 min
-
13.02.2026
What is your current role, and how do you contribute to projects?

I am currently a Solution Architect specialized in the Outsystems platform.
My role is cross-functional: I am involved both in pre-sales, to understand client needs, propose suitable solutions, estimate projects, and deliver POCs or POVs when necessary; and during the project phase, where I design application architectures, lead technical teams, and ensure delivery quality.

I am also responsible for strategic monitoring of Low-code trends and the evolution of the Outsystems platform, in order to anticipate needs and guide technological choices.

Finally, I regularly work as a certified Outsystems trainer, both internally and to support the upskilling of client teams.

Which clients have you worked with?

I have had the opportunity to work across various sectors such as banking, insurance, urban development, and the public sector.

Among the clients were both large enterprises and SMEs.
Projects often focused on the digitalization of complex business processes or the development of high-impact user portals.

Can you summarize your professional background in a few lines?

I started as an ITSM Consultant before specializing in application architecture.

I discovered Low-code a few years ago and was quickly drawn to its potential.

Since then, I have trained on Outsystems and progressed into technical leadership and architecture roles, while still keeping hands-on involvement in development.

My background combines technical expertise, consulting, pre-sales, training, and team enablement.

In your view, what are the specific characteristics of Low-code projects compared to more traditional development projects?

The first difference is delivery speed: things can move very fast, but this requires strong discipline to avoid compromising quality or maintainability.

Second, Low-code requires genuine collaboration between business and tech teams.
There is less emphasis on fixed specifications and more on an iterative approach.

Finally, Low-code—especially with Outsystems—imposes a new way of thinking about architecture, as you work within a framework that is both highly structured and very powerful.

What do you particularly appreciate about Low-code?

What I like is the ability to turn ideas into concrete applications very quickly.
You see results fast, and users are often involved early, which completely changes project dynamics.

But what I find truly powerful is also the reduction of technical complexity: Low-code, and Outsystems in particular, provides a set of tools, reusable components, and connectors that allow teams to focus on business value, while staying aligned with technological trends and innovations.

It is a real agility enabler for teams.