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
Wallet System with Transactions
00:00
5 left

Wallet System with Transactions

HardPython

Problem

Take-home: build a full-fledged wallet system with CRUD for wallet and transactions, transfer logic with validations (sufficient balance, atomicity), and role-based access for admins and users (Node.js, Express, MongoDB, Redis optional).

Asked in the Round 2: Take-home assignment stage. Followed by a walkthrough round. Reported follow-ups: How did you handle transaction consistency and failure rollback?; REST API structure, security, and middleware handling.

For grading, implement process_wallet_operations(operations). Each operation is a dictionary containing an actor, role, action, and action-specific fields. Return one result per operation. Support wallet CRUD, transaction creation and deletion, balance validation, atomic transfers, and admin/user authorization. Do not mutate state when an operation fails.

Constraints

  • 1 <= operations.length <= 10^4
  • Wallet IDs, actor IDs, and transaction IDs are non-empty strings
  • Amounts are finite non-negative integers or floats
  • Wallet balances must never become negative
  • Every failed operation must leave wallet and transaction state unchanged
  • Transaction IDs are generated in creation order

Function Signature

def process_wallet_operations(operations):
Interviewer

Your question is Wallet System with Transactions. 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.