How to hire a freelance React developer: skills, questions and red flags

React is the most popular way to build modern web interfaces, which means there are a lot of React developers on the market. That is good news and bad news. You have plenty of choice, but the gap between someone who has followed a tutorial and someone who can build a fast, maintainable product is huge.

This guide walks through what to look for, how to test it and how to avoid the most common hiring mistakes.

Start with what you actually need

"A React developer" can mean very different jobs. Before you write the brief, decide which of these you need:

• Product UI developer: builds screens, forms and flows from designs. Strong on components, state and accessibility.
• Front-end architect: sets up the project structure, data fetching, design system and performance budgets.
• Full-stack React developer: works across React and a back end such as Node.js, often with Next.js. See full-stack developers.
• React Native developer: builds mobile apps with React. Related, but a different skill set. See React Native.

Being specific about the role is the single best way to get relevant candidates. Our guide to writing a freelance job brief covers the rest.

The skills that matter

Core React

• Components, props and state, and knowing when to split a component
• Hooks, including effects and their pitfalls (stale state, missing dependencies, unnecessary re-renders)
• Forms, validation and error states
• Data fetching and caching, whether with a framework, a library or server components

The ecosystem around React

• TypeScript: most serious React codebases use it now. See TypeScript developers.
• A framework: Next.js or a similar framework for routing, rendering and deployment.
• Styling: CSS modules, Tailwind or a component library, and the discipline to keep styles consistent.
• Testing: component tests and a few end-to-end tests for critical flows.

Things that separate senior developers

• Performance: they know why a page is slow and how to measure it, not just how to add memoization everywhere.
• Accessibility: keyboard navigation, focus management, labels and contrast.
• Architecture: a codebase that a second developer can understand in a day.
• Product sense: they ask what the user is trying to do before building the screen.

How to test React skills

Skip trivia questions about lifecycle methods. Instead, use one of these:

1. Code review exercise. Give them a small component with a few real problems (an effect with a missing dependency, an inaccessible button, a list without keys) and ask them to review it. You will learn more in 30 minutes than in an hour of questions.
2. Paid trial task. A small, real piece of your product, paid at their normal rate. See paid trial projects.
3. Walkthrough of past work. Ask them to share their screen and explain a codebase they built: structure, trade-offs, what they would change.

Interview questions that work

• "How do you decide where a piece of state should live?"
• "Tell me about a performance problem you fixed in a React app. How did you find it?"
• "How do you structure a project so it stays maintainable as it grows?"
• "How do you make a custom dropdown accessible?"
• "When would you not use React for a project?"

Strong candidates answer with examples from real projects and talk about trade-offs. Weak candidates recite documentation.

Red flags

• A portfolio of tutorial clones (to-do apps, weather apps) and nothing shipped to real users
• No TypeScript or testing experience at all for a senior role
• Adding libraries for everything, including problems React solves on its own
• Ignoring accessibility entirely
• Vague answers about who built what on team projects

Rates and engagement models

Rates depend on seniority, region and how much architecture work is involved. Senior developers who can own a front end end to end cost more per hour but usually cost less per feature, because they make fewer wrong turns. For a rough budgeting framework, see the real cost of hiring freelancers.

Most React engagements fit one of three shapes: a fixed-scope build (a new feature or MVP), an ongoing part-time role alongside your team, or a short audit to fix performance and code quality.

Hire a vetted React developer

Every React developer in the HireCurated network has passed a technical review and a live interview. See React developers or request a shortlist and get matched within 48 hours.