Skip to content

Three ways to put my experience to work.

Consulting, training and talks. In all three you work with me directly. I'm the one on the call, in the room and in your pull requests, and there is no handoff.

Where
Remote, from Spain. On site for training, talks and a consulting day.
Languages
English and Spanish
How
In your repositories, your Slack and your pull requests

Consulting

  • 10 or 20 hours a month
  • 8 hours in one day

Architecture / Migrations / Code review / Mentoring

I join your team for the questions, reviews and decisions that come up as you build. A frontend that has to be split across teams, a build that takes too long, or an architecture that needs a second opinion before you commit to it. I mentor the engineers who will own it afterwards.

How the monthly hours work

  • Fixed monthly fee

    One invoice a month, agreed up front. No hourly billing.

  • Capped hours

    The agreement states the hours, so both sides know what a month includes.

  • Async first

    One scheduled session a week. The rest happens in writing, in your Slack and your repositories.

  • No on-call

    If production goes down at 3am, the person who answers has to be on your team. I help you hire them.

How a single day works

One full day of senior technical leadership on the decisions that are expensive to get wrong. A CTO's judgement, before you can hire one.

  • You set the agenda

    You decide what the day is for. An architecture to validate, a roadmap to review, or the questions investors will ask.

  • Online or in person

    By video call, or in the room with your team.

  • Decisions in writing

    You leave with the decisions and the next steps written down.

  • No commitment

    The day stands on its own. If you want ongoing help afterwards, the monthly hours are there.

What the hours can cover

  • Architecture

    Stack, data model, cloud and build-or-buy. The decisions that cost months to reverse, made with you, written down with the reasoning and sized for the company you are today.

  • Code and infrastructure review

    A walk through what your team has built. You hear what is fine, what will break first and what to fix before it does.

  • First technical hires

    Which roles you need first, how to interview for them and what a good answer sounds like. Your first engineers set the bar for everyone you hire after them.

  • The technical side of your raise

    The architecture and roadmap answers investors ask for, prepared before the technical due diligence calls.

Also as a one-off project

  • Technical audit

    A fixed-scope review of your architecture, code and infrastructure. You get a written report that says what is fine, what will break and what to fix first. Useful before a raise, an acquisition or a rewrite.

  • AI systems

    AI features that hold up in production: agents, retrieval and MCP servers that answer fast, cost what you planned and fail safely. I work hands-on with the major agent harnesses, such as Claude Code and Codex, and fit them into how your team already works.

Training

Module Federation / Rspack / TypeScript

Workshops and courses for engineering teams, hands-on and on your own codebase when that's possible. I taught Module Federation in Practice at CityJS London in 2026, and I can adapt it to your stack.

Two formats

  • Workshop

    One session on one topic, from an empty editor to working code. Module Federation in Practice is one I have already taught.

  • Course

    Several sessions over a few weeks, for a team that is moving to a new stack. Each one builds on the last, and the team applies it to its own code in between.

How it works

  • Hands-on

    The team writes code for most of the session. I keep the slides short.

  • On your codebase

    When it's possible, the exercises use your own repositories, so the team practises on the code it ships.

  • Adapted to your stack

    Module Federation with Rspack, Rsbuild or Vite, in React, Vue, Angular or Nuxt. Tell me what you run and I'll build the sessions around it.

  • Remote or on site

    By video call or in the room with your team, in English or Spanish.

Talks

Conferences / Meetups / Company events

Conference talks, meetups and company events, in English or Spanish. I have spoken at ViteConf in Shanghai and at CityJS in London and Singapore, about microfrontends, bundlers and infrastructure that isn't tied to one machine.

What I speak about

  • Module Federation

    Microfrontends across frameworks and bundlers, server-side rendering with Nuxt, and federated modules on Node.js.

  • Rspack and bundlers

    How frontend bundlers got here, and where Rspack and Rsbuild fit when teams deploy independently.

  • Distributed infrastructure

    Edge deployments, multi-cloud networking, and code that is not tied to one machine.

  • TypeScript in production

    Service architecture with tRPC, Effect and libSQL.

A technical decision that won't move? Tell me about it.

You don't need to arrive with the solution. Write a few lines about your product and your team. I read every message myself, and if I can help I'll reply by email to set up a call.

Fields marked * are required.

What you're building, where it hurts and what you need help with.