Dataford
Interview QuestionsInterview GuidesExperiencesCoaching
New
Pricing
Get started
Dataford
Popular roles
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Browse
Browse All RolesEvery role hub, from analyst to MLBrowse All CompaniesCompany-specific interview loopsAll Interview GuidesThe full guide library
Top questions by role
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Top questions by skill
SQLPythonStatisticsMachine LearningA/B TestingSystem DesignGenerative AIProduct SenseMetricsBehavioral
Browse all questions →Try a mock interview
Experiences
Practice
Mock InterviewsTimed interview simulations with feedbackCoaching1:1 coaching with people at your target companiesSuccess PathYour 6-week structured planModulesCurated lessons by topicWebinarsTalks from ex-Big Tech data leadsPlaygroundA free-form scratch editor
Learn
BlogInterview strategy and career adviceTech Job Market ReportHiring trends across data and AI rolesFor UniversitiesDataford for career centersAbout DatafordWho we are and how we build
Pricing
Build my plan

Refactor for Performance and Best Practices

MediumCoding00:00
Practice interviewer
In session
5 left
00:00

Your question is Refactor for Performance and Best Practices. Take a moment with it on the right.

Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).

You need to log in / sign up to chat or submit.

Problem

You're a software engineer at Wonderschool working on the childcare center dashboard. A teammate put together the component below to show a center director the roster of enrolled children, with a toggle to hide waitlisted kids. It technically works in a demo, but directors report the page flickers, sometimes shows the wrong child's row highlighted after adding a child, and occasionally throws a warning about updating state on an unmounted component when switching between centers quickly.

import { useEffect, useState } from "react";

interface Child {
  id: string;
  name: string;
  age: number;
  waitlisted: boolean;
}

function EnrollmentList({ centerId }: { centerId: string }) {
  const [children, setChildren] = useState<Child[]>([]);
  const [filters, setFilters] = useState({ hideWaitlisted: false });

  useEffect(() => {
    fetch(`/api/centers/${centerId}/children`)
      .then((res) => res.json())
      .then((data) => setChildren(data));
  });

  function addChild(child: Child) {
    children.push(child);
    setChildren(children);
  }

  const visible = children
    .filter((c) => !filters.hideWaitlisted || !c.waitlisted)
    .sort((a, b) => a.age - b.age);

  return (
    <ul>
      {visible.map((c, index) => (
        <li key={index}>
          {c.name} ({c.age})
        </li>
      ))}
    </ul>
  );
}

export default EnrollmentList;

Refactor this in your explanation: walk through every functional problem you'd fix and why the symptom the directors are seeing traces back to it, and describe the modern-React idioms you'd apply.