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

Debug Memory Leaks and Bottlenecks

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

Your question is Debug Memory Leaks and Bottlenecks. 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

Mercari's marketplace app has an infinite-scroll listing feed: as a shopper searches and scrolls, new product cards load in and live prices update over a WebSocket. QA reported the tab's memory climbing steadily the longer someone browses, and the feed feeling laggier after switching search terms a few times. Here is the component.

function ListingFeed({ searchQuery }) {
  const [listings, setListings] = useState([]);
  const [loading, setLoading] = useState(false);

  useEffect(() => {
    setLoading(true);
    fetch(`/api/listings?q=${searchQuery}`)
      .then((res) => res.json())
      .then((data) => {
        setListings(data.results);
        setLoading(false);
      });

    const priceSocket = new WebSocket('wss://mercari.example.com/price-updates');
    priceSocket.onmessage = (event) => {
      const update = JSON.parse(event.data);
      const updated = listings.map((item) =>
        item.id === update.id ? { ...item, price: update.price } : item
      );
      setListings(updated);
    };

    const scrollHandler = () => {
      if (window.innerHeight + window.scrollY >= document.body.offsetHeight - 200) {
        loadMoreListings(searchQuery);
      }
    };
    window.addEventListener('scroll', scrollHandler);
  }, [searchQuery]);

  return (
    <div>
      {loading && <p>Loading...</p>}
      {listings.map((item, index) => (
        <ListingCard key={index} item={item} />
      ))}
    </div>
  );
}

Walk through what is leaking memory and what is causing the rendering bottleneck, and explain what you would change and why.