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 setTimeout Output

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

Your question is Debug setTimeout Output. 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 interviewing as a frontend engineer at Faculty.ai. The team shows you a small TypeScript module from an internal dashboard that polls a model-training job for status and schedules a fixed number of retries before giving up. It was written to retry with indices 0, 1, 2, 3 and then give up, but the on-call engineer says the console log never looks like that in practice.

const MAX_RETRIES = 3;

console.log("start");

for (var i = 0; i <= MAX_RETRIES; i++) {
  setTimeout(() => {
    console.log("retry attempt", i);
  }, 0);
}

const giveUpId = setTimeout(() => {
  console.log("giving up");
}, 0);

Promise.resolve()
  .then(() => console.log("status check queued"))
  .then(() => console.log("status check sent"));

console.log("end");

function cancelPolling() {
  clearInterval(giveUpId);
}

cancelPolling is defined but never called in this snippet. Write out exactly what gets printed to the console, in order, and explain the underlying cause of every line that doesn't match what the author intended. Then explain, as if talking a teammate through it, how you'd fix each cause.