Skip to content

I join your team and solve the hard part.

I'm Néstor López, a software engineer from Spain. The hard part is usually the frontend architecture, the build tooling or the infrastructure. I bring over 10 years of experience building software, and what I learn contributing to the open source tools teams build with. I work as one more engineer until the problem is solved.

Portrait of Néstor López
Néstor López · Based in SpainSoftware engineer · Consultant · Speaker

Worked with

  • Zephyr Cloud
  • Fever
  • Nexiona
  • Southern Glazer's Wine & Spirits
  • Agoda
  • Cloudflare
  • Snap Inc.
  • ByteDance
  • Zillow
  • Akamai
  • Dynatrace
  • Carrefour
  • Navan
  • Callstack
  • Nx
  • Teamworks
  • Addepar
  • Questrade
  • Makeswift
  • Terminal
  • EnBW
  • Rimac Seguros

I help build the tools I recommend.

I'm an engineer who works on the tools other teams build with. Most of my open source time goes into Module Federation, Rsbuild and Vite, and I wrote the first versions of the Module Federation integrations for Nuxt, TanStack, Electron and Astro.

I got here by building things to find out whether they would work. Around 2016 it was a Game Boy with a Raspberry Pi Zero inside and a lot of 3D printed parts. In 2026 it was Bad Apple, split into 5,258 microfrontends and played at 24 frames a second through Module Federation. Pushing a tool that far is how I learn where it breaks.

I teach what I learn. I have given 20 talks in 5 countries, I run workshops for engineering teams, and I write long posts on my blog.

I like infrastructure at work and at home. My homelab has a name, the Planetary Datacenter, and if it involves servers or networks I'm probably tinkering with it. Away from the keyboard I play video games, with a soft spot for arcade machines.

See the projects on nstlopez.com

Based in
Spain, working remotely
Languages
English and Spanish
Also
Member of the Module Federation organization

Find me at

Néstor López teaching a workshop, in front of a screen that reads Let's add Module Federation
Module Federation workshop, CityJS London, April 2026
Néstor López at a lectern with a laptop covered in stickers, on stage at MadVue
MadVue, Madrid, May 2026
A frame of Bad Apple on the big screen at ViteConf Shanghai, next to a long list of network requests
Bad Apple in 5,258 microfrontends, ViteConf Shanghai, July 2026

Simple code. Decisions in writing. A team that can go on without me.

The product, the roadmap and the code are yours. I bring the judgement I earned building production platforms at Nexiona, Fever and Zephyr Cloud, and the hands to do the work next to your engineers. I work in your repositories, your Slack and your pull requests, like anyone else on the team.

I still write code every week.

A lot of it is public, so you can read my work before we talk. It also keeps what I recommend tied to what works in production today.

I can start with a business problem, help choose an architecture and end up pairing with your engineers on the last bug of the migration.

I don't want you to depend on me. I explain what I do while we work, so the knowledge is in your team when I leave.

Néstor López speaking with a microphone on stage at ViteConf Shanghai
ViteConf Shanghai, July 2026

Understand the problem. Then touch the code.

No universal recipes, and no technology picked because it's new. I fit into the way your team already works and bring whatever is missing: a second opinion, an architecture or one more pair of hands.

  1. Start with the problem

    Before I recommend anything I want to know what you sell, what is breaking and what the next year needs.

  2. Decide in writing

    Every recommendation comes with its reasoning and its trade-offs. You always know where things stand, and why.

  3. Build with your team

    Prototypes, code review, pairing and migrations done in small pull requests. I unblock your engineers. I don't replace them.

  4. Hand it over

    I prefer simple code your team can maintain without me. When the work ends, the code and the knowledge stay with you.

You keepOwnership of what you build.

The priorities, the decisions, the code, the infrastructure accounts and the final word on all of them.

I bringThe commitment of a teammate.

Over 10 years of experience across frontend, infrastructure and hardware, a straight answer when you ask for one, and the technical depth to carry the work through myself.

If I do this well, you won't need me next year.

Wide enough to see the system. Deep enough to fix it.

I know these six areas from the inside. In each one I have shipped production systems or merged code upstream. Outside them, I'll tell you who to call instead.

  • Module Federation and microfrontends

    Independent deploys across frameworks and bundlers, server-side rendering with Nuxt and federated modules on Node.js. I'm a member of the Module Federation organization, with more than 90 pull requests merged across its repositories.

  • Build tooling

    Rspack, Rsbuild and Vite. I rebuilt Nuxt's Rspack builder on top of Rsbuild and migrated Sentry's frontend bundling to it.

  • Edge and distributed infrastructure

    Edge deployments, multi-cloud networking with WireGuard and ZeroTier, and services that don't depend on one machine.

  • AI integrations and adoption

    Agents, retrieval and MCP servers that hold up in production, and coding agents such as Claude Code and Codex fitted into how your team already works.

  • Industrial IoT

    Device connectivity, MQTT and AMQP pipelines, Yocto edge operating systems and the cloud behind them. Three years building them at Nexiona.

  • Technical leadership and mentoring

    Architecture decisions, code review, first engineering hires and the technical side of a funding round.

Tools I work with

  • TypeScript
  • Rust
  • Python
  • Node.js
  • React
  • Vue
  • Angular
  • Nuxt
  • Astro
  • Module Federation
  • Rspack
  • Rsbuild
  • Vite
  • tRPC
  • Effect
  • libSQL
  • FastAPI
  • Cloudflare Workers
  • Terraform
  • Docker
  • WireGuard
  • ZeroTier
  • MQTT
  • RabbitMQ
  • Yocto
  • Linux

Three ways to put my experience to work.

  • Consulting

    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.

    Architecture / Migrations / Code review / Mentoring

    Hours, formats and terms

  • Training

    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.

    Module Federation / Rspack / TypeScript

    Formats and how it works

  • Talks

    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.

    Conferences / Meetups / Company events

    Topics and how to invite me

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.