Interview room
Monitor freshness SLAs, volume anomalies, P1/P2 tiers. Green jobs can still be stale.
Basics
Freshness is data time, not DAG success. SLA catalog per table. Volume baselines catch empty success. Severity prevents fatigue.
Prompt
Track watermarks vs SLA; volume bands; route P1/P2; runbooks; hundreds of tables.
Good
Owned SLA registry; freshness+volume; dependency-aware pages; mute windows.
Clarify/scope
Hours, on-call topology, source vs DE RACI.
Scoring lens: Data Freshness Monitoring
Interviewers reward incident-first teaching, a clear control loop, and named owners. Tool logos without that loop score poorly.
Weak vs strong answers on Data Freshness Monitoring
Weak: list products. Strong: tell the failure story, define the mechanism, draw the path, state rollout and monitors.
Scope control
Say what is out of scope for v1. Come back only if follow-ups demand it. This is a seniority signal for Data Freshness Monitoring.
Clarifying then committing
Ask a few high-use questions about SLAs, owners, and scale, then sketch. Endless questions without a diagram look evasive.
Watermark policy note
Event tables: now - max(event_time). Snapshot tables: now - last_publish_ts. Mixing them silently creates fake pages. Document per table class.
Source-late RACI
When bronze watermark is stale, page source owners primary and DE secondary. DE should not be the only human punished for vendor outages.
Planned windows
Encode expected batch completion windows so midnight work does not look like an incident. Mute is not the same as ignore: windows are explicit.
Interview framing detail 1
For lb-sd-29, spend the first minutes making the problem concrete: who gets hurt when this fails, what SLA is implied, and what is explicitly out of scope. Then teach the prerequisite concept before proposing boxes. A candidate who names vendors first usually loses the plot. Write two clarifying questions on the board and answer them with assumptions if the interviewer shrugs. Keep the first diagram small enough to redraw when a follow-up changes a constraint.
Interview framing detail 2
For lb-sd-29, spend the first minutes making the problem concrete: who gets hurt when this fails, what SLA is implied, and what is explicitly out of scope. Then teach the prerequisite concept before proposing boxes. A candidate who names vendors first usually loses the plot. Write two clarifying questions on the board and answer them with assumptions if the interviewer shrugs. Keep the first diagram small enough to redraw when a follow-up changes a constraint.
Interview framing detail 3
For lb-sd-29, spend the first minutes making the problem concrete: who gets hurt when this fails, what SLA is implied, and what is explicitly out of scope. Then teach the prerequisite concept before proposing boxes. A candidate who names vendors first usually loses the plot. Write two clarifying questions on the board and answer them with assumptions if the interviewer shrugs. Keep the first diagram small enough to redraw when a follow-up changes a constraint.
Interview framing detail 4
For lb-sd-29, spend the first minutes making the problem concrete: who gets hurt when this fails, what SLA is implied, and what is explicitly out of scope. Then teach the prerequisite concept before proposing boxes. A candidate who names vendors first usually loses the plot. Write two clarifying questions on the board and answer them with assumptions if the interviewer shrugs. Keep the first diagram small enough to redraw when a follow-up changes a constraint.
Interview framing detail 5
For lb-sd-29, spend the first minutes making the problem concrete: who gets hurt when this fails, what SLA is implied, and what is explicitly out of scope. Then teach the prerequisite concept before proposing boxes. A candidate who names vendors first usually loses the plot. Write two clarifying questions on the board and answer them with assumptions if the interviewer shrugs. Keep the first diagram small enough to redraw when a follow-up changes a constraint.
Interview framing detail 6
For lb-sd-29, spend the first minutes making the problem concrete: who gets hurt when this fails, what SLA is implied, and what is explicitly out of scope. Then teach the prerequisite concept before proposing boxes. A candidate who names vendors first usually loses the plot. Write two clarifying questions on the board and answer them with assumptions if the interviewer shrugs. Keep the first diagram small enough to redraw when a follow-up changes a constraint.