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
EventEmitter Implementation
00:00
5 left

EventEmitter Implementation

MediumPython

Problem

Box web surfaces such as Box Preview and Box Notes may need to notify multiple UI components when a file event occurs. Implement an EventEmitter class with ordered listener registration, event emission, and listener removal.

Implement:

  1. on(event, callback): Register callback for event. Listeners execute in registration order. The same callback may be registered more than once.
  2. emit(event, *args): Invoke every listener registered for event, passing all supplied arguments. Emitting an event with no listeners does nothing.
  3. off(event, callback): Remove the first matching registration of callback for event. If no matching registration exists, do nothing.

During an emission, dispatch a snapshot of the listeners that existed when emit began. Therefore, a listener added or removed while callbacks are running must not change the current dispatch, but it must affect later emissions.

For automated testing, also implement run_event_emitter(operations). Each operation is a dictionary with op equal to on, off, or emit. on and off contain event and listener; emit contains event and an args array. The helper should use callbacks identified by listener names and return an array of [listener, args] entries in invocation order.

Constraints

  • 1 <= operations.length <= 10^4
  • Event and listener names are non-empty strings
  • Each args array contains at most 10 values
  • A listener can be registered multiple times for the same event
  • off removes at most one registration

Function Signature

def run_event_emitter(operations):
Interviewer

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