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

Find And Fix Memory Leaks

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

Your question is Find And Fix Memory Leaks. 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

A client engagement team at Ampcus inherited this task queue class from another vendor's codebase. QA flagged that a long-running worker process using this class grows its resident memory steadily over a multi-day soak test until it's OOM-killed, even though the queue itself never holds more than a few hundred pending tasks at once.

#include <iostream>
#include <string>
#include <vector>

class Task {
public:
    std::string payload;
    Task(std::string p) : payload(p) {}
};

class TaskQueue {
private:
    std::vector<Task*> pending;

public:
    void addTask(const std::string& payload) {
        Task* t = new Task(payload);
        pending.push_back(t);
    }

    void processAll() {
        for (Task* t : pending) {
            handle(t);
        }
        pending.clear();
    }

    void handle(Task* t) {
        if (t->payload.empty()) {
            return;
        }
        std::string* log = new std::string("processed: " + t->payload);
        std::cout << *log << std::endl;
    }

    ~TaskQueue() {
    }
};

How would you identify the memory leak in this snippet, and how would you resolve it? Explain your reasoning, not just the fix.