Paul Kinlan

There is a peculiar species of person who joins one of the world's most powerful technology companies and spends 16 years making sure it cannot wall you in. Paul Kinlan is that person. As Lead for Chrome and Web Platform Developer Relations at Google, he has spent the better part of two decades with a single, clear obsession: the open web should win, and developers should have the tools to make it happen.

Kinlan grew up on the Wirral - that thumb-shaped peninsula between the Mersey and the Dee in North West England - watching his father repair computers in their living room. He was not a passive spectator. He found the demo scene, the cracking scene, and a computer club, and he started building things. At 12, he watched someone play Street Fighter in an arcade and thought not about the game but about the loop, the joystick input, the code underneath. He went home and taught himself QBasic. The first real project? Lottery-number-picking software for his grandfather. Not a startup pitch deck. Lottery numbers. For his grandfather.

That combination of practicality, curiosity, and a willingness to build things for actual people who need them has defined everything he has done since.

By 18, Kinlan had started a web hosting company, running it as an exclusively Perl shop at a time when Perl was the web. He later enrolled at Liverpool John Moores University for a BSc in Software Engineering, where he simultaneously worked at Experian building Hunter 2 - a fraud detection system - in .NET and JavaScript. After university, a stint at a Liverpool telecoms company building voice interaction systems filled the days. The evenings were for side projects: Twe2, FriendDeck, Vooices, Ahoyo. Products with character, built by someone who clearly could not stop making things.

In 2010, Google noticed. He joined to build developer platforms, and he has not looked back - or slowed down.

Developer relations is a job that succeeds in inverse proportion to how often the person doing it gets credited. Kinlan's fingerprints are on almost every tool and resource modern web developers take for granted.

Google Web Fundamentals - the reference site that taught a generation of developers what "progressive enhancement" and "responsive design" actually meant in practice - was his initiative. Add to Homescreen, the feature that blurred the line between website and native app, came through his team's advocacy. The 300ms click delay that made mobile websites feel sluggish compared to native apps? He pushed to kill it. Lighthouse, the tool millions of developers run before shipping anything, is part of his team's work. Workbox for service workers. Squoosh for image optimization. BrowserSync for synchronized cross-device testing. The list reads like a greatest hits of the modern developer workflow.

None of this happened by accident. Kinlan's team works at the intersection of engineering, education, and advocacy - they sit close enough to Chrome's development to influence what gets built, and they face outward enough to hear what developers actually need. It is a tricky balance to hold for one year. He has held it for sixteen.

There is a consistent strand running through everything Kinlan does publicly: the web's greatest virtue is that it is open, linkable, and does not require anyone's permission to participate in. His career has been an extended argument for that virtue from within one of the organizations most capable of either defending or undermining it.

He talks about "universal access" not as a platitude but as a design constraint - the link enables access for everyone, and any architecture that breaks or bypasses the link should be viewed with suspicion. His advocacy for Progressive Web Apps was about giving developers a path to near-native experiences without surrendering the open web's principles to a walled-garden app store.

He is also clear-eyed about the pace problem developers face. "Information overload," he has said, is among the most significant challenges - the technology changes faster than anyone can track, and the developer ecosystem rewards those who already know what to learn next. His work on web.dev, MDN contributions, and Chrome release communications has been partly an attempt to solve that problem at scale.

In 2025, Kinlan launched AI Focus - a newsletter and blog dedicated to exploring what artificial intelligence actually means for the web and web development. Not the breathless hype version. The practical, what-does-this-change-for-people-who-build-websites version.

His angle is characteristically grounded. He is not chasing the AI gold rush. He is asking what happens to the medium of the web when AI can generate sites, describe interfaces, and automate the parts of development that used to require specialist knowledge. His essays - "Email: The Web's Forgotten Medium," "Describing Sites Instead of Coding Them" - read like dispatches from someone who has been thinking about web platform design long enough to notice what the AI wave is about to change, and what it cannot touch.

At Google I/O 2025, he was on stage as Lead for Chrome Developer Relations - the same role, a bigger moment. The question he is working through in public is whether the open web can absorb the AI era the way it absorbed mobile, cloud, and every previous wave of change. His bet, predictably, is yes. His work is showing developers how.

He still lives in Ruthin, a medieval market town in North Wales with a population under 5,000. The contrast with Mountain View is not lost on him. It might be the point.