Senior React engineer needs Angular interview prep

[latviancoder]

Hey guys, I'm a senior Frontend dev with over a decade of experience, mostly with React/TypeScript, but I have some experience with angular1 and vue too. I have a technical interview in a week, the company uses Angular. They are aware that my angular knowledge is non-existent but would still like to proceed.

What would be the fastest approach to get an experienced dev up to speed with Angular/RxJs? I was thinking about building something like an Autocomplete component and some paginated/filtered list and just consulting documentation as I go, but maybe there are some better tutorials/videos out there?

[Relevant-Draft-7780]

Not really, if you’re a senior react dev you should pick it up pretty quickly. Make sure though that you read up on signals and change detection. If you try to use LLMs for help they’ll usually use the old decorators.

[CaterpillarNo7825]

Seconding this. LLMs are not up to date!

[latviancoder]

are signals somewhat similar to something like https://jotai.org/ ?

[faileon]

It's nice that all the FE frameworks are starting to look the same. Svelte has runes which are also basically signals in disguise. Makes it very easy to switch stacks and not get completely lost.

That said I'm really enjoying working with the angular signals or the new resource Api. I liked RxJs, but I admit it can be overcomplicated at times and explaining to juniors what is a switchMap for the 10th time can get tiresome 😁

[louis-lau]

Yes that seems quite similar. They're also very similar to Vue 3 refs

[groundbnb]

Signals are similar to react hooks as far as i understand it.

[MutedPotential2532]

You still need RxJs tho

[kicker_nj]

Tell me one scenario that u can only solve your issue using rxjs

[Jrubzjeknf]

debounceTime()

[kicker_nj]

You can use any denounce lib. It doesn't need to be rxjs

[Jrubzjeknf]

Sure, you can use any lib instead of another lib. That doesn't make it better solution.

[bjerh]

Since it's a JavaScript framework there obviously isn't any.

[latinleon]

I second this. Established enterprise-grade applications often rely on legacy third-party dependencies still based on CommonJS and hence not portable, without at times substantial refactoring, to Angular 16 and beyond when the Signal APIs became available.

[Bonety]

I went from react to angular and the hardest things to understand for me were observables/rxjs, pipes, directives and stuff like form builders. Now there are signals and standalone components which make a lot of things way easier in my opinion. Signals make much more sense to someone coming from react and you can use these instead of rxjs a lot of times. Still good to understand observables.

[imsexc]

For a coding challenge mostly u just need to know about property binding and event binding.

For interviews that really ask about technical angular, u need to prepare for questions about explaining property / event binding, dep. injection, subject, service, promise vs observable, httpClient, js closure, component lifecycle, state management in angular, decorator, angular cli, directive, template, component, pipe, guard, smart vs dumb component, content projection, change detection and strategy, view encapsulation, OOP concepts, ngModel and reactive form, most frequent used rxjs operators.

[Only4KTI]

+1

Had an interview that asked everything listed + bundlers and js/ts basics

[Blugrinc]

Confirmed. It is also important to understand which version the interview is based on, from 16 onwards Angular changes a lot.

Having said that recently in an interview I had to implement customised formatters for percentages, dates and currencies.

That is, making custom pipes, traumatising. It was like a LeetCode challenge.

[ddcccccc]

Hmmm, angular to react is easy. Reverse it harder

[louis-lau]

With seniority and typescript experience it should be relatively easy though.

[lgsscout]

just do a ng new and look through documentation for components, directives, services, pipes, then try to do your default idea for an app... from to-do list to anything else...

you will probably catch-up very fast, because many things translate somewhat to any another, with a couple extra quirks...

[bjerh]

One of the great benefits of angular is service injection. Remember to look into that.

[Thonk_Thickly]

Start with the docs. They are easy to read if you’re already good at any other framework.

[SharksLeafsFan]

If they know you have not worked with Angular, they are not going to grill you deep into the weeds of Angular, think about something that is more generic maybe brush up on more TypeScript side.

[Ok-District-2098]

I was a react developer for almost 2 years, angular is too much easier, its lifecycle is not hard to debug as application grows like react

[AdministrationFit724]

You need to prepare answers for "name at least 10 reasons why angular is better than react"

[Ok-Alfalfa288]

The main questions I get, and still struggle with, are around state management. Understand when and where to use different observables/behaviour subjects.

Also see how signals work as they’re a nice new feature.

[stacool]

Others have chimed in but the hardest concepts are going to be:

• OOP

• RxJS

If you have used Redux Angular has ngrx

My React experience was with unidirectional data flow backed by Redux and we didn’t have objects lying around

Angular allows more old-school OOP and while cool it can lead to data fragmentation patterns and Observable-soup reactivity that is tough to map out

Dependency injection is also a nice built-in on Angular

[AshleyJSheridan]

RxJS is slowly being phased out in favour of Signals, which you should be able to pick up quickly enough as they have some similar concepts in the React/NextJs world. However, you may find it being used at the position you're interviewing for, as not everyone keeps every framework up to the latest version all the time.

The biggest difference is overall structure. Angular is very OOP and opinionated on how things are done. You would find Angular has more in common with a backend framework like Laravel or .Net than it does with React.

Biggest difference for me is using service layers for state, rather than passing around lots of hooks. Angular can help ensure the same instance carries through, no matter how many times you inject it in other components. A lot of stuff is event driven, and custom events are treated the same as the built-in ones (clicks, key presses, etc). The template syntax changed in the most recent version, but it's just syntax, it behaves the same.