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
ExperiencesCoaching
New
Practice
Mock InterviewsTimed interview simulations with feedbackSuccess 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
Get started
Plan Debugging for Issues
00:00
5 left

Plan Debugging for Issues

HardPython

Problem

How to plan debugging for specific issues?

Given issue-check names and prerequisite relationships, return a valid debugging order that performs every prerequisite before the check that depends on it. If multiple checks are available, choose the lexicographically smallest name; return an empty list when the prerequisites contain a cycle.

Function signature: plan_debugging(checks, dependencies). checks is a list of unique strings, and each dependency is [prerequisite, check]. Return a list of check names.

Constraints

  • 1 <= len(checks) <= 10^4
  • 0 <= len(dependencies) <= 2 * 10^4
  • All check names are unique strings
  • Every dependency references names in checks
  • A dependency is represented as [prerequisite, check]
  • Duplicate dependency pairs do not occur

Function Signature

def plan_debugging(checks, dependencies):
Interviewer

Your question is Plan Debugging for Issues. Start with the requirements in the Question tab.

Run and submit as often as you like. When you're ready, talk me through your approach or go straight to the code.

You need to log in / sign up to run or submit.
Code
Sign up free to run your codeLog inLn 2
Run your code to see test output here.