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

Java Memory Management Process

MediumTechnical Fundamentals00:00
Practice interviewer
In session
5 left
00:00

Your question is Java Memory Management Process. 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

Relevance Lab's automation platform keeps a cache of recent test-run logs in memory for quick QA dashboard access. Here's the class responsible for it.

import java.util.*;
import java.io.*;

public class TestRunLogger {
    private static List<String> allLogs = new ArrayList<>();

    public void logRun(String testId, String result) {
        String entry = testId + ":" + result;
        allLogs.add(entry);

        try {
            FileWriter fw = new FileWriter("run_history.log", true);
            fw.write(entry + "
");
        } catch (IOException e) {
            e.printStackTrace();
        }
    }

    public String buildReport() {
        String report = "";
        for (String log : allLogs) {
            report = report + log + "
";
        }
        return report;
    }
}

What would the memory management process be for this code in Java? Walk through what happens as logRun is called repeatedly over a long-running test session, and what you'd change.