Hire me

I'm an Independent Developer Educator in Palma, Spain. I teach AI coding agents, MCP and agent skills through my site, YouTube, an open source learn-agent-skills repo, talks and live workshops.

Before that I led developer education and community for Playwright for three and a half years. Weekly downloads grew from under 1M to over 20M during that time. I pushed for the official Playwright MCP server and taught it to developers.

After that I worked in applied AI, first in developer relations and then in platform engineering, where I built a Playwright agent inside a company's AI platform. It drives Playwright over CDP, takes test requests in the app, runs them in an embedded browser and returns an HTML report and trace.

I've spoken at conferences since 2018, in English and Spanish.

I care about developers getting unstuck on real work, and I teach by building. I want to turn agentic AI into practical guidance builders can use on Monday: narrow tools, clear contracts and honest failure modes. Then I want to bring what I hear from developers back into the product. My bar is whether a builder ships faster.

Playwright release videos used to be recorded after a release shipped, so bugs showed up on camera after users already had them. In early 2023 I wrote a release video strategy that changed the order. We recorded first, got a technical check, reported bugs, re-recorded and then posted to social. I also listed what every release video must include. My manager signed off, and the whole team followed that process. Recording first caught many bugs before users hit them.

I also built the Playwright ambassador program from the start. More on that below.

I needed 55 pages of end-user documentation with screenshots and had no docs team. I built three reusable agent skills and worked with an AI agent to write 55 pages with 59 screenshots in four days.

Community Playwright MCP servers already existed, and people inside the company kept asking me which one to use. The core engineers didn't think we needed MCP. Over several meetings I brought the community servers, the internal questions and the risk of giving no answer. I framed it as a choice for the team, not a demand. When interest stayed low, I built a demo with a Blender MCP server where an agent made a leprechaun with a rainbow and a pot of gold.

The team agreed, then built and shipped the official Playwright MCP on 21 Mar 2025. It got about 5k GitHub stars in roughly its first week. I own the push and the early demos, not every star. What I learned is that with engineers, a working demo beats a slide deck.

I once led a team of engineers and failed that room at first. They talked over me and ignored my decisions, because I was defending my idea before I had heard theirs. I asked my manager to sit in. They coached me to listen first, stand up when it mattered, and guide the team so they felt ownership while I still set the direction. After that I ran those meetings on my own, and I still lead that way when a room gets loud or stuck.

At a conference in Sep 2022 I sat with a well-known testing educator while he tried Playwright for the first time. He wanted role-based accessible locators and a visual UI mode. He also went looking for a plugin for a web server feature we already had, which showed me we weren't telling people about what had shipped.

The week I got back I took his feedback to the engineers and got him talking to the team directly. Accessible locators shipped in v1.27 less than three weeks later, on 7 Oct 2022. UI Mode followed in v1.32. The web server got its own docs page, and he later became a Playwright ambassador.

I built the Playwright ambassador program. The ambassadors didn't report to me. I picked people already teaching in their own communities and languages, gave them a stage and direct feedback, and nominated them for recognition. The public roster reached 10 ambassadors in 5 countries and 4 languages. Several went on to write books and courses. One ambassador in Argentina now teaches Playwright in Spanish across South America. The program later became part of a larger, long-running developer recognition program, which let us grow more Playwright ambassadors and reach a much wider community.

When MCP was brand new, I built and broke MCP servers myself before writing a single slide. Then I co-taught a live beginner workshop in Spanish. We covered the mental model first, then real server demos, then a live build of a weather MCP server that viewers could copy in about 20 minutes. The recording has about 16k views.

I built playwright-movies-app as a teaching demo in Jan 2025. When I moved on, its cloud backend was no longer available, so I replaced it with a mock API and a simple hosted login. The live demo and the learn site still work, and the repo has over 100 stars.

When I left Playwright in Dec 2025, the community channels had 44K LinkedIn followers, 18K Discord members and 27K YouTube subscribers, and Playwright's dev.to posts had 269K views. Those are community numbers I helped build, not my personal following.

I look at what people watch and use. My Playwright MCP tutorials on the official channel passed 180K and 140K views. A live MCP workshop I co-taught in Spanish has about 16k views. A demo app I built for teaching has over 100 GitHub stars and still runs.

The official Playwright MCP server got about 5k GitHub stars in roughly its first week. By Dec 2025 it had about 24k stars and about 1M weekly npm downloads, and on 27 Oct 2026 it had over 38k stars. I pushed for it and made the launch tutorials, demos and workshops. The engineers built it.

While I led developer education and community for Playwright, from May 2022 to Dec 2025, weekly npm downloads of the playwright package grew from under 1M to over 20M. That's the whole ecosystem, not my personal credit. My part was the docs, videos, talks, workshops, community and ambassador program around it.

Yes. The Playwright ambassador program reached 10 people in 5 countries and 4 languages: English, Spanish, French and Hebrew. Each ambassador teaches in their own community and language, so the program reaches people I couldn't reach alone.

The week I got back from a conference, I took one developer's feedback to the engineers. Accessible locators shipped in v1.27 less than three weeks later. A visual UI Mode followed in v1.32.