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
Complete Airflow-like Task Pipeline Skeleton
00:00
5 left

Complete Airflow-like Task Pipeline Skeleton

HardPython

Problem

Given an incomplete object-oriented skeleton that simulates an Airflow-like task pipeline where tasks have dependencies, complete it and add the missing APIs.

Asked in the virtual onsite stage. OOD coding round; the remainder of the prompt is hidden behind the points wall.

Implement Task and Pipeline. A task has a unique name and may depend on other tasks. The pipeline must support adding tasks, adding dependencies, and returning a valid execution order. Return None when a dependency is missing or the graph contains a cycle. When multiple tasks are ready, preserve task insertion order.

I/O Contract

run_pipeline(task_specs) receives a list of dictionaries with name and dependencies fields. It returns a list of task names or None.

Constraints

  • 0 <= task_specs.length <= 1000
  • Each task name is a non-empty string
  • Task names are unique
  • Each dependency name is a string
  • A task may list a dependency at most once
  • The required output preserves insertion order among simultaneously ready tasks

Function Signature

def run_pipeline(task_specs):
Interviewer

Your question is Complete Airflow-like Task Pipeline Skeleton. 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.