What do you want from a Web Browser Developer Relations team?

It’s my 10 year anniversary at Google today, and I’ve had an incredible time. I’ve been able to work on Chrome for the entire time here, starting as the most junior member to be being able to run a great team of passionate Developer Advocates, Developer Programs Engineers, Tech Writers, Program Managers and Developer Marketers all whose goal is to focus on helping make web development easier and better (sometimes with a Chrome focus, most of the time an holistic focus of Cross browsers).

I’m also on a flight to San Francisco for our team summit where we will cover the next few years ahead, but I’ve got some time to reflect (and procrastinate building the presentation for the team). I was also reading Jason Snell’s feedback about Apple and Developer Relations is mentioned in it, and it got me thinking.

Improving Developer Satisfaction will be a major focus for us this year, but what do you think we could be doing more of? what could we doing less off? In an ideal world what would you like a Web Developer relations team to be doing? How can we help you and your teams even more?

Looking forward to hearing your opinions especially if there are broad strokes that I can think about that could inform a strategy, I’m also slightly apprehensive :)

Picture of me smiling.

Paul Kinlan

I lead the Chrome Developer Relations team at Google.

We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.

Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on web.dev, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.

RSS Github Medium