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
Batch Commit Function Implementation
00:00
5 left

Batch Commit Function Implementation

HardPython

Problem

Figma multiplayer edits may depend on earlier edits, such as creating a frame before adding a child layer. Implement commit_batch to divide edits into ordered commit batches while ensuring every edit is committed strictly after all of its dependencies.

Each batch may contain at most max_batch_size edits. Among edits that are currently eligible, preserve their original input order. Edits that become eligible while constructing a batch must wait until the next batch. Assume the dependency graph is valid and acyclic.

Formal Specification

Given a list operations, where each operation is a dictionary with:

  • id: a unique string identifying the edit
  • depends_on: a list of operation IDs that must be committed earlier

Return a list of batches. Each batch is a list of operation IDs. Every dependency must appear in an earlier batch, and no batch may exceed max_batch_size.

Constraints

  • 1 <= len(operations) <= 10^5
  • 1 <= max_batch_size <= 10^4
  • Operation IDs are unique strings.
  • Every dependency refers to an operation in operations.
  • The dependency graph is acyclic.

Function Signature

def commit_batch(operations, max_batch_size):
Interviewer

Your question is Batch Commit Function Implementation. 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.