There is a talk on YouTube about the browser's event loop. It has been watched millions of times. It uses animations of physical queues and shopping aisles to explain setTimeout, microtasks, requestAnimationFrame, and the difference between tasks and render steps. It is the kind of talk that makes a complex subject feel inevitable in retrospect. The person who made it is Jake Archibald, and he has been doing that - making hard things feel obvious - for over a decade.
Archibald currently works at Mozilla on Firefox. Before that, he spent roughly a decade at Google as a Developer Advocate for Chrome. Before that, he was at Lanyrd. Before that, the BBC. Before that, Reuters. And before all of it, he was a Flash developer at a university in Middlesbrough studying multimedia - building the very kind of thing he'd eventually help make obsolete.
The trajectory is worth sitting with. A lot of web careers move in a straight line toward specialisation. Archibald's moves laterally through the whole stack of browser culture: from proprietary plugin tech to core web standards, from developer tools to spec editing, from one major browser to its most direct competitor. He is one of a genuinely small number of people who has worked in meaningful technical roles at both Google Chrome and Mozilla Firefox.
Chapter One
From Flash to Function
The BBC stint is formative. Four years building a low-level JavaScript library under strict accessibility and cross-browser constraints. Pre-ES6, pre-fetch, a time when you wrote careful, deliberate code because you had no alternative. This is where the BBC taught him what most platforms eventually teach their engineers: that constraints make you better, not worse.
Remy Sharp noticed him at a meetup and got him to speak at Full Frontal, a conference in Brighton. That talk launched a conference career. His art teacher's maxim - "you get better at painting with every painting you paint" - became his philosophy for software. Every project, no matter how small, as practice.
Lanyrd was the bridge. The startup's core product was a conference social network, which had a very practical problem: conference venues have terrible wifi. Working offline was not a theoretical goal - it was a survival requirement. Archibald dug into the emerging web standards for offline-capable apps and found his calling. When Google came looking for someone who could talk credibly about Service Workers and offline-first architecture, his resume was impossible to argue with.
The Google Years
Building the Offline Web
The Service Worker specification is, without exaggeration, foundational infrastructure for the modern web. It powers background sync, push notifications, offline caching, and the entire progressive web app ecosystem. Archibald was one of its editors. He didn't just advocate for the spec - he helped write it, helped ship it, built tools to track its adoption across browsers, and wrote the Offline Cookbook: a document so practical that developers still reference it a decade after publication.
At Google, he co-hosted HTTP 203 with Paul Lewis - a podcast and video series that picked apart web platform quirks, browser edge cases, and the gap between spec and implementation. The format was two people on a sofa, talking through a technical problem with genuine curiosity. No slides, no bullet points, no corporate messaging. It worked because both hosts were actually interested in the answers.
Contributing to the HTML specification was, by his own description, a personal landmark. The web outlives any individual contributor. Leaving marks on its foundations is as close to permanence as a developer gets. Archibald has said as much explicitly - "the web will outlive me, so it feels good to be leaving a legacy." That is not the language of someone who sees developer advocacy as a marketing function.
He resigned from Google in May 2023 with a public post on X: "Big life update: I've resigned from Google to take on an exciting new role." A break followed. Then Mozilla.
Now
Firefox, Standards, and still at it
At Mozilla, Archibald works directly on Firefox's web platform implementation. Not advocacy. Not documentation. The browser itself. The shift from explaining what browsers do to actually changing what they do is not a small one. It closes the loop on a career that started by observing browser behaviour and ends - for now - by determining it.
In April 2025, he announced Firefox 142's developer-facing features with a characteristically dry thread on X. In early 2026, he contributed to coverage of Interop 2026 - the collaborative initiative between Apple, Google, Igalia, Microsoft, and Mozilla to close cross-browser compatibility gaps. He is scheduled to speak at SmashingConf Freiburg in September 2026, and appeared at Web Day Out in Brighton in March 2026, talking about the long road to a customisable <select> element.
His blog at jakearchibald.com remains active. His contact page remains theatrical: recruiters are instructed to write their pitch on paper and throw it out the window. The RSS feed is maintained. The dry British humour has not been patched out.
The handle, for the record, is @jaffathecake - a reference to Jaffa Cakes, the British confection at the centre of a real VAT tribunal case over whether it is legally a biscuit or a cake. It is a perfect encapsulation of the man: technically precise about something most people don't think twice about, with just enough absurdity to make you laugh before you realise you've learned something.