Into the future

job ai

In May 2026, after almost 10 years at RubiconMD, I was laid off along with everyone else in the Spain section.

It didn’t feel great, to be honest, but I’m proud of everything we accomplished there, from Series B and the rushed feature development days to two acquisitions and full corporate transformation. I’m forever grateful for the opportunity I was given by the team back in 2016, all the awesome people I worked with and now count as friends, and everything I’ve learned along the way.

So, I took a short break, and now I’m back on the job market: looking for senior+ roles in platform engineering, technical leadership or good old hands-on development, full-time or contract, fully remote (and happy to travel). If that sounds like something you need, my resumé is here.

Coming back to the market in 2026 means facing the elephant in the room: AI. The same tools that are turning hiring for people like me upside down are the ones I’ve had to fully embrace to keep going. Turns out, I’m actually enjoying it.

A day with an agent

Back in December 2024 I wrote that I needed to review the resumé content and links, and that I definitely should write more. Then, in July 2025, I mentioned it had been my first time in a while without AI agents around, since we were heavily using them on the job. Well. Today, after mulling some ideas in my head, I sat down with the Claude Code CLI agent and, in a single session, “we”:

  • wrote an AGENTS.md and a few skills, so agents know how this site works;
  • fixed a pile of small template and SEO issues;
  • reworked the blog: five full posts per page, a page per tag, a tag cloud, and an archive by year in the sidebar;
  • cleaned up 143 messy tags (RAILS, ruby on rails and friends);
  • gave the whole site a visual refresh: IBM Plex fonts, a green accent, about 80 characters per line and a đź“ť favicon;
  • rescued my 31 old CookiesHQ posts: the company’s blog went offline in 2025, but the Internet Archive kept every single article, so the links work again;
  • fixed my resumĂ© (wrong dates, a typo, a broken separator) and gave it a “Save as PDF” button;
  • rewrote the About page so it actually says what I do, and that I’m looking;
  • and split the CSS into tidy files, checking pixel by pixel that nothing changed.

Every one of those would have taken me an evening or a weekend on my own, and realistically most of them would have stayed on the “someday” list forever. They’ve been sitting there for years.

It wasn’t magic, and it wasn’t me just pressing a button either. I still reviewed every change, said no to some suggestions, rewrote bits myself and made the calls. But the distance between “I should really fix that” and “done” has never been shorter.

So, into the future. Allons-y!

If you’re hiring, drop me a line.