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
Topological Ordering for Dependencies
00:00
5 left

Topological Ordering for Dependencies

MediumPython

Problem

An AMD ROCm build pipeline contains tasks such as kernel compilation, linking, testing, and packaging. Each dependency is given as [prerequisite, task], meaning the prerequisite must be completed before the task.

Implement dependency_order(tasks, dependencies) to return the lexicographically smallest valid completion order. If the dependency graph contains a cycle, return an empty list because no valid order exists. Tasks with no dependencies must still appear in the result. Duplicate dependency pairs should be treated as one dependency.

Formal Specification

  • Input tasks: a list of unique strings representing all tasks.
  • Input dependencies: a list of two-element lists [prerequisite, task].
  • Output: a list containing every task exactly once in valid dependency order, or [] if a cycle exists.
  • The lexicographically smallest order is required when multiple valid orders exist.

Constraints

  • 1 <= len(tasks) <= 2 * 10^5
  • 0 <= len(dependencies) <= 4 * 10^5
  • Task names are unique non-empty strings of length at most 50
  • Every dependency references tasks in tasks
  • Duplicate dependency pairs may occur

Function Signature

def dependency_order(tasks, dependencies):
Interviewer

Your question is Topological Ordering for Dependencies. 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.
CodePython 3
Sign up free to run your codeLog inLn 2
Run your code to see test output here.