Technical Lead at IRISBOND · Bidasoa, Gipuzkoa / France

Uraitz Olaizola

I lead IRISBOND’s accessible-applications team and agentic AI systems that build software with me. Twenty years of code, product and leadership.

Looking for my next chapter as CTO, Head of Development or Agentic AI Lead.

Scroll

Defining moments

Five moments that explain how I work.

From the first change I led without a title to two physical products manufactured in seven months. Always the same sequence: detect, propose, prove it in the product, then scale.

01
IRISBOND · 2022—today

Two physical products in seven months, without being a designer.

I took over Product Design temporarily with a fixed brief: two accessible products ready for manufacturing in seven months. It wasn’t my turf; I had to understand commercial and user needs, turn them into decisions, and keep applications, hardware and accessibility aligned.

Read the case →
2products manufactured
and on sale, on time
02
Ibermática · 2019—2021

A full team and an architecture from scratch.

I led a development team of four engineers and defined the architecture of Barcelona City Council’s mobility app, coordinating the mobile side with the REST API team in a demanding environment.

See it in my career →
4engineers reporting to me
and the product architecture
03
Enagora · 2020—2022

Leading teams that weren’t mine.

From my own company I delivered projects for consultancies while leading the consultancy’s own teams: defining scope, coordinating and delivering with people who didn’t report to me, where authority had to be earned on every decision.

See it in my career →
10+projects delivered
for mid-sized and large companies
04
Venta Peio · 2013—2018

From 18 hours to 5: the first mobile stocktake.

I started on mobile in the early days of Xamarin, when hardly anyone was betting on it. We automated the company’s stocktake with Android and iOS apps integrated with internal data: 7 hours in the first iteration, around 5 in the following ones.

See it in my career →
18→5hstocktake duration,
iteration by iteration
05
Lander · 2005

The first change I led came without a title.

The railway simulators were trying to run, in real time, 3D environments built for renderings. They didn’t perform and nobody questioned the process. I proposed changing it and proved it myself, integrating the first optimised environments into the real simulator, not a separate prototype.

See it in my career →
1method adopted by the company
and a brand-new 3D department

Full career →   Personal projects →

How I work

Leading agents the way you lead a team.

Architecture, acceptance criteria and review are mine. Execution is split among agents with defined roles and a pipeline that verifies it.

  1. Architecture first; ship every week.
  2. I review code and go deep when the problem calls for it.
  3. No green tests, no delivery.
  4. Hard decisions are made with product, support and hardware at the same table.
  5. Agents execute; judgement and accountability are mine.
  1. HumanTechnical direction

    Architecture, system boundaries, acceptance criteria and final review.

  2. Agent · Claude DesignDesign

    Proposes the interface; corrected by hand wherever usability demands it.

  3. Agent · OpenClawVision and continuity

    Keeps the project’s global context across sessions.

  4. Agent · Claude CodeImplementation

    Most of the .NET MAUI code for iOS and Android.

  5. Verification100+ xUnit tests

    Written by the agents, demanded by the lead.

  6. DeliveryJenkins → TestFlight / Play

    Automatic distribution to the test channels.

That’s how Momentuan was rewritten in a week, and how Enagora’s editorial system publishes every day .

Contact

If my path fits what you’re building, let’s talk.

I’m drawn to problems that mix technology, product, people and hard decisions.