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 vs Rewrite Decision

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

Your question is Refactor vs Rewrite Decision. 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

Scenario

You are evaluating an aging core service that still powers an important part of a B2B SaaS platform. The system has accumulated technical debt, delivery speed is slowing, and reliability issues are starting to affect adjacent teams, but it also contains years of business logic that would be expensive to rediscover. You need to decide whether to refactor incrementally, rewrite the system, or continue investing in the current architecture for now.

Question

How do you decide whether to refactor, rewrite, or keep investing in an existing system?

What Makes This Hard

  • Technical debt is real, but so is the risk of losing embedded business logic.
  • The system is business-critical, so disruption costs are high.
  • Different stakeholders will prefer different answers for valid reasons.
  • The right choice depends on evidence, not engineering instinct alone.