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
Debug a Complex Issue
00:00
5 left

Debug a Complex Issue

MediumPython

Problem

How do you approach debugging a complex issue in your code?

Implement a focused debugging utility that compares an actual execution trace with an expected trace and identifies the first differing snapshot. Return -1 when both traces match exactly.

Use find_first_trace_mismatch(actual, expected), where each trace is a list of comparable snapshots, and return the zero-based mismatch index.

Constraints

  • 0 <= actual.length, expected.length <= 10^5
  • Each snapshot is a comparable Python value
  • Return the smallest zero-based mismatch index
  • Return -1 only when the traces are identical

Function Signature

def find_first_trace_mismatch(actual, expected):
Interviewer

Your question is Debug a Complex Issue. 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.