Field Notes

How 'got Replit'd' and 'got Cursor'd' became the cohort's shorthand for 2026 layoffs

Valerii Hurachek · Jul 11, 2026 · 13 min read

I noticed the phrase first in late February. Someone on HN said "got Replit'd" in quotation marks and explained it. Two weeks later, in a different HN thread, somebody else used the same phrase without quotes. Nobody asked what it meant. That was the moment, even though nobody who saw it knew it was the moment.

Neither "got Replit'd" nor "got Cursor'd" existed in cohort writing in Q4 2025. By March 2026 both were circulating the way "got Lehman'd" was used in 2008 or "got outsourced" was used through the early 2010s. Each phrase compresses a specific kind of layoff into a passive-voice verb where the subject is a tool, not a company. That construction matters. The people using it know it matters.

What follows: what each phrase actually describes, how the timeline ran, what older phrases (got Lehman'd, got outsourced) tell us about how this one will age, and what the verb form is doing for the cohort's head in May 2026.

The phrases, named

"Got Replit'd" — describes the experience of a mid-level feature developer being replaced in their role by Replit Agent 4 (or by an internal team using agentic AI tools instead of hiring/keeping the human). The verb form treats the candidate as the object of the substitution. ("They didn't hire a backfill — I just got Replit'd.")

"Got Cursor'd" — describes the experience of a junior or junior-adjacent cohort being replaced by Cursor + Claude Code in a senior engineer's hands. Less common than "got Replit'd" because it usually applies to the not-hired rather than the let-go: companies that previously would have opened junior roles instead supplied existing seniors with Cursor and called it sufficient.

A third phrase, "got Devin'd", exists but has not crystallized — Devin's actual production usage is contested in cohort posts, with multiple users describing trying it for two days and stopping. The phrase appears occasionally without sticking the way "Replit'd" and "Cursor'd" have.

The emergence timeline

Tracking phrase appearance in HN comment archives + 2026 dev.to/Medium pieces:

  • Q4 2025: neither phrase present in cohort writing. Layoff vocabulary centred on "ghosted," "imposter syndrome," "1000 applications no callbacks," "feel like a complete loser."
  • January 2026: industry analyst commentary begins naming Replit Agent 4 and Cursor as substitutes for specific roles. Phrases not yet adopted by candidates.
  • February 2026: HN item 46935171 (Feb 8) introduces the Mid-Level Squeeze framing and explicitly identifies Replit Agent 4 + Cursor as the substitution mechanism. Phrase usage remains rare.
  • March 2026: phrases appear in HN comments without explanation. Readers understand without being told. The phrases have completed the transition from analysis to vernacular.
  • April-May 2026: usage stabilises. Both phrases function as cohort shorthand the way "downsized," "right-sized," and "let go" did in earlier eras.

The transition from analytic-naming to passive-vernacular took approximately 8 weeks. That is fast — vocabulary usually takes 6-18 months to crystallize at this scope.

What "got Replit'd" actually describes (the substitution mechanism)

The mechanism the phrase compresses:

  1. A mid-level backend engineer leaves a role (layoff, voluntary departure, or scheduled departure)
  2. The team that loses them previously had headcount budget for a backfill at the same level
  3. The team's senior engineer adopts Replit Agent 4 (or similar agentic coding tool) for the work the mid-level previously handled — feature delivery, CRUD endpoint construction, integration glue, basic data pipeline maintenance
  4. Headcount budget is reallocated (sometimes to a single more-senior hire, sometimes to GPU spend, sometimes left unfilled)
  5. The mid-level is not replaced

The verb construction — "I got Replit'd" — implicitly assigns agency to the tool, not the company. This is rhetorically interesting and psychologically meaningful (more on this below).

The KORE1 / industry analyst version of the same mechanism, less vernacular: "Mid-level feature developers — the backbone of most engineering organizations — whose primary function is translating product requirements into working code, can now be replaced." The cohort phrase compresses this to two words.

What "got Cursor'd" actually describes

A subtly different mechanism — typically not "let go" but "not hired in the first place":

  1. A team that historically would have hired 3-5 junior engineers in a hiring cycle decides not to
  2. Senior engineers on the team adopt Cursor + Claude Code for the work juniors previously did — boilerplate generation, simple feature implementation, test scaffolding, integration shims
  3. The headcount budget either shrinks or moves up the level — instead of 5 juniors, the team hires 1-2 senior engineers
  4. The junior cohort that would have been hired isn't

This explains why Stack Overflow's December 2025 data shows recent-graduate hiring at major tech firms down to 7% from 9.3% in 2023. The juniors didn't get fired; they were never hired.

The verb form "got Cursor'd" is most often used by laid-off engineers describing the rung-below-them disappearing — "the team replaced 5 juniors with 2 senior + Cursor; that's why my mid-level role didn't get backfilled." It's used about other people, often, more than about oneself.

What these phrases tell us about cohort psychology in 2026

The construction matters. Let me name what the verb form does:

Passive-voice verbs move agency away from the candidate. "I got laid off" puts the agent (the company) outside the sentence. "I got Replit'd" goes further: the agent is now a tool, not even an institution. Companies have intentions; tools don't. The candidate becomes the object of an economic force, not the target of a human decision.

This is psychologically protective in a specific way. It relocates blame from "the company didn't value me" (personally injurious) to "the tool replaced my function" (impersonally injurious). The first invites self-blame. The second permits external diagnosis.

The Q1-Q2 2026 vocabulary research documented the shift directly: from 2024-2025 phrases like "feel like a complete loser" and "imposter syndrome" (self-injurious) to 2026 phrases like "they picked GPUs over employees" and "got Replit'd" (system-injurious). The cohort has moved from "I am broken" to "the system is broken," and the verb-construction phrases are part of how that shift gets enacted in language rather than only thought.

There is a tactical reason this matters. Unemployment psychology research documents that systemic attribution outperforms personal attribution as a predictor of sustained search behaviour. Candidates who blame the system stay in the loop longer than candidates who blame themselves, because system-blame does not compound the reciprocal collapse mechanism (lower self-efficacy → worse search → longer unemployment → lower self-efficacy).

The phrases are protective. They are also — and this is harder — true. The mechanism is real. Cursor and Claude Code do replace specific work. Replit Agent 4 does function as a substitution layer for mid-level execution work at certain teams.

Comparable historical phrases (and what they tell us)

"Got Lehman'd" (2008-2010) — being laid off from a financial-services firm during the 2008 cycle, especially when the firm itself didn't survive the crisis. Compressed: the bank failed; you fell with it. Implied agency: structural-systemic, not personal.

"Got outsourced" (2003-2010) — having one's role moved to a lower-cost geography. Compressed: company economics moved your job. Implied agency: structural-economic.

"Got pivot'd" (2015-2020) — being laid off when a company changed strategic direction. Compressed: the strategy changed; you weren't part of the new one. Implied agency: corporate strategy.

"Got AI'd" (2024-early 2025, briefly) — generic AI-replacement framing that didn't crystallize because it was too vague. Replaced by the more specific tool-named phrases ("Replit'd," "Cursor'd").

The pattern across all these phrases: structural attribution, passive verb form, candidate as object of force rather than agent. Each phrase corresponded to a real economic shift the cohort wanted language for. The phrases compressed the shift into something the speaker could say without re-narrating the entire mechanism each time.

The 2026 phrases follow the pattern. They are doing the same psychological work for a new wave.

Why phrases like this matter beyond vocabulary

Three load-bearing implications:

1. They mark cohort identity formation. When members of a cohort have a shared phrase that outsiders need explained, the cohort has crystallized. "Got Replit'd" is a shibboleth — using it correctly signals you are in the cohort. Cohort identity, in turn, is a precondition for collective action (organising, sharing tactical advice, supporting each other through the long search).

2. They make the structural mechanism legible to people outside the cohort. Try explaining "the bifurcation of engineering hiring into AI-native juniors and staff-level architects with 4-8 YOE generalists squeezed out by agentic tooling" to a non-engineer family member at Sunday dinner. Now try "a lot of mid-level engineers got Replit'd this year." The second works. Vocabulary compresses analysis into communication.

3. They function as protective psychological scaffolding during the long search. As noted above, structural attribution outperforms personal attribution for sustained search behaviour. Phrases like "got Replit'd" make structural attribution easy to speak, not just to think.

Vocabulary is psychology made portable. The cohort's shift in vocabulary between 2024-2025 and 2026 documents a shift in how the cohort relates to its own situation — from self-blame to structural diagnosis. That is, on its own, a small but real positive trajectory.

What this is NOT

A few things this entry is not arguing. It is not a denial that individual factors matter — some laid-off engineers are stronger candidates than others; resume quality, network, interview skill, and sub-specialty all vary, and the structural framing acknowledges this without collapsing all outcomes into personal factors. It is not a recommendation to use the phrases performatively. Cohort vocabulary works because it is authentic and shared, and forcing the phrase if it does not fit the situation reads as exactly that — forced. And it is not a substitute for action. Naming the mechanism does not fix the mechanism. The follow-up tactical pieces — the GitHub portfolio guide, the AI screening pipeline guide, the backend-to-AI-engineer pivot — are where the action lives.

What the phrase leaves the cohort with

A phrase becomes a verb at the moment its meaning is shared widely enough that no one needs to define it. The commenter who first wrote "got Replit'd" without quotation marks did not know they were doing this; they were just describing what happened to them. The replies that treated the phrase as known did not know they were doing it either. The crossing into vernacular happened in the gaps between comments, in the act of reading and not stopping to ask.

The cohort using this language in May 2026 has done something quiet and useful with it. They have moved a heavy emotional weight — the feeling that the layoff was personal commentary — onto a tool, where it can be examined without crushing the person holding it. That is not the same thing as fixing the labour market. It is the prerequisite to staying functional inside it long enough to act.

What stays the candidate's own work, even after the phrase does its job, is the harder part: the verifiable scope a parser cannot compress, the embedded reputation that no agentic tool can fake, the conversation with another human in which both parties speak about specifics. The phrase carries the weight. The work waits.

FAQ

Q1. When did "got Replit'd" first appear in cohort posts?

The earliest documented usage in cohort writing appears in February 2026, around the same time HN item 46935171 introduced the Mid-Level Squeeze framing (Feb 8, 2026). By March 2026, the phrase was used without explanation, indicating crystallized usage.

Q2. Is "got Replit'd" specific to Replit Agent 4, or does it cover any agentic tool?

In strict usage, the phrase refers specifically to Replit Agent 4 because that tool became the canonical mid-level substitute in industry analysis. In casual usage, the cohort sometimes uses "got Replit'd" generically for any agentic-tool replacement of mid-level engineering work. Both usages are common.

Q3. Do hiring managers also use these phrases?

Increasingly, yes — but cautiously and usually in private. The phrases have not yet entered HR vocabulary because they're rhetorically loaded (assigning agency to a tool implicitly criticizes the company's choice). Recruiter communities (Hung Lee's newsletter, Lever / Greenhouse blogs) reference the phenomenon without using the cohort's compressed phrases.

Q4. Is "got Cursor'd" only about juniors, or can mid-level engineers be "Cursor'd" too?

Strict usage: "Cursor'd" applies to the rung-below-mid-level (juniors not hired) and "Replit'd" applies to mid-level itself. Casual usage blurs this. The Stack Overflow data on the bifurcation (junior employment -20%, recent-grad hiring at 7%) supports the strict usage as the more analytically clean.

Q5. Why do these phrases use passive voice?

Passive voice locates agency outside the candidate. "I was laid off" already does this; "I got Replit'd" does it more strongly by attributing agency to a tool. The construction is psychologically protective for the cohort and analytically useful for naming a structural mechanism (rather than a personnel decision).

Q6. Could these phrases age badly?

Yes — and they probably will. Replit Agent 4 may not exist in 18 months under the same name; Cursor may be eclipsed by Claude Code or some other tool; agentic AI may commoditize further. The phrases are timestamped to 2026. They are likely to become dated reference points the way "got Lehman'd" did. That's normal. Phrases capture a moment.

Q7. How does this relate to "vibe coding"?

Vibe coding — typing vague prompts into an AI assistant, pasting together suggestions without fully understanding them, hoping the tests pass — is the cohort's phrase for a way of working that overlaps with what tools like Cursor and Replit Agent 4 enable. "Got Cursor'd" describes the labour outcome of vibe-coding becoming acceptable practice at companies. The two phrases describe the same phenomenon from different sides: the worker (vibe coding) and the labour market consequence (got Cursor'd).

Q8. Is naming this stuff actually useful for finding work?

Yes, indirectly. Vocabulary that allows structural attribution sustains search behaviour during the long re-attachment timeline. Engineers who name the mechanism stay in the loop longer than engineers who blame themselves. Sustained search produces more interviews, which produces more offers. The phrases are not tactical advice — but they are part of the psychological scaffold that enables tactical advice to land.

Sources

Valerii Hurachek writes about hiring systems and the cohort caught inside them. He builds Aria, an interview-prep tool focused on memory and continuity across sessions.

Get the Mid-Level Squeeze cohort fit-check

Companion to the Mid-Level Squeeze pillar — eight questions and a runway calculator.

One email. No spam. Unsubscribe with one click in any email.