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
Memory Block Tracker with Thread Safety
00:00
5 left

Memory Block Tracker with Thread Safety

HardSQL · PostgreSQL

Problem

Design a system that tracks changed memory address blocks (64-byte blocks); given changed ranges like [1,2],[3,4],[6,9],[10,12], return merged ranges [1,4],[6,12] on query, and make it thread-safe.

Asked in the System coding stage. Treat range endpoints as inclusive block numbers and merge both overlapping and directly adjacent ranges.

Output

  1. Return one row per merged range with merged_start_block and merged_end_block.
  2. Exclude incomplete or invalid ranges, order by merged_start_block ascending, and ensure concurrent sessions use a consistent view.

Schema

changed_memory_ranges
ColumnTypeDescription
range_idPKBIGINTUnique identifier for the recorded changed range
start_blockBIGINTInclusive first 64-byte block number
end_blockBIGINTInclusive last 64-byte block number
Tableschanged_memory_ranges
Interviewer

Your question is Memory Block Tracker with Thread Safety. Start with the requirements and the one table in the Question tab.

Run and submit as often as you like. When you're ready, talk me through your approach or go straight to the code.

You need to log in / sign up to run or submit.
CodePostgreSQL
Sign up free to run your codeLog inLn 1
Run your query to see results here.