Skip to content
Axire Infotech Logo
SaaS and Web App Development

Hiring React JS Developers: 7 Interview Questions

By Axire Infotech11 min read

Hiring React JS Developers: 7 Interview Questions

Hiring React JS developers? Use these 7 interview questions, with strong vs weak answers, to vet candidates before you sign. See how to get started.

When you are hiring React JS developers for a first web app, seven questions will tell you most of what you need to know: can they show shipped work, why they pick their tools, how they handle web and mobile, how you will see progress, how they test, who owns the code, and what they would cut from version one. Below, each question comes with what a strong answer and a weak answer sound like.

You do not need to read code to use this list. You only need to listen for specifics. At Axire Infotech, a lean studio that has built web and mobile products since 2022, we work remotely with startups across Europe from India, with overlap into CET afternoons. We build with React, Next.js, Node.js and Supabase, and we hold ourselves to the same seven questions.

7 questions to ask before you sign a React JS developer

React is a library for building user interfaces, and it is used for single-page, mobile or server-rendered apps through frameworks built on top of it. That flexibility is why two developers who both say "I know React" can deliver very different results. The questions below separate them.

Ask them on a video call, not by email. Polished written answers are easy to produce. A live answer shows whether the person actually made the decisions they describe. Take notes, and score each answer using the table near the end.

1. Can you show me a React app you shipped, and what was your part in it?

Ask for a live React app the developer shipped, then ask what they personally built, what went wrong and what they changed. A strong answer names a working URL, a specific role and one trade-off. A weak answer shows screenshots, says "we" for everything and cannot name a decision.

Open the link while you are on the call. Click around on your phone as well as a laptop. Pages that load fast and behave on a small screen suggest care.

Strong: "I built the checkout flow and the account area. We dropped one feature because it delayed launch by three weeks." Weak: "The team did it all, I mostly helped." If the work is under an NDA, a good developer can still describe the problem, their role and the result in plain words.

2. Why would you choose Next.js, or plain React, for my product?

Choose plain React for a client-side interface and Next.js when you need fast first loads, search-friendly pages or server logic. A strong developer explains that choice in terms of your product and users. A weak one gives the same stack to every client and cannot say what it would cost you later.

Next.js is a React-based framework that adds server-side and static rendering. For a first web app with a public landing page, a login area and a dashboard, it often saves you from stitching several tools together. That is the stack we use most, alongside Node.js and a Postgres-based backend.

Strong: "Your marketing pages need to load fast and be indexable, and your dashboard needs login, so Next.js covers both in one project." Weak: "React is the best, so we use it for everything." Also notice whether they ask about your users before answering.

3. How do you keep one codebase working for web and mobile?

Ask which tool turns the web app into iOS and Android apps. At Axire, we start with Capacitor wrapped around a Next.js app and move to React Native when an app needs deeper native features. A strong answer names a tool and explains when it stops working. A weak answer promises everything.

Laptop browser window and a smartphone side by side showing the same app screen from one codebase

One codebase means you pay to build each feature once, and a fix reaches both platforms together. For a first product, that usually matters more than squeezing out the last bit of native polish. If you later need heavy camera work, background processing or complex animations, a developer who knows the limits will tell you early.

Strong: "We reuse the web app inside a native shell. If you need something the shell cannot do, we switch that part to React Native." Weak: "Don't worry, it will all just work." For more on this decision, our app development cost and feature complexity guide shows how each feature choice moves the budget. If mobile is part of your plan, our mobile app development service is built around this one-codebase approach.

4. How will I see progress each week?

Ask what you will receive every week and in what form. A strong developer commits to a written update plus a working link you can click, even when the build is unfinished. A weak one says you will see everything at the end, which leaves you finding problems after the money is spent.

We send every client a progress update each week. It covers what shipped, what is next and what needs a decision from you. You also get a link to the latest build, so you judge the product by using it, not by reading status reports.

Strong: "Every Friday you get a short summary and a staging link. If something slips, you hear about it that week." Weak: "We'll show you when it's ready." Weekly visibility is the cheapest insurance a non-technical founder has.

5. How do you test your code and handle bugs after launch?

Ask who tests the code, how, and what happens when a bug appears after launch. A strong answer describes automated checks, testing on real devices and a clear support period. A weak answer says "we test as we go" with no detail and treats post-launch fixes as a separate negotiation.

Every real product ships with bugs. What you are buying is the speed and manner of the fix. Our process runs in four steps: discovery and planning, design and prototyping, development and testing, then launch and support. Testing runs through the build, and support does not stop at launch day.

Strong: "Critical flows like sign-up and payment have automated tests, we test on actual phones, and we stay on for fixes after launch." Weak: "Bugs are rare with us." Nobody's bugs are rare. Be wary of anyone who says so.

6. Who owns the code, and which database will you use?

You should own the source code and hold access to the repository from day one, and the database should be a mainstream one such as Postgres. A strong developer agrees readily and explains the setup. A weak one keeps code on private accounts or uses obscure tools only they understand.

This question protects you if the relationship ends. If your code sits in an account you cannot open, switching developers becomes a hostage situation. Ask to be added to the code repository, the hosting account and the database on the first day, and get the ownership terms written into the agreement you sign.

Strong: "The repository is in your organisation, you are an admin, and the data lives in Postgres, which any developer can work with." Weak: "We'll hand it over at the end, once everything is paid." Common, mainstream tools also make it easier to hire your next React JS developer without starting over.

7. What would you cut from my first version?

A good React developer names features to delay and explains why. A strong answer protects one core user journey and pushes extras to a later release. A weak answer says yes to every idea, which usually means a longer build, a bigger bill and a first version that tests nothing.

Index cards sorted into keep and cut piles on a desk representing first-version feature scoping

First versions fail when they try to be finished products. The aim is to learn what users actually do. A developer who pushes back on your feature list is protecting your budget, not being difficult. Our MVP development work starts from exactly this conversation.

Strong: "Launch with sign-up, the core booking flow and payment. Admin reports and referral codes can wait until you have real users." Weak: "Sure, we can add all of it." If you want a longer checklist for the whole relationship, see how to evaluate a development partner.

What a React developer should know, and how to probe it

A React developer builds the user-facing part of an app from reusable components. You can check the core skills below with plain-language follow-up questions, even if you cannot read code.

  • Hooks: Ask, "How do you decide when to keep data inside a component and when to share it?" A strong answer mentions hooks such as state and effects and gives an example from their own work. A weak answer recites names with no example.
  • State management: Ask, "How did you manage data shared across many screens, and what would you change?" Listen for a reason for the choice and an honest downside.
  • TypeScript: Ask, "What bugs did types catch for you?" A strong answer gives a concrete case. A weak answer says "it is just best practice."
  • Performance: Ask, "Describe a slow page you diagnosed in React." Listen for how they measured the problem, what they changed and how they confirmed it worked.
  • Testing: Ask which parts of the app they test automatically and why those parts. This ties back to question 5.

Seniority: what to expect

A junior developer builds well-defined components with guidance and needs review. A mid-level developer owns whole features and explains trade-offs. A senior developer shapes the structure of the codebase, questions your feature list and spots risks early. For a first app with no technical lead on your side, favour someone who can answer the probes above from experience.

Worked example: scoring two candidates (hypothetical)

Suppose Candidate A shows a live URL, says "I built the account area, and we cut one feature to launch on time", and names Postgres and repository access from day one. Candidate B shows screenshots, says "we" throughout and will hand over code after final payment. Using the 0 to 2 scale, A might score 2 on questions 1 and 6. B scores 0 on both, so B is dropped whatever the other totals say.

A trade-off from our own projects

We start mobile apps with Capacitor around a Next.js app and move to React Native only when an app needs deeper native features. That trade-off buys one codebase and faster delivery, and it gives up some native polish.

Outsourcing React development: three extra checks

Many founders searching for React developers end up outsourcing, because a full-time senior hire is slow and costly for a first app. Outsourcing works well when you add three checks to the seven questions above. They cover time, communication and continuity.

  • Working-hour overlap: Ask for the exact hours the team is online during your day. Our team is in India and overlaps with CET afternoons, so European founders get live conversations, not next-day replies.
  • A named point of contact: You should know who answers your questions and who makes technical decisions. Anonymous ticket queues slow down a small project.
  • Response times in writing: We respond to all inquiries within one working day, including anything you send through our contact page. Whatever a provider promises, get it in writing before you sign.

If you are still weighing freelancers, an in-house hire and an agency, our guide on hiring React and Next.js developers without overpaying compares the options in more depth.

How to score the answers and choose between candidates

Score each answer from 0 to 2: 0 for vague, 1 for partly specific, 2 for specific with a reason attached. Add the totals out of 14. Any candidate who scores 0 on questions 1 or 6 should be dropped whatever the total.

Use the table as a quick reference during the call.

QuestionStrong signWeak sign
1. Shipped workLive URL, clear personal role, one trade-offScreenshots, "we" with no detail
2. React or Next.jsChoice tied to your users and pagesSame stack for every client
3. Web and mobileNames a tool and its limits"It will all just work"
4. Weekly progressWritten update plus a clickable build"You'll see it at the end"
5. Testing and supportTests on critical flows, real devices, support after launch"We test as we go"
6. Ownership and databaseRepository access from day one, PostgresCode held until final payment, obscure tools
7. What to cutProtects one core journey, delays extrasSays yes to everything

Tied scores are common. Break the tie on question 4. A developer who shows you work every week is the one who will notice trouble early and tell you about it.

Want our own answers to these seven questions for your product? See how our SaaS and web app development service takes a first web app from discovery to launch, and book a discovery conversation.

Contact

Planning a build like this?

The SaaS and Custom Web App Development page covers what we deliver and how we work with founders.

See SaaS and Custom Web App Development

Have a product to build? Tell us about it.

Book a short call. We will ask about your idea, give an honest view on scope and timing, and say if we are not the right fit.

Book a call

The calendar is a third-party service and may set cookies. It loads only when you ask for it.

Based in Ahmedabad, India, with a working day that overlaps UK and European mornings.