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

Refactor for Performance and Readability

MediumCoding00:00
Practice interviewer
In session
5 left
00:00

Your question is Refactor for Performance and Readability. Take a moment with it on the right.

Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).

You need to log in / sign up to chat or submit.

Problem

Persistent is running an account migration for a client moving off a legacy CRM. A helper function takes a batch of account records pulled from the old system and a blacklist of account IDs that should be skipped, and returns the IDs that were migrated. It works on a demo dataset of fifty accounts, but on the client's real export of around two hundred thousand accounts the migration job that used to take minutes now runs for hours and someone eventually notices the result looks wrong on a second run.

processed = []

def migrate_accounts(records, blacklist):
    global processed
    result = ""
    for r in records:
        skip = False
        for b in blacklist:
            if r["account_id"] == b:
                skip = True
        if skip:
            continue
        acc = {}
        acc["id"] = r["account_id"]
        acc["name"] = r["name"]
        acc["region"] = r["region"].upper()
        if acc not in processed:
            processed.append(acc)
        result = result + acc["id"] + ","
    return result

Refactor this function to improve both its performance and its readability. Explain what's wrong with the current version and what you would change.