When you inherit a pipeline with no documentation, what do you do in your first couple of weeks with it?

What the interviewer is looking for

• This question tests ownership & incident response. Owns failures end to end: assesses impact, tells affected people early, fixes the root cause and adds safeguards afterwards.
• What to bring out: Maps lineage and consumers, reads code and run history, adds monitoring and tests, writes documentation as they learn.
• Expect a follow-up like: What would you change first, and what would you leave alone?

Another way it may be asked: A colleague leaves and you take over their undocumented jobs. How do you get to the point where you can safely change them?

A structure to follow: STAR, with the weight on Action and Result

1. Step 1

   Situation

   One or two sentences: where, when and what was at stake. Pick a real example you were close to.

2. Step 2

   Task

   What you personally were responsible for. Say "I", not only "we", so the ownership & incident response you showed is visible.

3. Step 3

   Action

   The two or three things you did and why you chose them over the alternatives. This should be about half your answer.

4. Step 4

   Result

   What changed, in your own measure of it, and what you would do differently. Only use numbers you can stand behind.

This is guidance on shape, not a script. Use your own real experience and facts; never invent details to fill a gap. See the STAR guide and answer frameworks.

Common slips

• Describing what the team did without saying what you did.
• Choosing an example with no clear outcome, or one you cannot answer detailed questions about.
• Ending on the action and skipping the result and what you learned.

How to practise it

Write two bullet points for each STAR letter, then say the answer aloud in about two minutes.

Related questions

• Tell me about the most serious data incident you've owned. What happened, how did you communicate it, and what changed afterwards?
• Can you explain the difference between a fact table and a dimension table, and when you would use each?
• If you had to load a daily file from a partner into a warehouse, how would you make sure running the job twice doesn't create duplicate rows?
• What checks would you put on a new data source before analysts start relying on it?
• Tell me about a time a Spark or similar distributed job was slow or failing. How did you find the cause and what did you change?

Browse all questions