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

Choosing Batch vs Real Time

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

Your question is Choosing Batch vs Real Time. 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're planning a new workflow in a data pipeline and need to decide how it should run. Some consumers may need fresh data quickly, while others can work with scheduled updates if the pipeline is simpler and cheaper.

Question

How do you decide whether a workflow should run in real time or in batch?

What Matters

  • Freshness requirement and business SLA
  • Volume and arrival pattern of data
  • Operational complexity and support burden
  • Replay, backfill, and audit requirements
  • Data quality tolerance for late or missing records

Batch vs Stream

Latency
Complexity
Cost model
Best fit