#1 India's Top IT Training Institute

×

About Uncodemy

Know more about who we are and what we stand for.

About Us

About Us

Discover our mission to equip individuals with essential IT skills and industry expertise.

Read More →
UnCodeMy Gallery

UnCodeMy Gallery

Explore highlights from our IT training sessions and success stories.

Read More →
×

Free Resources

Learn, practice and plan your career — bilkul free.

Tutorials

Tutorials

Step-by-step written tutorials to learn any technology at your own pace.

Read More →
Free Counselling

Free Counselling

Book a free video counselling session and pick the right course for you.

Read More →
Online Compiler

Online Compiler

Write, run and test your code online — no setup required.

Read More →

Interview Insights · React Developer

Why React Developer Candidates Freeze on the Simplest Questions

A candidate explains React Query caching well, then goes blank when I ask 'what is state?'. It happens more than you would think. Simple questions feel dangerous because there is no clever answer to hide behind.

Tracks
Simple Question Test · Live Interactive
Question
—
What I ask
Frozen reply
—
What I often hear
Calm reply
—
What works
Question→Plain words→Example→Why it matters
Click a simple React question to compare a frozen reply with a calm one built from plain words and an example.

Home / Tutorials / Career Guides / Why React Developer Candidates Freeze on the Simplest Questions

Interview Insights · React Developer

Why React Developer Candidates Freeze on the Simplest Questions

MOVE 1MOVE 2MOVE 3MOVE 4DefineOne plain sentenceNo jargonClearExampleTiny componentReal useConcreteWhy it mattersWhat breakswithout itDepthCommon mistakeOne pitfallAnd the fixExpert
Answer any basic question in four short moves: a plain definition, a tiny example, why it matters, and one common mistake.

Quick summary — Simple React questions

Candidates freeze on simple React questions because they try to sound advanced instead of answering plainly. Basic questions such as 'what is state?', 'why do lists need keys?' or 'what is the difference between props and state?' feel like traps. Many candidates think the interviewer expects a deep, perfect answer, so they search for impressive words and lock up. In reality, I ask simple questions to see whether you understand the foundation clearly. A plain definition, a tiny example and one reason it matters is exactly what I want. This page gives you a method and worked answers for the questions that cause most freezes.

In this guide you will learn:

  1. Why simple questions cause more freezes than hard ones
  2. A four-move method for answering any React basic
  3. Worked answers for state, props, keys and controlled inputs
  4. Code that shows the key bug many candidates cannot explain
  5. A daily drill to make basics automatic

SECTION 01Why simple questions feel harder than hard ones

When I ask a hard question, such as how to avoid unnecessary re-renders in a large list, candidates relax a little. They know nobody expects a perfect answer, so they think aloud. When I ask 'what is a component?', the pressure jumps. The candidate feels they must not get it wrong, and they also worry that a simple answer will sound too basic.

That double pressure causes the freeze. The fix is to accept that a simple question deserves a simple answer, delivered calmly, and then let the interviewer go deeper if they want to.

Thought during the freezeWhat actually happensBetter thoughtEffect on the answer
They expect something deepThey want the foundationPlain and correct is enoughStarts quickly
A simple answer sounds juniorClarity sounds seniorClear words show understandingConfident tone
I must not miss any detailThey will ask for detailsStart small, expand if askedShort, structured
I knew this yesterdayMemory blocks under stressUse an example to recall itRecovers the thread
Me: What is state in React?

Candidate: State is... it is the useState hook.
It is like... the state management. We use Redux
also for state. It is very important in React.

Me: Can you give an example?

Candidate: (long pause) Like a counter?

(Mixed terms, no definition, no example until pushed.)
state-answer.txt

The calm answer takes about twenty seconds. It is not clever, but it shows a clear mental model, and it hands me several directions for my next question.

Key insight: Simple questions are not traps. They are the interviewer checking the foundation before building on it. A clear foundation makes every later answer more believable.

SECTION 02The key question, with the bug it prevents

'Why do lists need a key?' is one of the most common freezes I see. Many candidates answer 'to remove the console warning', which is true but misses the point. Keys tell React which item is which between renders, so it can keep the right state with the right item when the list changes.

The clearest way to understand this is to see the bug that appears when you use the array index as a key and then remove or reorder items. If you can explain this bug, you will never freeze on the key question again.

Key choiceWhen it worksWhen it breaksWhat the user sees
Array indexStatic list that never reordersItems removed, inserted or sortedTyped text jumps to the wrong row
Stable ID from dataAlmost alwaysIf IDs repeatCorrect rows keep their state
Math.random()NeverEvery renderInputs reset and lose focus
Item name or labelNames are unique and fixedTwo items share a nameDuplicate key warning and odd updates
import { useState } from "react";
import TaskRow from "./TaskRow";

export default function TaskList() {
  const [tasks, setTasks] = useState([
    { id: "t1", title: "Write tests" },
    { id: "t2", title: "Fix login bug" },
    { id: "t3", title: "Update README" },
  ]);

  const remove = (id) => setTasks((ts) => ts.filter((t) => t.id !== id));

  // BUG version: key={index}
  // Each TaskRow keeps its own note input state.
  // Remove the first task and the notes shift up one row.
  //
  // FIX: key={task.id}, so React matches rows by identity.
  return tasks.map((task) => (
    <TaskRow key={task.id} task={task} onRemove={remove} />
  ));
}
TaskList.jsx

Try this yourself: give each row an uncontrolled text box, type into the first one, then remove it with index keys. Seeing the text jump once is enough to remember the answer for good.

Remember: When you answer a basic question, mention the bug it prevents. 'Without stable keys, typed text can move to the wrong row' shows real understanding in one sentence.

SECTION 03Worked answers for the other common freezes

A handful of other basics cause most of the remaining freezes: props versus state, controlled versus uncontrolled inputs, what JSX actually is and what a re-render means. Each one has a short, plain answer and a small example that makes it stick.

Prepare these with the same four moves: define, example, why it matters, common mistake. You do not need to memorise wording. You need to own the idea well enough to say it in your own words under pressure.

QuestionPlain definitionTiny exampleCommon mistake
Props vs state?Props come from the parent; state is owned by the componentA Button gets a label prop; a Dropdown owns isOpen stateCopying a prop into state and letting it go stale
Controlled input?Input value comes from state and changes via onChangevalue={email} with setEmail on changeSetting value without onChange, so typing does nothing
What is JSX?Syntax that compiles to function calls creating elementsA tag becomes a React element objectThinking it is HTML inside JavaScript
What is a re-render?React calling the component again to get new outputState changes, the function runs againThinking a re-render always updates the DOM
import { useState } from "react";
import TextInput from "./TextInput";

// Controlled: React state is the single source of truth
export default function EmailField({ onValid }) {
  const [email, setEmail] = useState("");
  const isValid = /^[^\s@]+@[^\s@]+\.[^\s@]+$/.test(email);

  const handleChange = (e) => {
    const next = e.target.value.trimStart();
    setEmail(next);
    if (/^[^\s@]+@[^\s@]+\.[^\s@]+$/.test(next)) onValid(next);
  };

  return (
    <TextInput
      label="Email"
      value={email}
      onChange={handleChange}
      error={email && !isValid ? "Enter a valid email" : ""}
    />
  );
}
EmailField.jsx

Notice that isValid is not stored in state. It is calculated from email on every render. Mentioning this when you explain controlled inputs shows that you also understand derived values, which is a natural follow-up question.

Pro move: If you blank on a definition, start with the example instead: 'For instance, a dropdown's open or closed value...'. The example often brings the definition back within seconds.
How Uncodemy helps: Uncodemy trainers cover React Developer interview answers as part of the React JS Training Course: project reviews, mock interviews and resume feedback, with placement assistance once you are interview-ready.

SECTION 04Daily drill to make React basics automatic

Freezing is a pressure problem, and repetition reduces pressure. Use this drill every day for two weeks before interviews. It takes fifteen minutes and needs only a phone recorder.

DAILY BASICS DRILL

1. Pick 5 cards from the question list.
2. For each, answer aloud in 4 moves:
     Define  -> one plain sentence
     Example -> tiny component or situation
     Why     -> what breaks without it
     Mistake -> one common pitfall
3. Record. Keep each answer under 45 seconds.
4. Play back. Mark any answer that started with
   'it is like...' or 'basically...'.
5. Redo marked answers once.
react-basics-drill.md

SECTION 05Habits that stop the freeze before it starts

These small habits lower the pressure of basic questions and keep your answers short and clear.

  • Expect the basics — Assume every React interview will include simple questions. Expecting them takes away most of the surprise.
  • Keep your own examples — Link each basic idea to something in your own projects so you always have an example ready.
  • Avoid filler words — Starting with 'basically' or 'it is like' often leads to rambling. Start with the definition instead.
  • Stop after the core answer — Give the four moves and stop. Interviewers prefer asking a follow-up to sitting through a lecture.
  • Practise with a real person — Answering a friend or a trainer adds the pressure that recording alone cannot. A mock interview with an Uncodemy trainer is a good way to do this.
Pro tip: Pick the three basics you fear most and teach them to a friend who does not code. If you can explain them in plain words to a non-developer, an interviewer will be easy.

SECTION 06Interview Q&A — Simple React questions

Q1What is the difference between props and state?

Props are inputs passed from a parent component and are read-only inside the child. State is data the component owns and can change with its setter. For example, a Button receives its label as a prop, while a Dropdown keeps whether it is open in state. Copying a prop into state is a common mistake because the copy can go stale.

Q2Why should you not use the index as a key?

Because when items are removed, inserted or reordered, indexes move to different items. React then matches the wrong old item to the new one, so local state such as typed text can appear on the wrong row. A stable ID from the data avoids this. Index keys are only safe for lists that never change order.

Q3What is a controlled component?

An input whose value comes from React state and updates through onChange, so React is the single source of truth. It makes validation and formatting easy. An uncontrolled input keeps its own value in the DOM, and you read it with a ref when needed, which can be simpler for basic forms.

Q4What actually happens in a re-render?

React calls the component function again to get new output, compares it with the previous output and updates only the parts of the DOM that changed. So a re-render does not always mean the DOM changes. State changes, parent re-renders and context changes are common triggers.

Q5Is JSX the same as HTML?

No. JSX is a syntax that compiles to JavaScript function calls which create React element objects. It looks like HTML, but uses className instead of class, camelCase event names and curly braces for JavaScript expressions.

SECTION 07Test yourself — Simple React questions quiz

Five questions. No sign-up.

0 / 5

Pick an answer to see why it is right or wrong.

SECTION 08Frequently asked questions

What are the basic React interview questions for freshers?

Common ones include what is a component, what is state, props versus state, why lists need keys, what is JSX, controlled versus uncontrolled inputs, what useEffect does and what the virtual DOM is.

Why do I go blank in interviews even when I know the answer?

Stress narrows attention, and many candidates try to build a perfect answer before speaking. Starting with a simple definition or an example from your own work breaks the freeze.

How do I explain state in a React interview?

Say that state is data a component owns that can change over time, and that React re-renders the component when it changes. Give a small example, such as whether a dropdown is open, and mention one mistake, such as storing derived values.

Is using index as key always wrong in React?

No. It is acceptable for static lists that are never reordered, filtered or edited. For lists that change, use a stable unique ID from the data to avoid state appearing on the wrong item.

How can I practise React basics before an interview?

Record yourself answering one basic question at a time using a definition, an example, why it matters and a common mistake. Build tiny demos, such as the index key bug, to see each idea in action.

How can I prepare for React Developer interview answers with a trainer?

Yes. Uncodemy's React JS Training Course in Noida (classroom and online) includes live projects, one-to-one mock interviews and resume reviews, so you practise React Developer interview answers with trainer feedback before the real interview. You can book a free demo class from this page to see how the sessions work.

Classroom & online · Noida

Master React basics until they feel easy

Our React JS Training Course builds strong React foundations through small demos, projects and mock interviews, so simple questions never catch you off guard.

Talk to a counsellor for current fees
  • Core React and JSX
  • Hooks with hands-on demos
  • Mock technical interviews
  • Weekday & weekend batches