Behavioral

Solution

Name the SLO you missed (freshness, volume, or grain), how you found it (Datadog, row-count check, a Slack from BI), and the first safe move — stop writers, clone or time-travel, do not reload on a live table. Then the permanent fix: a test at that grain, an owner, and a page that is not “job succeeded.” Interviewers want the clock and the control, not a hero story.

Solution

Restate the grain and the SLA you already promised. One more source at a different grain is a fan-out, not a favor. Offer a dated spike or a separate mart. “We will add it and DISTINCT later” is the story they are waiting to fail. Good answers name the person you told and what shipped instead.

Solution

Write both grains on the board: order vs line vs payment. Pick one for the gold table and give the other a named mart. Do not average the disagreement into a DISTINCT. Close with who owns the metric definition now — dbt docs, a semantic layer, or finance. The interview is about conflict plus a contract, not who won.

Solution

Do not guess. Query history, warehouse resume count, a clustering job, a Cortex or BI refresh loop. Show credits by warehouse and by user, then one change you made (auto-suspend, a smaller size, materialize the explore). Chargeback tags if you have them. “We will migrate to Spark” without a number is a fail.

Solution

Revoke, audit the extract, tell security, then the control: separate PII, column grants, no SELECT * on bronze, and a test that fails if an email lands in a marketing mart. “I asked them not to do it again” is not a control. Banks and healthcare loops will push until you name the grant.

Solution

Pick a real miss: Type-1 when you needed Type-2, Streams+Tasks when you needed Airflow, pandas on a 40 GB join. Say the incident that proved it, the rollback, and the rule you wrote down. Humility plus a written policy beats a perfect résumé of wins.

Solution

Pair on the first unique/not_null tests, require them on every gold PR, and show a past fan-out. Do not take the keyboard forever. Interviewers want coaching plus a gate, not “I rewrote it Friday night.”

Solution

Page on the contract test, not the person. Share the failing rows, the SLA, and a dated fix. Then move the contract upstream so warehouse tests are defense in depth. Blame in Slack is the junior tell; a written producer contract is the senior one.

Solution

STAR: situation (wrong grain), task (stop the blast), action (revert pointer, post the invariant, add a unique test), result (hours of bad numbers, then a written owner). Do not skip who you told. Hiding it is the fail.

Solution

Offer a dated prototype on bronze with a watermark in the title, not gold. Gold needs a key and an owner. Give them a number they can use with a caveat, or a date you can certify. “No” without an alternative is brittle; “certified Friday” without a contract is how you get fired later.

Solution

A spike: one workload, cost, and a consumer. Data, not identity. If you lost, say what you learned (maybe the warehouse was right for BI). If you won, say the rollback plan. Ego is the junior tell.

Solution

User-facing gold first (revenue, auth), then the job that unblocks others, then noise. Communicate ETA in the incident channel before you debug. Heroic silence is not seniority.

Solution

Pair on the grain, add the exposure/test so the next person sees the survivor, and blamelessly document why two revenues existed. Mentorship is a process change, not a Slack dunk.

Solution

Do not defend the dashboard first. Align grain (invoice vs cash), timezone, and filters. Then reconcile a single day in SQL together. Bring the query, not a feeling. Offer a bridge table if both definitions must live.

Solution

Refuse, offer synthetic or masked rows, and if pressured, escalate to security — in writing. A demo is not a lawful basis. This is a pass/fail behavioral, not a clever workaround.

Solution

The decision record, the prototype that showed cost, and the people you unblocked. Do not pretend it shipped. Interviewers want learning and shutdown hygiene, not a fairy tale.

Solution

Give a timed break-glass with logging, or a narrower role that unblocks the task. Explain blast radius (UNDROP, shares, billing). If leadership overrules, write the exception. Permanent ACCOUNTADMIN is how incidents become existential.

Solution

Concrete: auto-suspend, a clustering key on a real filter, killing a 5-minute dashboard tick, or a warehouse per team. Percent and dollars. “We migrated everything to X” is not the only story — small levers count.