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
Offline ATM Refill Task Architecture
00:00
5 left

Offline ATM Refill Task Architecture

HardPython

Problem

Design the complete client-side architecture for a system that assigns and tracks ATM refilling tasks for field workers, including offline synchronization.

For this coding exercise, implement the synchronization core as a pure function. Merge local and remote task snapshots, apply pending offline field operations deterministically, ignore operations already acknowledged by the server, and return the merged tasks plus operations that still require upload.

The function receives dictionaries keyed by task ID and returns { "tasks": ..., "pending_ops": ... }. Each task contains status, assignee, per-field timestamps, version, and optional applied_ops; each operation contains op_id, task_id, field, value, and ts.

Constraints

  • 1 <= number of tasks <= 500
  • 0 <= number of pending operations <= 2,000
  • Each operation targets exactly one task field
  • Task fields are limited to status and assignee
  • Timestamps are non-negative integers
  • Operation IDs are unique within the pending operation list

Function Signature

def reconcile_tasks(local_tasks, remote_tasks, pending_ops):
Interviewer

Your question is Offline ATM Refill Task Architecture. 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.