If you want to know how to hire Angular developers, start with the resume line that says "five years of Angular". It can mean AngularJS, which officially lost support in January 2022, or a pre-standalone codebase built entirely on NgModules. Neither tells you whether the person can build with signals, run a zoneless app or upgrade across two major versions.
This guide sits in our series Hire developers by tech stack: rates, vetting and interview guides. With Angular, most bad hires are decided before the first interview, by a job spec that doesn't pin a version or say what kind of app the person will work on.
Why "Angular developer" hides three different hires
Most Angular job posts are really one of three roles.
The first is the migration engineer. They maintain an AngularJS app or an old NgModules codebase and move it forward, one version or one framework at a time. The second is the modern Angular application engineer, who works with standalone components, signals and zoneless change detection on a current version. The third is the full-stack engineer who pairs Angular with a backend, such as Node with NestJS, .NET or Java.
These people overlap less than the job title suggests. A great migration engineer may never have shipped a zoneless app. A modern-Angular specialist may have never opened an AngularJS controller, and shouldn't have to. Name the app type in the spec ("internal admin tool on Angular 21", "AngularJS to Angular migration, 80 screens") and the wrong resumes filter themselves out.
Angular versions in 2026: what to write in the job spec
Pin the major version in the spec. It costs one line.
Angular's release schedule changed with v22, so articles written before it describe the old cadence. The Angular release policy on angular.dev now says to expect a major release every 12 months, 4-6 minor releases for each major release, and a patch release and pre-release build almost every week. The same page says that until v22, Angular "had a 6-month major release cycle, with 1-3 minor releases for each major release." Majors are typically supported for 24 months: 12 months of active support with regular updates and patches, then 12 months of long-term support with only critical fixes and security patches.
The page's current table reads like this. v22 was released on 2026-06-03 and is active until 2027-06, with LTS running to 2028-06. v21 (released 2025-11-19) is in LTS until 2027-06. v20 (released 2025-05-28) is in LTS until 2026-11-28. The page says versions v2 to v19 are no longer supported. It lists the next major, v23.0, at roughly June 2027, and marks that date as subject to change.
Two practical consequences follow. If your codebase is on v20, the support clock ends on 2026-11-28, so the job is partly an upgrade plan, and you should say so in the ad. And if your ad says "Angular 15", you're advertising an unsupported framework to the people best placed to notice.
Ask every candidate about ng update experience. Someone who has moved a real app across two majors has read changelogs, fixed broken third-party dependencies and met the Node and TypeScript requirements. The Angular version compatibility table lists them per release. For v22.0.x it asks for TypeScript >=6.0.0 <6.1.0, and for v21 it asks for TypeScript >=5.9.0 <6.0.0, so an upgrade is never only an Angular change. Our TypeScript hiring guide covers how to screen the language side.
What modern Angular changes about screening
The skills that separated candidates in 2020 aren't the ones that matter now. Four things belong in a 2026 screen.
Signals come first. Angular's signals guide defines one as "a wrapper around a value that notifies interested consumers when that value changes." A candidate who can only explain state through RxJS observables and @Input() bindings has learned an older Angular.
Zoneless is next. The zoneless guide says zoneless is the default in Angular v21 and later, and lists performance, Core Web Vitals, debugging and ecosystem compatibility as the benefits. Anyone who has only worked on zone-based apps will have a hole here.
Standalone components are the third. According to the NgModules overview, a component must be explicitly marked standalone: false to be declared in an NgModule. NgModules are now the exception, so ask whether the candidate has built a project without them.
Testing is the fourth. Per the Angular testing guide, new CLI projects use Vitest with jsdom by default, and Karma is still supported. Some hiring pages still list Jasmine and Karma as core skills. Both are fine to know, but a candidate who has never seen Vitest hasn't started a new project recently.
RxJS stays in the screen. The compatibility table accepts RxJS ^6.5.3 or ^7.4.0 for v22.0.x, so it's still part of the platform, and signals haven't removed the need to reason about streams.
Angular vs React: what it means for hiring pool and ramp-up
React's pool is much bigger. The Stack Overflow 2025 developer survey technology page puts React at 46.9% of professional developers (44.7% of all respondents), Angular at 19.8% (18.2%) and Vue at 18.4% (17.6%). Angular's pool is far smaller than React's and close to Vue's in size.
There's no primary source we can cite for how long a React developer takes to become productive in Angular, so we won't give a number. A strong React engineer is a fair candidate if you screen for what doesn't transfer. Component thinking and state discipline carry over. Dependency injection, RxJS and Angular's template syntax mostly don't, so screen those directly. Our guide to hiring React developers covers screening on that side, and our hiring guide for Vue.js developers is the closest frontend comparison.
Rates and cost
We aren't printing an Angular rate here. No primary dataset gives one, and the vendor figures conflict: the ranges we checked on marketplace and agency pages overlap only partly, and none of them explains how it was calculated. A number you can't trace is worse than no number.
What moves the price is more useful. Seniority does, obviously, but so does whether the candidate can own architecture decisions (state, rendering, module boundaries) rather than implement tickets. Backend overlap raises it, since a full-stack Angular and NestJS engineer covers two jobs. The engagement model matters as well: contract, staff augmentation and permanent hires all price differently. Ask any vendor quoting an Angular rate where it comes from and which country it covers.
How to vet an Angular developer
Four exercises cover most of what matters. Give the candidate the code and ask for a written review, not a live fix. Written reviews show what they notice without the pressure of a shared screen.
1. Change detection and signals review
Give the candidate a component that mutates state outside signals, holds a subscription that's never unsubscribed, and misuses an effect to copy one value into another. The bugs are quiet. The view stops updating in some cases, and the leaked subscription keeps running after the component is destroyed.
A candidate with modern Angular in production sees the state problem first and suggests moving it into a signal or a derived value. They'll connect the leak to the component lifecycle. Someone whose Angular stopped at 2020 reviews the template and misses the class.
2. RxJS exercise
Show a component with nested subscribe calls: one request inside the callback of another. Ask them to flatten it and explain which operator they'd use. The useful follow-up is switchMap against mergeMap for a search box that fires on every keystroke.
The good answer is specific. switchMap cancels the previous inner request, so stale results can't overwrite fresh ones, while mergeMap lets them all run. "They're similar" means the candidate has copied operators without understanding them.
3. NgModules to standalone migration judgment
Describe an app with forty NgModules and ask how they'd move it to standalone components. Don't look for a single right answer. Look for sequencing, such as leaf components first, shared modules next and the bootstrap last, and for a view on whether the whole thing should be done at once.
Weak candidates either propose a big-bang rewrite or say they'd leave it alone forever. A senior engineer knows the two styles coexist during the move and can say where they'd stop if the budget ran out.
4. Testing check
Ask what they'd run tests with in a new project, and why. The answer should name Vitest, the default for new CLI projects, and show awareness that Karma is still supported for existing suites.
Then hand them a component test written against the old stack and ask what they'd change if the project moved. This separates people who've maintained a Karma suite from people who understand what a test is for.
Angular interview questions that show real seniority
1. When would you use a signal and when an RxJS observable?
Tests whether they see signals as state and observables as streams over time. A good answer covers values you read synchronously in a template against events like keystrokes or websocket messages. Red flag: "signals replace RxJS."
2. Why would you run an app zoneless?
Tests understanding of what zone-based change detection does and what zoneless removes. They should be able to connect it to the benefits angular.dev lists, such as performance and debugging, rather than reciting them. Red flag: "because it's the default now."
3. Standalone components or NgModules?
Tests whether they've built with both. Listen for standalone as the default for new work and an honest account of when an NgModules codebase is better left alone. Red flag: treating NgModules as something nobody still maintains.
4. How does OnPush change detection work, and when does it bite you?
Tests whether they understand why a component skips a check, and what it means to mutate an object instead of replacing it. Red flag: sprinkling it everywhere without being able to say what it prevents.
5. How would you upgrade an app two major versions behind?
Tests whether they've done it. Good answers go one major at a time with ng update, check the Node and TypeScript ranges on the compatibility table, and plan for dependencies that lag. Red flag: "just bump the version in package.json."
6. How does dependency injection work, and where do you use inject()?
Tests whether they understand providers, scopes and why Angular is built around DI. Red flag: only ever using constructor injection and treating the injector as magic.
7. When would you not use Angular?
Tests honesty about tradeoffs. A good answer names a case where a small marketing site, an existing team with different skills or a heavy server-rendered content site makes another tool the better fit. Red flag: "always."
Staff augmentation vs full-time for an Angular hire
When the Angular work is enterprise internal tooling or a migration, it's usually a bounded project. A move off AngularJS, a dashboard rewrite or a jump across several majors has a clear end. That favours staff augmentation or a fixed-scope engagement over a permanent hire from day one.
A long-lived product with a big Angular frontend and a roadmap that runs for years is different. It needs someone who owns the architecture and will still be around to upgrade it in 12 months. Hire that person full-time.
If the API behind the app is on the JVM, our guide to hiring Java developers covers the backend half of a full-stack pairing.
Hiring timeline
We have no primary source for how long a direct Angular hire takes, so we won't quote one. Vendor pages publish time-to-hire figures, but they're marketing claims, not measurements.
Spec quality matters more than sourcing speed. An ad that pins the version, names the app type and says whether AngularJS or NgModules work is involved means the wrong candidates drop out before the first call, which shortens every stage after it.
FAQ
How much do Angular developers cost?
We don't publish an Angular-specific figure because no primary dataset gives one. Price moves with seniority, architecture ownership, backend overlap and the engagement model. Treat any vendor's Angular rate as a marketing number until they show how it was calculated.
AngularJS or Angular for a new hire?
Angular, and say so in the post. AngularJS support officially ended in January 2022. Hire AngularJS specialists only to maintain or migrate a legacy app, and test them on modern Angular if the migration is part of the job.
Do I need a React developer who can learn Angular?
Only if the Angular pool is too thin for your budget or timezone. A strong React engineer can work, but screen dependency injection, RxJS and the template syntax, because those don't carry over. We have no sourced figure for ramp-up time.
Which Angular version should the job post name?
The version you're actually on, or the one you'll land on after your planned upgrade. Per angular.dev, v22 is active, v21 and v20 are in LTS, and v2 to v19 are unsupported. If you're on v20, mention the LTS end date of 2026-11-28 and the upgrade work it implies.
Should I hire through staff augmentation or full-time?
Staff augmentation fits a bounded migration or a rewrite with an end date. Full-time fits a product with a long roadmap and a frontend that needs a permanent owner who'll handle each upgrade as it comes.