On July 22, 2026, Monday.com filed to cut roughly 20% of its workforce, about 630 people, while raising its FY26 non-GAAP operating margin outlook from ~13% to ~15%. This is not a distressed company. It is a profitable one firing the humans who built the SaaS surface that "monday Agents" will replace in 2027. If you're one of them, or you're at Visa, Cisco, GitLab, Cloudflare, or Oracle running the same play, the resume you shipped in 2024 is now working against you.
The reframe is not "learn AI." It is renaming the work you already shipped in the vocabulary the hiring manager is now reading in.
Why Monday.com's cut is the template, not the exception
Monday.com's layoff is the cleanest example yet of AI pivot layoffs: profitable SaaS companies cutting product surface teams while explicitly keeping the hiring budget open for agent work. The SEC filing spells it out. Hiring continues in "key strategic areas" throughout 2026, even as $30 to $35M in severance goes out the door and another $30 to $35M in office impairments hit the books.
Co-CEO Eran Zinman described a "flatter organization" with fewer management layers and smaller autonomous teams, plus a new go-to-market motion with deeper on-site implementation support. Translation: fewer PMs writing specs for the dashboard, more forward-deployed engineers wiring agents into customer workflows. The company still expects 19 to 20% YoY growth in 2026.
The trigger event was February 2026. CNBC reporters with zero coding experience used Anthropic's Claude Code to build a working Monday.com clone in under an hour for less than $15. MNDY shares are down more than 50% year to date and ~75% off the 52-week high. That is the moment "SaaS surface" started reading as commodity on Wall Street, and the layoff notices started reading as inevitable in the boardroom.
The pattern is now industry-wide:
- Monday.com: 630 cut (~20%), July 22, 2026.
- Visa: 2,600 cut (~7%), primarily tech and product teams.
- Cisco: ~4,000 cut (5%) in May. CFO Mark Patterson: "This was really not a savings-driven restructure... realigning resources around silicon, optics, security and AI."
- GitLab: ~350 cut (~14%) on June 3, 2026. CEO Bill Staples called it a "generational rebuild" for 100x agentic workloads.
- Cloudflare: rebuild announced for agentic AI.
- Oracle: 21,000 reduction (13%) over 12 months, disclosed to regulators that AI deployment "resulted, and may continue to result, in reductions to our workforce."
Through June 2026, AI was the leading stated reason for US job cuts for four consecutive months, cited in 101,743 announcements, roughly 23% of everything Challenger, Gray & Christmas tracked.
The number nobody applying is looking at
There are only 868 US "AI Product Manager" title-holders in the entire market. Monday.com alone just released 630 people who could plausibly aim at that pool. That is the real math laid-off SaaS PMs need to price into their strategy.
In Refolk's index of US professional profiles, here is what the supply side actually looks like right now:
| Segment | US count | What it means for you |
|---|---|---|
| "SaaS" Sr/Principal PM | 2,127 | The legacy pool being displaced |
| "AI Product Manager" title variants | 868 | The target role identity |
| PM + SWE with LangChain / LLM / Agents skills | 2,238 | Agent-fluent cross-functional supply |
| SaaS PMs per open AI PM identity | 2.45x | You are competing against ~2.45 other SaaS PMs |
| Agent-skilled SWE+PM per AI PM | 2.58x | Engineers with LLM skills are the bigger threat |
| Monday.com layoff vs. entire US AI PM pool | 630 vs. 868 | One company just dumped 73% of the identity pool into the market |
Top current employers hiring AI PMs, per the same index: Google, Box, Bill.com, Wells Fargo, ServiceNow. Concentrated in SF, NYC, and Atlanta. For agent-skilled engineers, add IBM, Speak, Whop, and CCC Intelligent Solutions.
A single company's cut equals ~73% of the total US population holding that job title today.
Two things follow. First, "just relabel yourself as an AI PM" is a strategy 2,127 other people are running. Second, the differentiator is not the label. It is the specific SaaS depth you have that agent teams need, described in words the agent team uses.
The structured-substrate reframe
The most useful sentence in the entire Monday.com news cycle came from analyst Sanchit Vir Gogia, who described Monday.com's moat as its "structured substrate": boards, permissions, and typed workflows give agents "something firmer to act on than documents and chat history." That is your resume language.
A pre-agent Monday.com PM bullet reads:
Led roadmap for board permissions and automation recipes across 250,000 enterprise customers.
The same work, renamed for 2026 hiring managers:
Designed the permissioned board schema and typed automation surface now serving as the agent action substrate for 250,000 enterprise customers. Defined the invariants (row-level ACLs, typed columns, deterministic recipe outputs) that let downstream LLM agents take reversible actions without escalation.
Nothing invented. Same shipped work. Different vocabulary. Agent teams are hiring people who understand why documents and Slack threads are terrible action surfaces and structured schemas are good ones. You spent four years living that lesson. Say so.
Rewriting every bullet on every posting is the exact work Refolk takes off you. Paste the job description, get your resume back rewritten in the target company's language, with a fit score against the posting and a cover letter that actually references the role. With median time-to-hire stretched to 4.7 months, spending 40 minutes per application to rewrite by hand is severance you don't get back.
Bullets to rename, by function
Match old language on the left to new language on the right. This is translation, not creative writing.
| Pre-agent language | Agent-era language |
|---|---|
| "Owned dashboard configuration UX" | "Owned the tool-schema exposed to downstream agents" |
| "Wrote requirements for Zapier integrations" | "Defined typed action contracts for third-party automation" |
| "Ran onboarding flows for enterprise CS" | "Built the forward-deployed implementation playbook now used for agent rollouts" |
| "Managed permissions and RBAC" | "Designed the action-authorization surface for autonomous agents" |
| "Reduced support ticket volume 30%" | "Built the deflection substrate; documented failure modes now training agent-handoff evals" |
"AI-washing" is real, and you can exploit it
Roughly 90% of executives told NBER researchers that AI has had no impact on employment at their own firm, even while attributing impact at other firms. Many "AI restructurings" are ordinary org redesigns in a new outfit, which means candidates who can point to actual shipped AI work beat candidates who only rename old work.
The NBER working paper (WP34836, Bloom et al., ~6,000 executives across the US, UK, Germany, and Australia) is the counter-frame worth knowing. Sam Altman said the quiet part out loud in February 2026: "almost every company that does layoffs is blaming AI, whether or not it really is about AI." Wharton's Peter Cappelli was blunter: "They're just hoping."
Every "AI restructuring" you read about is part strategy and part cover story. Your resume has to survive both readings.
What this means practically for the laid-off Monday.com or GitLab PM:
- One shipped AI artifact beats ten renamed bullets. An internal LLM eval you built, an agent-handoff pattern you spec'd, a prompt library you owned, a RAG pipeline you scoped with a data engineer. If you have one, it goes at the top.
- If you don't have one, ship one in week two. Not a course certificate. An eval harness for a domain you know. A public write-up of the agent action surface at your last job (redacted). A working prototype using Claude Code or LangChain. The 2,238 agent-fluent engineers in the index all started somewhere.
- Interview for the "key strategic areas" clause, not the general listing. Monday.com's own SEC filing said hiring continues. IBM is tripling entry-level AI hiring while replacing ~200 HR positions with agents. The doors are open. They are just narrow.
Target the companies laying off, not just the ones hiring
Direct answer: apply to Monday.com, GitLab, Cisco, and Visa for their agent roles. These companies just fired thousands between them and are actively hiring for the next architecture. Internal recruiters have the context you don't have to explain.
Concrete targets by function, drawn from current listings and the Refolk index:
- Forward-deployed / implementation engineer: Monday.com's new go-to-market motion is built around this role. Also Box, ServiceNow, Bill.com.
- Agent-workflow PM: Google, ServiceNow, Wells Fargo. Wells Fargo is the sleeper here for anyone with enterprise-compliance SaaS depth.
- AI product-ops / evals lead: IBM (tripling entry-level AI hiring), Speak, Whop.
- Platform PM for agent-facing APIs: Bill.com, CCC Intelligent Solutions, ServiceNow.
The tailoring problem is the same across all four. The Bill.com bar is not the Wells Fargo bar. The Google agent-team bar is not the Speak bar. Refolk scores how well you fit each posting before you spend the afternoon writing a cover letter, so you can triage 40 target companies down to the 8 where the fit score justifies the effort.
Up from 3.2 months in 2024, a 47% increase. Tech unemployment is 5.8%, the highest since the dot-com bust. Every un-tailored application eats runway.
What to do in the first two weeks
Direct answer: rewrite your master resume in agent-era vocabulary, ship one small AI artifact, and target 30 to 50 postings at companies currently in the AI pivot, tailoring each one.
- Days 1 to 3: Rewrite every bullet on your master resume using the structured-substrate reframe. Every mention of "workflows," "permissions," "integrations," "automations," or "dashboards" gets translated.
- Days 4 to 7: Ship one artifact. An eval harness, a public teardown of your last product's action surface, a prompt library for a vertical you know cold. Post it. Link it from your resume.
- Days 8 to 10: Build your target list of 40 companies from the AI PM and agent-skilled employer lists above. Apply the fit-score triage. Drop anything below a 70% match. Refolk will draft the tailored resume, the cover letter, and the fit read per posting, so the compressible work is compressed.
- Days 11 to 14: Warm intros to the top 10. Recruiters at Monday.com, GitLab, and Cisco are watching their alumni lists closely right now. Use that.
The people who will be re-employed by October are not the ones who spent August applying with a generic "Senior Product Manager, SaaS" resume. They are the ones who understood that 868 is a very small number, and that being one of the 2,127 people fighting for those seats requires a resume written for the seat, not for the last job.
FAQ
Should I take the "AI Product Manager" title even if my last three jobs were traditional SaaS PM?
Yes, if you can defend it in an interview with one specific shipped artifact. The 868-person US AI PM pool is small, contested, and hiring managers know most applicants are relabeling. What separates the interview-getters from the ghosted is a concrete piece of AI work in the last 6 to 12 months: an internal eval, a prompt system, an agent handoff spec. Without that, aim for "Platform PM," "Forward-Deployed PM," or "AI Product Ops" roles where your SaaS depth reads as an asset instead of a substitute.
Is it worth applying to Monday.com, GitLab, or Cisco right after they laid people off?
Yes. All three explicitly stated they are continuing to hire in AI and agent-adjacent areas. Monday.com's SEC filing named "key strategic areas" as a continuing hiring priority throughout 2026. GitLab's Bill Staples framed the June cut as a "generational rebuild," meaning the rebuild needs people. Internal recruiters at these companies do not need the market context explained to them, which shortens the cycle by weeks.
How do I explain being laid off from a company that framed the cuts as an AI restructuring?
Directly, in one sentence, without apology, then pivot. "Monday.com restructured around agents and cut 20%. The team I was on built the board schema and permission model that's now the substrate for monday Agents. I'm looking for the next place where structured product work meets agent surfaces." That answer positions you as the person the acquirer needs, not the person the seller cut.
How much of this reframe can I automate versus do by hand?
The vocabulary translation and per-posting tailoring is the automatable part. The one shipped AI artifact is not. Use Refolk to generate the tailored resume, cover letter, and fit score against each posting, so the 40-minute-per-application tax drops to a few minutes and you can cover 50 targets in the time you used to cover 8. Spend the reclaimed hours building the eval harness or the write-up. That is the part that actually moves interview conversion.