Angular has changed a lot since 2023. Signals arrived. Standalone components replaced most NgModule boilerplate. And starting with v22, Angular moved to one major release per year, with 24 months of support for each (angular.dev). Angular v2 through v19 are now out of support. So when a candidate says "five years of Angular," the follow-up question is: which Angular?
Key Takeaways
- Anything older than Angular v20 is unsupported, so upgrade experience is a hiring requirement for most existing apps.
- Screen for signals, standalone components, and RxJS judgment, the three places modern and legacy Angular differ most.
- Angular fits large, long-lived apps with big teams. Hire people who like that kind of structure.
- About 1 in 5 professional developers uses Angular, so the pool is solid but smaller than React's.
Two Different Angular Developers
There are two groups on the market, and their resumes look alike.
The first learned Angular during the NgModule era and kept doing it that way. They write RxJS for everything, wrap simple state in subjects, and haven't touched signals. Their code works, but it's heavier than it needs to be, and upgrading their apps is slow.
The second group has moved with the framework. They know that a signal is "a wrapper around a value that notifies interested consumers when that value changes" (Angular docs), and they can explain when a signal is the right tool and when an RxJS stream still is. They build standalone components by default, a pattern the Angular team has pushed hard since v19.
For a new build, you want the second group. For a legacy rescue, you want someone from the second group who remembers the first era well enough to migrate out of it.
The AngularJS Question
If your app still runs AngularJS (version 1.x), that is a separate problem. AngularJS support officially ended as of January 2022 (AngularJS docs). It is a different framework from modern Angular, so moving off it means rewriting every screen, though a hybrid setup lets you do that one piece at a time instead of all at once. Some vendors sell paid extended support, which can buy you time. Our rewrite vs refactor guide covers how to plan the move without freezing the product.
What to Test
| Topic | Weak signal | Strong signal |
|---|---|---|
| State | Subjects and manual subscriptions everywhere | Signals for local state, RxJS where streams make sense, no leaked subscriptions |
| Components | NgModules for everything | Standalone components, lazy-loaded routes |
| Change detection | "Angular just updates" | Explains OnPush and why it matters for performance |
| Upgrades | "We stayed on v12" | Has used `ng update` across several majors and fixed what broke |
| Testing | Few tests, mostly snapshots | Component tests that check behavior, not markup |
A good 45-minute exercise: give the candidate a component that subscribes to an observable and never unsubscribes, then ask them to fix the leak and rewrite the local state with signals. A strong candidate finishes early and explains the tradeoff. A weak one fixes the leak and stops.
A Concrete Version
A 40-person insurtech company has an internal underwriting portal on Angular 14. It works, and nobody wants to touch it. Then a security review flags it: the framework is years out of support.
A strong Angular hire scopes the job before writing any code. They run `ng update` in a branch to see the list of breaking changes between each version, count the third-party libraries with no modern release, and find two that need replacing. Their plan moves one major version at a time, with the existing tests (plus a handful of new end-to-end tests on the quote flow) run after each step. Standalone migration and signals come last, once the app is on a supported version.
The company gets a realistic timeline and a list of risks up front. That early scoping is what you pay a senior engineer for.
The Honest Counterpoint
Angular is more framework than a small startup often needs. For a marketing site or a lightweight MVP, React or Vue with a small toolset can ship faster, and there are more developers to hire. In Stack Overflow's 2025 survey, 19.8% of professional developers used Angular, compared with 46.9% for React (Stack Overflow).
Angular's strengths show up at scale: many developers, many screens, long life, strong conventions. That is why it's common in enterprise, fintech, and insurance products. If your company fits that profile, the smaller pool is a fair price. If it doesn't, think twice before choosing Angular for a new project just because one engineer likes it.
Frequently Asked Questions
Should an Angular developer know RxJS?
Yes. Signals handle a lot of local state now, but HTTP calls, websockets, and complex event flows still lean on RxJS. The skill is knowing which tool fits which job.
Can a React developer switch to Angular?
A strong one can, in a few weeks, but they will fight Angular's conventions at first. If your app is large and your team is small, hire someone who already has Angular experience.
How long does an Angular upgrade take?
It depends on how far behind you are and how many abandoned libraries you use. A senior engineer can give you a real estimate after a day or two of running `ng update` in a branch, so ask for that before you commit.
The Bottom Line
Hire Angular developers who have kept up with signals, standalone components, and the new release schedule, and who have done real upgrades. Angular is a good choice for large, long-lived apps, and a heavy one for small products. For senior Angular engineers who have passed a live technical screen, see senior frontend developers in LATAM or see available engineers. For the broader role, read how to hire a frontend developer.
Roberto Espinoza is CEO of Ruzora, which helps US startups hire pre-vetted senior LATAM engineers, with a vetted shortlist in 72 hours. See available engineers.
