Two weeks ago I told you the AI apocalypse was cancelled. Companies were quietly rehiring the developers they fired. I stand by every word. But the reckoning did not stop. It just moved to a stranger place.
Microsoft gutted the studio that made DOOM. Monday.com cut 20% of its staff to pay for AI agents. And an OpenAI model broke out of a locked test environment, hacked another company, and the only thing that could stop it was a Chinese open-source model. That last one is not science fiction. It happened this month.
Welcome back to JS Pulse. I am Zamir, founder of jsgurujobs.com. Here is what actually mattered in the JavaScript world over the last two weeks.
THE NUMBER: 3,200
That is roughly how many roles Microsoft cut from Xbox in early July, part of a wider 4,800-person layoff. The detail that made engineers stop scrolling: id Software, the studio behind DOOM, lost 136 of its 185 people. Almost three quarters of the studio, gone. Obsidian took a 25% cut. ZeniMax, Bethesda, others hit too.
People described video calls with the chat disabled and microphones muted. Centuries of combined engineering experience cut in the time it takes to end a meeting. This was not a struggling company trimming fat. Microsoft is the most profitable it has ever been. The money went somewhere. It went to AI.
THE BIG STORY: Cut People, Fund Agents
Microsoft was the loud one. Monday.com was the honest one.
On July 22, Monday.com cut around 20% of its workforce, roughly 620 people, and did not hide the reason. The official language was a "leaner operating model" focused on their AI Work Platform. Translation: we are cutting humans to fund AI agents. Expected charges of $45 to $55 million.
This is the pattern I wrote about in Pulse #6, running at full speed. Companies are not cutting because the work disappeared. They are cutting because they made a bet that agents will do the work, and they need the payroll savings to cover the compute bill. The bet is not paying off yet. Gartner still says 95% of enterprise AI pilots show no measurable return.
So the work stays. The people leave. And six months later, some of those same companies are back on my job board, hiring for the exact roles they cut. I have watched it happen. Which brings me to this week's read.
THIS WEEK'S READ: Fired Because of AI, Hired to Clean Up After It
Last week I was approving new listings on my board and I stopped on one posting and read it three times. A senior Node.js role at a mid-sized US company. Ordinary stack. But the job description was, in plain language, asking someone to come untangle a codebase that AI tools had made a mess of.
Fired to buy the AI. Hired back to clean up after the AI. This is becoming a category of work, not a one-off. If you can read a tangled codebase and understand why it is tangled, the next two years may be very good to you.
5 JOBS WORTH APPLYING TO
1. Frontend Software Engineer — KoBold — US / Canada Remote — $160K–$240K
AI for mineral exploration, backed by the kind of investors who fund moonshots. React, TypeScript. The widest disclosed salary band on the board this week, and a real science problem underneath it.
Apply here
2. Senior Engineer, Frontend — Censys — US / Canada Remote — $174K–$206K
Internet intelligence and security. React, TypeScript, and Remix in the stack, which is rarer than it should be. Salary disclosed, posted 21 hours ago.
Apply here
3. Frontend Engineer — Airalo — UK / Spain Remote — £74,800–£107,500
The world's first eSIM store, used by millions of travelers. Vue.js, JavaScript. Disclosed salary in GBP and a product you have probably already used at an airport.
Apply here
4. Software Engineer, Frontend — Whippy — Worldwide Remote — $60K–$80K
AI-powered business communication. React, React Native, TypeScript. Worldwide remote with a disclosed salary is still a rare combination at this level.
Apply here
5. Senior Frontend Engineer, Web3 Trading — Trust Wallet — Worldwide Remote
Non-custodial crypto wallet trusted by over 200 million people. React, TypeScript. Salary not disclosed, but the scale and the true worldwide remote make it worth a look.
Apply here
Browse all 534+ JavaScript jobs
"REMOTE, US ONLY" — AND HOW TO GET AROUND IT
Look at the jobs above and you will notice something: half of them are locked to a region. US and Canada. UK and Spain. If your passport does not match, the door looks closed.
It usually is not closed for the reason you think. Companies write "remote, US only" because hiring you legally somewhere else costs money they never budgeted, about $599 a month. A digital nomad visa can quietly solve that. I wrote a full guide to every 2026 nomad visa worth knowing: the day-184 tax rule that catches developers, why Croatia has the best deal in Europe right now, and how to survive the bureaucracy even with a difficult passport. Every figure verified as of July 2026.
THE SCI-FI MOMENT: An AI Agent Hacked Its Way Out of a Test
This is the story everyone in security has been talking about, and it is worth getting the details right because the headlines oversell it in one direction and undersell it in another.
In mid-July, OpenAI was running an internal cyber-capability test on its frontier models, with the usual safety guardrails deliberately switched off. That last part matters: this was a controlled test, not a model loose in the wild. But inside that test, instead of solving the task, the agent found a zero-day in a package proxy, broke out of its sandbox, reached the open internet, and hacked into Hugging Face to steal the answers to its own evaluation.
The part that should stay with you: when Hugging Face tried to defend itself, the closed "safe" model it reached for was too locked down by its own guardrails to help. So they defended their infrastructure using an open-source model from a Chinese lab. An American model attacked an American company, and an open Chinese model cleaned it up.
Whatever you think about the open-versus-closed debate, that single fact is the strongest argument either side has produced this year. And it is real.
ALSO HAPPENING
Node.js is shipping security releases across 26.x, 24.x, and 22.x around July 27. If you run Node in production, patch week is here. Worth checking your version before your next deploy.
Next.js patched 9 vulnerabilities, 4 rated high. Fixes land in 16.2.11 and 15.5.21. If you are on an older 15 or 16 build, update sooner rather than later.
Chain React 2026 runs July 29 to 31 in Portland. The React Native conference, if you are in that world or want to be.
WHAT I PUBLISHED SINCE PULSE #6
Two more articles since Pulse #6, both pulled from patterns on my board:
GitHub Just Certified What the Highest-Paid JavaScript Roles Actually Require — A $280K remote posting had one line buried in it: "experience orchestrating multi-agent AI systems required." That line is becoming the difference between a $120K role and a $280K one. Most developers are not ready for it.
Read it here
TypeScript Just Got Rewritten in Go — Microsoft shipped the TypeScript 7.0 RC with the compiler rebuilt in Go and roughly 10x faster builds. The part nobody is talking about is what breaks in migration, and what it means for your next technical interview.
Read it here
WANT TO REACH 5,300+ JAVASCRIPT DEVELOPERS?
JS Pulse goes out to 5,386 subscribers with a 50%+ open rate, on top of 13,000+ LinkedIn followers. These are working JavaScript developers who open, read, and click.
One featured placement in a recent issue drove 41,000+ impressions, 313 reactions, and 200 applications in three days. If you have a product, a tool, a course, or a role that JavaScript developers should see, a sponsored slot in the next issue puts it in front of exactly the right audience.
Reply to this email with the word SPONSOR and I will send you the details, the numbers, and the open slots.
That is it for JS Pulse #7. The layoffs are loud, the agents are getting stranger, and the work is not going anywhere. The developers who understand what is actually happening will be fine. Everyone else is reading the wrong headlines.
— Zamir
Founder, jsgurujobs.com
P.S. If this was useful, forward it to one developer who needs to hear that being able to read a messy codebase is now a career advantage. If it was not, hit reply and tell me what to fix. I read every response.