Software Engineering · Chapter 8 of 8
Backend, frontend, full-stack, mobile — and where the demand is
What the corpus says about each track, and what that means for how you position yourself.
Of 2,609 software engineering postings, the split by named specialism is uneven and worth knowing before you decide what to call yourself.
| Track | Roughly | What it changes about your prep |
|---|---|---|
| Backend | The largest named specialism | System design carries the loop; know your datastore deeply |
| Full-stack | Strong and growing | Breadth is the point — but have one side you are genuinely deep in |
| Frontend | Smaller than its visibility suggests | Performance, accessibility and state management are the differentiators, not framework familiarity |
| Mobile | Concentrated in consumer companies | Platform depth matters more than in web; releases are slow and unrollbackable |
| Embedded / systems | Small and durable | Least substitutable skill set here; debugging depth is the currency |
| ‘Agent’ engineer | Growing fast from nothing | See the AI field — this is now a distinct archetype |
On calling yourself full-stack
It is honest and it can read as shallow. The version that works: name the side you are deep in and describe the other as working competence. “Backend-leaning full-stack — I have shipped production React and I would not claim to be the person you want designing your design system” is far stronger than an unqualified claim to both.
The positioning that gets interviews
Specialism plus a domain beats specialism alone. “Backend engineer” competes with thousands; “backend engineer who has built payments at scale” or “…who has worked in a regulated environment” competes with far fewer and matches what enterprise postings actually ask for.
The domain does not need to be glamorous. It needs to be specific, and true.