For most of my career, I treated my tech stack like a progress bar.
More Angular. More RxJS. More Nx. More Supabase. More AI tools.
If I just kept adding skills, the ceiling would move up automatically.
I kept upgrading my stack and my career stayed exactly the same.
I hit a point where I had a loaded stack and a surprisingly flat trajectory.
Freelance matches were thin. Take‑homes still got rejected. My own AI SaaS hit friction that more syntax couldn’t fix.
I didn’t hit a skills ceiling. I hit a positioning ceiling.
The Senior Playbook: Add Frameworks, Hope for the Best
Watch how most senior devs “level up”:
- They add another frontend framework (React, Next, Svelte).
- They sprinkle in a backend (Node, .NET, Java, Go).
- They experiment with a new database, a cloud provider, maybe Kubernetes for good measure.
The CV gets longer.
The LinkedIn headline becomes a tech‑stack salad.
The feeling is: “I’m more employable because I know more tools.”
In reality, what you often get is horizontal growth:
- You go from “Angular dev” to “Angular + React + Node dev”.
- But you’re still competing in the same generic pool: “senior fullstack developer who can build features.”
If your LinkedIn headline is just a list of tools, you’ve already lost the story game.
Meanwhile, the market is quietly rewarding people who did something else:
- They picked a niche (“I fix broken fintech dashboards that lose users on step 3 of onboarding.”).
- They productized their value (“Performance and UX audits that lift conversion by 15% in 2 weeks.”).
- They learned to tell a story about their work, not just list the tech.
And then AI arrived and quietly pushed the stack race into even stranger territory.
My Case Study: Maxed Out on Angular, Stuck on Story
Here’s my situation, stripped of ego.
- I’ve been in Angular for 7+ years.
- I’ve done legacy migrations, zoneless modernizations, Signal‑based state, Nx monorepos, performance work.
- I use Claude Code and Antigravity heavily to move faster.
- I can operate as the “Legacy Rescue” person: the one who drops into a messy Angular codebase and turns chaos into something you can ship.
On paper, that looks great.
In practice:
- Most “Angular roles” now want fullstack with .NET or Java on the backend — stacks I don’t want to go into.
- Angular‑only freelance opportunities are fewer, and many still treat you like a generic pair of hands.
- I started my own solo company: building AI‑driven SaaS and offering automation consulting. Both need web and mobile, and I can’t hide in “Angular only” anymore.
- Even with AI support, I hit friction on things like Supabase, auth, RLS, and mobile — not because they’re impossible, but because my brain was still wired around “stack first.”
My instinctive solution?
“Maybe I should add React. Or Next. Or a backend stack. Or something new…”
But when I looked honestly at what was actually blocking me, it wasn’t the lack of one more framework.
It was the fact that I was still thinking like a stack , not like a story.
What “Your Story” Actually Means as a Developer
Let’s clear something up: “your story” is not a fluffy bio paragraph.
In a tech context, your story is the through‑line that answers three questions:
1. Positioning — Who are you for?
— “I rescue legacy Angular apps for B2B SaaS founders who can’t afford downtime.”
— “I build fast MVPs for non‑technical founders in fintech.”
— “I design developer tooling that cuts CI times in half.”
2. Niche — What specific problem do you own?
— “Angular performance & modernization for compliance platforms.”
— “AI‑powered internal tools for ops teams drowning in spreadsheets.”
— “Onboarding flows for SaaS with high trial drop‑off.”
3. Product value — What outcome do you reliably create?
— “We cut your largest Angular page LCP by 40%.”
— “We ship your MVP in 4 weeks so you can sell before you hire.”
— “We reduce your manual ops time by 30% with automations.”
Notice what’s missing:
- “I know Angular, React, Node, Next, Prisma, Postgres, Tailwind, Docker, AWS.”
Your tech stack is the implementation detail behind that story.
Clients, hiring managers, and users care far more about the story.
Most seniors don’t have a stack problem. They have a positioning problem disguised as a stack obsession.
AI Changed the Stack Equation (Whether We Like It or Not)
Before AI coding tools, being “the person who knows X” was a real edge.
- You knew Angular inside out.
- Or you knew React best practices before others.
- Or you knew how to hand‑roll Node backends quickly.
Now?
- Claude Code can scaffold an unfamiliar stack.
- AI can translate patterns between frameworks.
- Antigravity can reason about codebases you haven’t even seen before.
This doesn’t make expertise useless.
But it shrinks the value of “I’ve memorized every corner of this framework” as your main differentiator.
AI can help you:
- wire up a basic Supabase schema,
- draft RLS policies,
- hook Next.js to Stripe,
- scaffold a mobile client in React Native.
What AI can’t do for you:
- choose the right problem to solve,
- pick a clear niche with money and urgency,
- design a valuable product around that problem,
- tell a compelling story about why your solution matters,
- build trust with the people who pay you.
AI can fake a stack. It can’t fake a story, a niche, or a value proposition.
If you keep treating “leveling up” as “adding more stack”, you’re racing in a lane that AI is rapidly commoditizing.
AI will happily write yet another CRUD app; it won’t convince anyone they should pay you senior rates.
How I’d Actually Choose a Stack Today (Assuming AI Support)
So how do you decide what to build with, as a senior dev in 2026?
If we assume you’re willing to lean on AI to fill gaps, the stack decision comes after three questions:
1. Who is this for?
— Example: B2B SaaS founders with a broken Angular app.
— Or: ops teams in fintech drowning in manual workflows.
— Or: solo founders who need to validate an AI product in 4 weeks.
2. What painful bottleneck am I solving?
— LCP/TBT too high, users bailing on dashboards.
— Manual processes blocking growth.
— No MVP, no sales conversations, just “ideas”.
3. Where does the value live?
— In a dashboard? A small internal tool? A marketing site? A mobile touchpoint? An automation that runs in the background?
Only after that do I pick a stack, with three constraints:
- Can I reason about it? (I don’t need to be an expert, but I must be able to debug it with AI help.)
- Can AI accelerate me in it? (Good tooling, good examples.)
- Will my buyer care what I used? (Spoiler: usually not, as long as it’s stable and maintainable.)
For example:
For my AI SaaS MVP, a pragmatic choice might be:
— Next.js for the app,
— Supabase for auth and data,
— Stripe for billing,
— plus AI tools to patch my non‑Next gaps.
The buyer doesn’t care that it’s not Angular. They care that it works, loads fast, and makes them money.For my consulting, the opposite is true:
— I should double‑down on Angular as a stack,
— but package it as Angular audits, detoxes, and modernization sprints, not “hours of Angular.”
Your stack is a cost function and a delivery detail.
Your story is the value proposition.
The Real Ceiling: Over‑Indexing on Stack, Under‑Indexing on Story
Here’s the pattern I see (in myself and other seniors):
We pour energy into:
- learning new frameworks,
- adding more tools to the CV,
- chasing the “hottest” stack on Twitter.
We under‑invest in:
- clarifying who we actually serve,
- narrowing to a problem we can own,
- collecting and telling stories of outcomes, not features,
- packaging our skills into offers that are easy to buy.
And then we quietly wonder:
- why our applications look like everyone else’s,
- why we feel “replaceable” in interviews,
- why our freelancing rates stall,
- why our own products struggle to gain traction.
Your biggest bottleneck probably isn’t your stack. It’s how forgettable your story is.
The ceiling isn’t that you “only know Angular” or “only know React”.
The ceiling is that your work is indistinguishable from every other “senior dev” who learned the same stack and never turned it into a story.
What “Leveling Up” Looks Like in Practice Now
If I rewired my own senior‑dev leveling plan around this, it would look less like:
- “Add React, then Go, then AWS cert 1, then AWS cert 2.”
And more like:
Sharpen positioning
— “I fix the Angular apps that generalists break for B2B SaaS and fintech.”
— or “I build AI‑powered internal tools that cut ops time by 30%.”Define 1–2 niches
— Angular modernization for compliance platforms.
— AI‑powered automation for data‑heavy teams.Productize my work
— Fixed‑scope Angular audit.
— 2‑week performance sprint.
— AI automation pilot with one clear success metric.Use AI to bridge stack gaps on demand
— Need a tiny Next.js marketing site? Let AI bootstrap it and I reason check it.
— Need to wire Supabase RLS safely? Draft with AI, then review as an architect.
— Need a mobile companion? Use AI to scaffold React Native or Flutter and validate quickly.Tell the story publicly
— Medium articles that walk through legacy rescues, performance wins, and AI‑assisted builds — not just “here’s how to use X API”.
— LinkedIn posts that show before/after metrics and decisions, not just tools.
— Case studies on my site framed as narratives, not portfolios.
The stack is now a servant of the story, not the star of the show.
Your Tech Stack Isn’t Your Ceiling
I’m not against learning new frameworks.
I’m still improving my web fundamentals. I’m still expanding beyond Angular where it makes sense. I still enjoy the craft.
But I no longer believe my next breakthrough will come from adding yet another logo to my profile.
Your tech stack gets you into the room. Your story decides what happens once you’re there.
Your story is:
- who you serve,
- what bottleneck you remove,
- what outcomes you can point to,
- how clearly you can explain it.
AI will keep eroding the advantage of “I know this stack slightly better than the next person.”
The advantage it can’t touch is “I know who I’m for, what I solve for them, and I can ship value fast — with whatever stack makes sense.”
Before you learn another framework, try writing a better story about the ones you already know.
So before you commit to the next framework on your roadmap, try this:
Write one paragraph that starts with:
“I help [who] go from [pain] to [result] by [what you actually do].”
If that feels harder than learning a new tool, that’s a sign.
It’s not your stack that’s holding you back.
It’s the story you haven’t written yet.
I fix the Angular apps that generalists break.
Karol Modelski is a senior Angular developer and frontend architect rescuing legacy B2B SaaS frontends.
If your Angular app is slowing your team down, start here: https://www.karol-modelski.scale-sail.io/
Top comments (0)