What we do
Tools
Industries
Department
How we workLet's talk →
Home/React Developer
React Development

Hiring a React Developer? First Find Out Where Your App Renders

"React developer" used to mean one skill set. Now a React app either runs entirely in the browser, or renders part of itself on a server through a framework such as Next.js or React Router, and the two need different experience. Work out which one you have, or need, before you write the job ad. That answer tells you which skills to test for in the interview.

Why the split matters now

For years most React apps started from Create React App and ran only in the browser. The React team deprecated Create React App in February 2025, and its docs now recommend starting new apps with a framework, or with a build tool such as Vite if you want to assemble the pieces yourself.

Frameworks brought Server Components with them: parts of the page that run on the server, fetch their own data and send finished HTML, with 'use client' marking the parts that need to run in the browser. A developer who has only built browser apps has never had to decide where that line goes. A developer who has only built Next.js marketing sites may never have managed heavy client state, like a dashboard with filters, drafts and live updates.

Neither is a better developer. They're different hires, and plenty of job ads ask for one while describing the other.

What you are building, and the React experience it calls for

What you are building Likely setup Hire someone who has
An internal dashboard or admin tool behind a login A browser-only app on Vite, or React Router in SPA mode Managed a lot of client state and cached server data, with a library such as TanStack Query rather than hand-written effects.
A public site or store that has to rank in search A framework with server rendering, such as Next.js Decided which components stay on the server, and dealt with caching and revalidation when data changes.
A customer portal that is both public and logged in A framework, with heavy client components behind the login Handled authentication on the server and in the browser without leaking data between users.
A React front end on an existing backend you keep Whatever fits the backend, often a Vite app calling its API Agreed API contracts with a backend developer and handled errors and loading states for every call.
An iPhone and Android app as well React Native, sharing logic but not screens Shipped to the app stores. Web React experience alone is not the same job: see React Native developers.

Interview probes that only make sense for React

Generic coding tests tell you someone can write JavaScript. These tell you whether they understand how React behaves.

  • Show me an effect from your last project you could have deleted.

    React's own docs have a page called "You Might Not Need an Effect". Developers who've read it stop using useEffect to copy one piece of state into another, which is the most common source of extra renders and stale values.

  • Why does this list need a key, and why not the array index?

    Index keys break when items are reordered or removed: the wrong row keeps its typed text or checkbox. A good answer mentions stable IDs from the data.

  • This page refetches every time I switch tabs. Where would you look?

    You want to hear about the dependency array, cached server data, or where the component sits in the tree. "Add a useMemo" without asking why is a weak answer.

  • Where would you put 'use client' in this page, and what would it cost?

    Only for framework roles. Putting it at the top of every file works, but it sends all the code to the browser and gives up most of what server rendering was for.

  • Two components need the same data. Lift it, use context, or fetch it twice?

    There's no single right answer. A thoughtful one weighs re-renders, how often the data changes, and whether a data-fetching cache already dedupes the request.

  • How would you upgrade this app to the current React version?

    Look for a plan: read the upgrade guide, run the codemods, upgrade libraries that pin old React versions, and test the screens that matter, rather than "bump the version and see".

What we find when we open an inherited React app

Most React work that reaches n-frames is an existing app whose original developer has moved on. These come up again and again.

Still on Create React App

How you'll know: react-scripts in package.json, and builds that print deprecation warnings or block newer libraries.

Fix: Move to Vite for a browser-only app, or to a framework if the app needs server rendering. The components mostly carry over. The build config, environment variables and test runner are what change.

Effects feeding effects

How you'll know: Several useEffect calls that each set state the next one watches, and screens that flicker or show old values for a moment.

Fix: Calculate derived values during render, and move data loading into the framework's loaders or a fetching library that handles caching and cancellation.

One context that re-renders everything

How you'll know: Typing in one field makes the whole page lag, because a single context holds the user, the theme, the cart and the form.

Fix: Split context by how often each value changes, or move fast-changing state down to the components that use it.

'use client' at the top of every file

How you'll know: A Next.js app that ships as much JavaScript as a browser-only app would.

Fix: Move the boundary down to the interactive pieces, such as forms, menus and charts, so the rest renders on the server.

Data fetched in an effect with no cleanup

How you'll know: Switch customers quickly and the screen shows the previous one's details.

Fix: Cancel or ignore stale requests, or let a fetching library track which response belongs to which request.

Let's talk

React work, staffed for the kind of app you have

n-frames builds and maintains React apps on Vite, Next.js and React Router, with more than one developer who knows each codebase, plus the backend and integrations the screens depend on. We read your existing code before quoting, and the quote is free.

Put React developers on my app →

Questions people ask

Do you handle the backend too, or just the React front end?

Both, when the job needs it. React screens are only as good as the data behind them, so we often build or fix the API, or connect the app to the CRM, store or accounting system it reads from. A full stack engagement covers both sides in one quote.

What happens when React's own tooling changes and breaks an old project?

We upgrade the build setup and dependencies on purpose, in small steps, rather than letting the app drift until one routine update turns into a rewrite. Moving off Create React App is the most common version of this right now.

Our last developer's code is hard to follow. Can you work with that?

Usually. We read the codebase first, run it locally, and list what's fragile before changing anything. If a partial rebuild is cheaper than patching, the estimate shows both so you can compare.

Is the quote actually free, or is there a catch?

It's free, with no obligation. You get a written estimate based on what the React app has to do and what it connects to.

Should a new app use Next.js, or is plain React enough?

If the pages are public and need to load fast and rank in search, a framework is the safer default. If everything sits behind a login, a browser-only app on Vite is simpler to host and often enough. Vue and Angular are worth a look if your team already knows them.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.