THE NUMBER
570.
That’s the floor. The confirmed minimum of engineers who got walked out in March, badges deactivated, and severance package PDFs waiting on the other side of an HR Zoom call. This number is the floor, because two of the five companies that cut this month decided the headcount was nobody’s business. Verint Systems said “several hundred.” Digg said “a sizable portion” and then pulled their app from the App Store before anyone could ask follow-up questions. Strip out the acquisition restructures, and an air taxi company that discovered physics doesn’t negotiate, and what you’re left with is 74 engineers who were developers, IT, and R&D who walked in on a Friday and walked out with a box. That’s your number. The rest is noise, wearing a press release. [Source: layoffs.fyi]
WHAT’S MOVING
Labor
You Can Have the Job. Just Come Into the Office. The LinkedIn numbers this week tell a story the job board newsletters will not. DevOps Engineer postings: 6,418 total, 3,528 new this week. Healthy volume on paper. But run the location filter, and the market shows its teeth: remote positions are 902, hybrid plus onsite combined (“Hybrid” is just another way of saying “On Site”) is 2,608. Ratio: 0.35. For every posting offering genuine location flexibility, nearly three are telling you where to sit and when to be there. SRE roles are worse at 0.26. Platform Engineer roles sit at 0.30. Cloud Engineers at 0.31. The RTO argument is over. The question you should be asking is whether the salary bands reflect the commute they just added back to your life. Based on this week's sample data, the answer is: sometimes, and only if you negotiate. [Source: LinkedIn Jobs]
Technology
The Bots Took the Tag. A script I built to track what DevOps engineers are actually excited about on GitHub returned ten results this week. Nine of them were AI agent frameworks wearing a DevOps tag and keywords like a visitor badge they found on the floor, stuck on their shirts to complete their barely thought-out disguise. The one repo that wasn’t an AI framework was project-nomad, an offline-first survival computer built for zero-connectivity environments, which nearly doubled its lifetime stars in seven days. Engineers are not excited about DevOps tooling right now. They are excited about building things that work when the network doesn’t. That is a signal worth sitting with. [Source: GitHub Topics Search executed on 3/16/2026-3/22/2026 via API]
Vibe
The Quiet Collapse of an Open-Source Project: Deno laid off staff this week without a public announcement. Developers pieced it together from LinkedIn departure posts and a Reddit thread. A blogger wrote a pointed postmortem titled “404 Deno CEO not found.” It hit 204 points and 138 comments on HN. The community largely defended Ryan Dahl (the Node.js creator), a genuinely rare engineering talent while the comments ran hot on a deeper question: is there a single VC-backed open-source project that has stayed genuinely healthy over the long term? The room couldn’t name one cleanly. Bun got acquired by Anthropic. Deno got quiet layoffs and a mean blog post. Your readers build on this infrastructure. [Source: Hacker News]
THE REPO WORTH WATCHING
Crosstalk-Solutions/project-nomad - 7,178 stars this week, 12,933 total
A self-contained, offline survival computer. AI, critical tools, and knowledge designed to work anywhere, with or without connectivity, and with or without a cloud provider standing between you and your data. It nearly doubled its lifetime stars in seven days, which, given where the vibe is at this week, and in general, tracks. This is the same week the “devops” GitHub tag got colonized by AI agents; the top-velocity repo in the infrastructure space is about building things that work when the network is gone. Engineers are quietly bringing all the useful things on the internet back within the castle walls, or at the very least, planning on doing so.
VERIFIED VS. VIBES
“You Don’t Even Need DevOps” They Said, From a Vercel Blog
The Vibe: Vercel published a piece this week titled “Two Startups at Global Scale Without DevOps.” The argument: managed platforms have matured to the point where dedicated DevOps functions are optional overhead for startups moving fast.
The Verification: LinkedIn shows 6,418 active DevOps Engineer postings this week, 3,528 of them added in the last seven days alone. Whether or not companies intend to fill these roles that they actually posted remains to be seen, but the numbers alone tell a story. The federal government’s official labor market data (BLS JOLTS) is running behind because the government is shut down, which means the statistical floor under all of these narratives is currently a hole in the ground until fresh numbers drop, so until then we will have to rely on open sources like LinkedIn to get these numbers and see where they go week to week.
The Read: Vercel sells managed hosting. A world where startups don’t hire DevOps engineers is a world where startups buy more Vercel. Read the incentive structure before you read the headline. The argument isn’t wrong for every company at every stage, but it is published by the company that profits most from you believing it. Six thousand active postings say the market hasn’t agreed yet.
TL;DR - The numbers imply that this is just a hot take by Vercal’s marketing team, and not an industry reality.
THE QUIET THING
We were somewhere outside of the old internet as people my age remember it, that wide-open, beautiful and chaotic disaster that used to feel like it was built for actual human beings, when things began to change in a meaningful way. What once was has become a distorted facsimile of itself.
The people who inherited the beautiful chaos of the old internet began to see human behavior on that medium as sterile metrics. Engagement numbers, optimization loops, quarterly growth targets, and all the data about who is doing what turned every platform that was ever worth a damn into something that needed to be worth more. The gospel of platform growth treated actual humans like they were in the way, or worse, like they were the product. It stopped being for the people.
Digg died the week of March 13th. Again. Kevin Rose bought back the platform he started in 2004 and rebuilt the whole thing from scratch to be what it once was, putting a team on the field with real moderation and verified humans with the goal of creating a genuine place to put things worth sharing. Not long after the public beta launched, the bots found it within hours. Before a single real community had a chance to form, the automated accounts were already camped out like they were waiting for easy spawn kills. Voting on things no one had read. Building the appearance of a conversation that was not actually happening. CEO Justin Mezzell wrote the postmortem himself, which is the kind of thing a person does when they still believe honesty matters: “the internet is now populated, in meaningful part, by sophisticated AI agents.” The app has since been pulled from the app stores. The only content on Digg at the time of this writing is the eulogy.
This past week, I ran a script to find what DevOps engineers were actually excited about on GitHub as part of the vibe check for this issue. The script returns the top ten trending repositories for a given set of categories related to DevOps and Platform Engineering. Nine of those ten results were AI agent frameworks wearing a DevOps tag like a costume from a dead man’s closet.
The same week, a YC-funded company launched a product to help brands get cited by AI search engines called Sitefire. The machines are now writing content to be read by other machines to be summarized for humans who will never see the original. Somewhere in that chain the human got optional.
I have been looking for the original dream of the internet my whole career and I think I know what it was now. Not the retirement package, not the IPO, not the VP title. The dream the original builders were chasing when they stayed up until 3AM in dorm rooms and garages and server closets held together with cables some other engineer forgot were plugged in was a network that amplified human connection rather than replacing it. A place where distance did not matter and your idea was as good as anyone else’s idea and the conversation was real because the people having it breathed the air and walked on their own legs.
We did not lose that dream. We lost the thread of it somewhere around the third round of VC funding, when the metrics stopped measuring connection and started measuring synthetic values that exist in service of making the numbers look impressive in a deck.
But here is the thing about dreams: they do not die when you stop finding them. They die when you stop looking.
Someone is going to build the more human internet, and they will do so carefully, with intention, in service of something actually worth building. Someone is going to figure out how to put the humans back in the center of the network. Someone is going to solve the bot problem that killed Digg’s relaunch, get the community there before the machines do, and build the thing that makes human presence visible and meaningful again.
That someone is learning how systems work right now. In a classroom, on a VPS, on old server hardware rescued from an e-waste pile. That someone is going to find a bunch of other people like them and set off on some harebrained, underestimated quest with a beautiful ramshackle idea that will remind everyone that we are still here.
The dream of the old internet is not dead. It is waiting for the engineers who are young and curious enough to still believe it is possible, and skilled enough to actually build it. I know those people exist because I have met them, and they have given me hope.
What I saw crawling around the innards of tech this week may look like a warning. I see it as a critical inflection point, a moment where the current AI runup is showing its age and the tools it produced are finally mature enough to build something genuinely worthwhile with. The warning and the invitation are the same thing. It depends entirely on who picks it up.
FOR THE PIPELINE
The remote ratio data from this week’s job search tells a story every student in a tech program needs to hear before they build their job search strategy around remote-first assumptions. In the current DevOps, Platform, and Cloud Engineering market, on-site and hybrid postings outnumber remote postings nearly 3-to-1. That does not mean remote is completely dead. It does, however, mean geographic flexibility is now a negotiating asset, not a baseline expectation. Before you take an interview, research the company’s remote history, not just their current posting. A company that was remote-first in 2022 and is now “hybrid” is a different negotiation than one that was never remote. Know the difference. The LinkedIn Company Pages “Life” tab and employee reviews filtered by “remote work” will tell you what the policy actually looks like from the inside. That is free research that most candidates skip. Don’t skip it.