# You'll Lose Your Job in 2027 — Elena Verna

Elena Verna (growth advisor; ex-SurveyMonkey/MongoDB/Miro/Lovable) writing on Substack to a tech-worker audience: assume your current role expires by end of 2027, even if you keep your seat. Her own case — she "fired herself" out of pieces of her manager role and dropped back into IC work — is offered as the example. The piece's stance is opposite to the [[anti-llm-discourse]] cluster and sits in what would be the "adapt-or-die" counter-cluster: don't refuse the tools, restructure your career around them.

## The argument in one move

Full-time stability was already shaky pre-AI (juniors replaceable, seniors expensive line items); AI compresses the timeline. The response isn't to fight the trend but to develop *career optionality* — the ability to leave or rebuild on demand — and to retool the day-to-day with LLMs.

Three steps:

1. **Honestly check whether you like your job.** Once your role gets rewritten, the people winning at the new shape will be the ones who love the work. If you don't, this is the window to pivot.
2. **Build career optionality now**, before you need it. Two shapes: skill-as-product (consulting/advising/freelancing — Verna's own path; "more from solopreneurship than from cash comp of my full-time role") or a "Mom 'n' Pop SaaS" (niche micro-product, $3k/month semi-passive is the bar she names). The point is the *foundation* — don't quit cold; start the slow process while still employed.
3. **Become AI-native** — but specifically, climb the tier ladder below.

## The six tiers of AI-nativeness

See [[ai-native-tiers]] for the standalone concept. Verna's ladder reads naturally as a competence progression for non-engineering workers, but the framing also lands for engineers (Tiers 4-5 are roughly the vibe-coding-vs-agentic-engineering distinction from [[simonw-vibe-coding-agentic]]).

1. **Writing buddy.** AI improves the clarity of written communication. Verna's caveat: *write your own version first and have AI critique it, so you actually learn*. Otherwise the loop is the [[cognitive-debt]] trap.
2. **Meeting partner.** Granola in every meeting. Prompts she actually uses: "If you were my manager, what are my strengths and areas for improvement?" — i.e. the AI as a low-stakes performance reviewer.
3. **Thinking partner.** Anti-sycophancy is the whole point. Prompts that work: "Disagree with me — what's the strongest counter-argument?" "What am I missing or being naive about here?" The threading through to [[ai-sycophancy-loop]] is left implicit.
4. **Builder.** Internal tools, external apps, prototypes — anything with a UI. Verna's plug: Lovable (she advises them).
5. **Shipping to prod.** Non-engineers writing code that ships in the company's actual product. "Instant superpower and job security unlock."
6. **Agents.** Self-executing recurring tasks. Verna's warning, unusual for the rest of the piece's tone: "Often require more setup, oversight, and cost than just doing the thing yourself. So it's worth checking these out, but beware the hype." Echoes [[agentic-coding-fatigue]] and [[agentic-coding-is-a-trap]] from inside engineering.

## Where it sits in the wiki

This is the wiki's first piece in the *pro*-AI-adoption-from-the-PM/growth-side cluster. Most of the existing voices on LLM adoption ([[i-am-an-ai-hater]], [[i-will-never-use-ai]], [[no-silver-bullet-llms]], [[peril-of-laziness-lost]], [[cult-of-vibe-coding]], [[building-syntaqlite-ai]]) come from engineers or hostile critics. Verna's piece is what the workplace-strategy version of the same questions sounds like — and notably, her advice doesn't deny the harms, it routes around them: "AI just helps you do the wrong thing faster" without clarity is her version of the [[ai-great-leap-forward]] / [[business-idiot]] worry.

Her Tier 1 caveat ("write your own first, then critique") is the same posture-shift Osmani prescribes in [[dont-outsource-learning]]. The two pieces converge on the same micro-practice from opposite ideological starts.

What's notably absent from Verna's framing: any treatment of who decides which role survives, how unevenly the optionality advice scales (her own platform comes from 5 years of building it), or the [[skill-atrophy-supervision-paradox]] risk that climbing the tiers erodes the skill underwriting your services business in the first place.

## See also

- [[ai-native-tiers]] — the six-tier ladder as a standalone concept
- [[elena-verna-blog]] — author entity
- [[dont-outsource-learning]] — converges on the "write first, critique with AI" posture
- [[anti-llm-discourse]] — the opposing cluster this piece structurally counters
- [[agentic-coding-fatigue]], [[agentic-coding-is-a-trap]] — engineer-side warnings about Tier 6
- [[cognitive-debt]] — what Tier 1 done wrong becomes
- [[simonw-vibe-coding-agentic]] — Tier 4 vs Tier 5 line, from the engineering side
- [[oss-sustainability]] — closest existing piece on the "skill-as-product" career shape