It probably just didn't have enough economic value for the company, from your explanation of the role I'm not sure I see the value either. The guy probably earned enough money in a few years that would take me 15 years of work, I'm not sure this as a "personal tragedy".
Completely agree. What is a tragedy though, is that if Google treats their most hardworking engineers like this they are creating a culture of minimal effort. If this is "just a job" as you can expect to be laid off at a moment's notice with no care for the value of your contributions, then what is the point in doing anything more than what the job description entails. It's just incentivizing people to treat their job the same way the company treats their employees. A culture of distrust and minimum effort. It's very sad to see.
> if Google treats their most hardworking engineers like this they are creating a culture of minimal effort
This is bizarre to me because my impression from three years ago was that they were trying to correct from that, and it sounds like they overcorrected right back to it. I spoke with a Google engineer I think in 2022, he had heard rumors there were going to be layoffs on his team, and he had sent a message to a more senior team member that he hadn't heard from in months to let her know that she should, to put it delicately, maybe manage her visibility better. And she responded that she had lost interest in the job anyway, hadn't done anything except respond to emails and messages in over a year, and had 99% transitioned to managing a collection of properties she had been accumulating over the years, so if he heard she got laid off, he shouldn't feel bad for her. I'm pretty sure that was in 2022.
To see Google go from tolerating being ghosted by highly compensated senior+ engineers in 2022 to laying off people who were doing excellent and high-profile work in 2025 must be surreal for people inside Google. If this is all accurate, they swung the pendulum from one zone of encouraging laxity and disloyalty right through the healthy zone and into another zone of encouraging laxity and disloyalty with dizzying speed.
> If this is "just a job" as you can expect to be laid off at a moment's notice with no care for the value of your contributions, then what is the point in doing anything more than what the job description entails
I guess the half million dollars yearly (I'm assuming he made) and the fact there aren't tons of other places he can get that kind of money and prestige for doing that kind of job. I'm not saying I'm loving any of this, but yeah the system we've built treats all of us like replaceable cogs. During good economic times we don't really feel it, but we are now in a rough patch and we see the capitalist economic reality for what it is.
> from your explanation of the role I'm not sure I see the value either
Google has traditionally had a fair number of developer relations engineers. Chrome team alone has several. The current devrels include Una Kravets, Bramus van Damme, Rachel Andrew, possibly Jecelyn Yeen, Oliver Dunk, Matthias Rohmer, probably some others... They help prioritise new browser features through developer feedback, document new features, maintain documentation at web.dev, spec up new features and represent Google at various standardizing bodies, write walkthroughs and tutorials, build demos to showcase new browser features, make explanatory videos, give conference talks, and generally keep us, web developers, up to date with modern browser best practices.
Their value to web developers is immense. Their value to Google is possibly in that good devrels are a living advertisement of web technologies in general, and Chromium-based web browsers in particular. The better developers know browser features, the more attractive and capable UIs they can build for the web, the more consumers will be attracted to the web (including Chrome), and the more money Google will ultimately make via advertisements.
Adam has been so great in this role that it does not make sense to me that Google decided to cut specifically his position.
> Google has traditionally had a fair number of developer relations engineers
I wish them all well, but things can change fast depending on how the economy is doing and where the company is headed priority wise.