The 2026 Tech Job Market Is Hot (If You Have the Right Skills)
Lenny Rachitsky dropped the latest tech job market data last week. It's the most optimistic report he's published in four years. PM roles at 3-year highs. Engineering openings past 67,000 globally. AI roles in hockey-stick mode.
One number hasn't moved: design roles are flat since early 2023.
The story isn't that design stopped mattering. It's that AI changed who gets to ship.
The numbers
7,300+ open PM roles — 75% above the 2023 low, up 20% this year. We're back to 2022 levels.
67,000+ engineering openings — 26,000 in the U.S. alone, still accelerating.
AI roles are exploding — at AI-native companies and traditional companies adding AI-specific positions.
5,700 design roles — flat since 2023. There are now 1.27x more PM roles than design roles.
The market is rewarding people who can build.
Why design flatlined
Lenny thinks AI is letting engineers move so fast that the traditional design process gets skipped. I agree.
A frontend dev with Claude Code and a component library ships landing pages in an afternoon. The Figma-to-handoff process feels like bureaucracy. AI generates UI patterns on demand. The six-week design cycle looks like overhead.
Products that look bad still fail. But the path from idea to shipped work doesn't always run through a designer anymore.
The bottleneck shifted from "can we design it?" to "can we build it?" The people who can build, win.
What this means for you
The job market is already back. Just not for everyone.
The heat is in roles that combine product sense with execution. A PM who can prototype their own ideas tests faster than one waiting for eng. A founder who ships their own MVP doesn't beg for a technical cofounder. An engineer who understands product builds what should exist, not just what was requested.
The market is separating people who talk about product from people who ship product.
Here's what I keep seeing: a PM learns the SaaS Builder skill, prototypes a feature themselves, and ships in a weekend instead of a month. An engineer picks up the Landing Page Builder skill and starts handling marketing pages without waiting for a designer. These aren't hypothetical examples — this is what happens when you remove the dependency bottleneck.
The skill stack that wins
The roles that are growing want the same things:
- You can take an idea from zero to deployed without three other people
- You know how to use Claude/Cursor/Copilot as force multipliers, not crutches
- You ship fast and iterate
- You know what users actually want, not just what they say they want
None of these show up on a resume. They're visible in what you've built.
The new credential
"Ex-Google" and "PM at Big Tech Company" don't signal what they used to. Everyone has them on LinkedIn. Hiring managers can't tell who's actually good.
The new credential is shipped work. A side project with users. A SaaS that makes money. An open-source tool people use.
Apply for a PM role with "I built [X], got [Y] users, learned [Z]" and you're not competing with the thousands of "passionate about user experience" applicants. You're in a different league.
That PM I mentioned who prototyped in a weekend? They used the SaaS Builder skill to scaffold the full stack architecture, Stripe integration, and authentication in one session. Their portfolio had a shipped product, not a case study about "leading cross-functional alignment."
Skills vs networking
Old advice: network your way into a job. 2026 version: build your way into consideration.
Ship something interesting, people notice. Write about what you learned, like-minded people find you. Solve real problems, opportunities find you.
A founder builds a tool with a skill file, posts about it, gets three inbound inquiries from companies looking for that exact capability. An engineer learns SEO through the SEO Optimizer skill, builds a side project that ranks, and suddenly they're the only technical person in the room who understands growth. I've watched this happen repeatedly.
What to actually do
Stop waiting for permission. Start shipping.
Pick a framework — Next.js, Remix, whatever. Just commit.
Get good with AI tools — Not "I tried ChatGPT once." You should know how to make Claude write production-ready code. The SaaS Builder skill is literally the patterns I use to ship MVPs in days.
Build something small — Launch it. See what happens. The Landing Page Builder skill handles the UI that slows most people down.
Learn to get users — The Guerrilla Marketing skill teaches you how to get your first 100 users without spending on ads.
Not sure where to start? The skill quiz takes 60 seconds and points you to the right one based on what you're building.
Six months from now you won't be "looking for opportunities." You'll have a portfolio that speaks for itself.
The job market is hot. Whether you're the one everyone wants to hire or the one watching from the sidelines — that difference isn't luck. It's what you've built.
Sources: