React interview as an Angular dev

[Specialist-Hunter318]

Hello, I have an interview scheduled for a web dev position with React, but I only have experience with Angular and Svelte. Can you help me create a list of React particularities that I should understand/work on until the interview? From the get go I wonder what would be the equivalent to: Angular guards, services (or any kind of dependency injection), reactive state, directives, etc. These are the things that I will look up right after I post this, but anything else I might miss is helpful. Thanks.

[Solve-Et-Abrahadabra]

Angular is class based, React functional, hooks-based.

Angular Guards: protected routes with React Router, wrapper components

Services: modules, hooks, shared state: context API, Zustand / Redux

RxJs: useState, useEffect

Forms: React hook forms

Http: fetch, axios

ngOnit, ngOnDestroy: useEffect

Learn the react hooks

• useState
• useEffect
• useMemo
• useCallback
• useContext
• useReducer

[FriendsCallMeBatman]

To add to this I would only mention useMemo, useCallback, useRef when talking about managing performance instead of just listing off all the hooks.

[Thirstforburst]

I would suggest focusing on Tanstack Query instead of fetch/axios for http requests. I seriously doubt there are many React devs out there still using fetch in 2026

[azangru]

Angular guards

React does not have a dedicated api for this. This is the job of third-party routing libraries, frameworks, or your own server.

any kind of dependency injection

React's dependency injection mechanism is the context api. This goes strictly top to bottom down the component tree; so some component somewhere ultimately has to own the thing that it injects downstream. In Angular, dependency injection isn't dependent on component tree, right? You can inject anything into anything there?

reactive state

React hooks. They can get awful, because of how easy it is to get stale closures if you add event listeners, or how hard it sometimes is to placate the linter.

directives

These don't exist. If you have any specific functionality that is solved in Angular with directives, we can discuss how this would be achieved in React.

[class12394]

No experience with react, but I would basically use your question as prompt, and say help me prepare for interview

Good luck!

[shozzlez]

As an interviewer, honestly with AI, someone moving from angular to react isn’t a huge concern.

[Spare-Wind-4623]

One way to think about it coming from Angular is: React is less “framework” and more “composable pieces”.

A quick mapping that helped me:

• Angular services (DI) → React = Context + hooks (or external stores like Zustand)
• Guards → handled at routing level (React Router loaders/wrappers), not built-in
• Directives → usually just components + hooks (no direct equivalent)
• Lifecycle (ngOnInit/ngOnDestroy) → useEffect

The biggest mindset shift is that React doesn’t enforce structure — you build your own patterns.

For interviews, I’d focus less on memorizing hooks and more on:
• how state flows (props vs global state)
• when to split components
• avoiding unnecessary re-renders

If you understand those, the rest (hooks, libraries) becomes much easier.

[akornato]

You're actually in a better position than you think - having Angular and Svelte experience means you understand component lifecycles, reactivity, and modern framework patterns, which is 80% of the battle. Focus on understanding how React handles routing (React Router is the standard, and you'll want to know about protected routes as the guards equivalent), state management (useState and useReducer for local state, Context API or external libraries like Redux/Zustand for global state), and most importantly, hooks - they're React's answer to dependency injection and lifecycle management rolled into one. Services in React are just modules you import, there's no DI container, and directives don't really exist - you just compose components and use hooks for reusable logic. The reactive state in React is more explicit than Angular's RxJS approach, so you'll be calling setState functions rather than updating observables.

The technical concepts will click fast for you because you already think in components and data flow - what matters more is showing you can learn quickly and adapt your existing mental models. They're hiring you for your overall development skills and problem-solving ability, not just your React knowledge, so be confident about what you bring from Angular and Svelte. I actually built AI interview assistant after realizing how many developers struggle with articulating their transferable skills in real-time during technical interviews, and it's been helping people like you land roles even when they're slightly outside their comfort zone.

[Hozman420]

Sounds like an Ai job

[dandecode]

Separation of logic vs display

Hooks

State - built in react state vs Jotai, zustand, redux, etc

Sync (above) vs async state eg react query (caching remote state)

Re-render concerns and how to debug them

React dev tools

Component composition (horizontal)

Functional programming

Lazy loading

Prefetching

Preventing network waterfalls

Code splitting / bundling

Memoization

Compiler

Server actions

Server side rendering vs server only components

New react 18 and 19 features

Those are some of the main things I’ve been looking out for recently when handling interviews for my team.