00Profile

Gaizka JiménezSoftware developerwith AI in production

Gaizka Jiménez is a software developer in Bilbao. He ships generative AI and mobile apps to production.

AI in Python, the product in TypeScript. The native app, all the way to the store.

Bilbao, Basque Country · Available to start

Four years of software, two of them with RAG, agents and LLM pipelines in production. Until September 2026, AI and mobile engineer at CODX Digital. On the side I build emap, a Basque mobility map. It is on the App Store.

G
Gaizka
Jiménez
ProfileSoftware · AI and mobileBased inBilbao, SpainCODX2025–2026StackTypeScript · Python · NativeLanguagesES · EU native · EN
·Questions

Short answers.

Who is Gaizka Jiménez?

Gaizka Jiménez is a software developer in Bilbao. He ships generative AI and mobile apps to production: the AI layer in Python, the product in TypeScript, and the native app as far as the store.

Is he available to join a team?

Yes. He is looking for a team in Bizkaia, on-site or hybrid, and also remote within Spain or the EU. Email is contacto@gaizkajimenez.com.

What is emap?

emap is a mobility map for the Basque Country: live public transport, door-to-door routing and open data. The iOS app is on the App Store and the web is at emapapp.com.

emap page→

What is emap Labs?

emap Labs is an open benchmark for geographic retrieval in Basque and Spanish, with DOI 10.5281/zenodo.21282784. If the retriever invents an answer, it fails.

emap Labs page→
01Work

My own product, and team product.

They are in production: you can open them, download them or cite them. Each one made a different call (my own infra, several AI providers, native, or a closed ecosystem). That is the work.

03How I work

I work so that whoever comes next understands it.

Habits I already use in the projects above. You can audit them in the repo.

01

Decisions get written down, not remembered.

I keep numbered architecture decisions (emap is up to D-023), with the context and the option I dropped. Whoever arrives later does not have to ask me why routing avoids a third-party API: it is written down, and dated.

02

A green CI is the definition of done.

A hard rule I hold myself to: after every push I check the pipeline, and if it is red that gets fixed before anything else. In the data layer the evals have regression gates: if a metric drops, the push does not pass.

03

No pretending.

What cannot be measured is left out. The benchmarks I publish reward an “I don't know” over inventing an answer. Limitations sit next to the results, coverage bias included. I would rather have one small number that survives a whole interview.

  • Interface changes verified with a screenshot, not with a claim
  • WCAG 2.1 AA accessibility audited with axe-core
  • Spanish, Basque and English at parity, without machine translation
05Notes

Working notes on what I build.

The build logs cover how something got built, dead ends and decisions included. The rest are notes on AI, mobile and tech in Asia. Written in Spanish.