I've been a frontend engineer for 10+ years, mostly React, design systems, and performance work. Currently a Lead at a product company, targeting Staff IC roles next.
I keep getting this question internally too — should I extend into full stack, or build mobile experience?
My honest take: Full Stack wins, at least for the Staff IC track.
Here's my reasoning:
Mobile fragments your narrative unless you're going full React Native + cross-platform
Full stack makes you dangerous in product discussions — you own the full feature slice
Staff roles reward depth + cross-team influence, not platform breadth
But curious what the community thinks — especially folks who've made this transition or hired for Staff roles.
What would you have done?
Full stack, not even close. At least if Staff IC is the target. Mobile isn't a wrong move, but it splits your focus at exactly the point where you need to go deeper. Staff roles reward people who can own a problem from end to end, not people who can work across platforms.
What's actually mattered most in my career isn't the stack, it's understanding what happens between a user clicking something and a database changing. Where data lives, how it gets there, what goes wrong when it drifts. That thinking transfers to every codebase I've touched.
The React Server Components + Next.js App Router story has made this concrete in 2026. You can own a full feature slice without leaving the JS ecosystem. That's a much easier sell in a Staff IC conversation than "I do a bit of both."
Ethan Frost
AI builder & open-source advocate. Curating the best AI tools, prompts, and skills at tokrepo.com
Hot take: in 2026, the distinction between "full-stack" and "mobile" matters less than it used to, because AI coding agents handle most of the platform-specific boilerplate.
What actually moves the needle for a senior frontend dev: understanding systems design, API contracts, and state management patterns that transfer across any platform. If you can architect a clean data flow, Claude Code or Cursor can help you implement it in React, Swift, or Flutter.
My suggestion: go full-stack. The backend knowledge compounds — understanding databases, auth, and deployment gives you the ability to ship complete products independently. Mobile-only devs often get bottlenecked by backend dependencies. Full-stack devs ship.