How would you explain repo grounding to an interviewer?

Instruction: Describe what repo grounding means for a coding agent.

Context: Checks whether the candidate can explain the core concept clearly and connect it to real production decisions. Describe what repo grounding means for a coding agent.

Updated

Example Answer

Repo grounding means checking a proposed change against this repository's actual interfaces and behavior. If I'm fixing duplicate invoice creation, I'd trace the endpoint to the service and database constraint, inspect callers, and read retry tests before proposing a patch.

I'd keep a small evidence map: relevant paths, symbols, and the commit I inspected. A reviewer can verify why this is the owning code. A search match alone is insufficient: an old helper in another package may have the same name. I'd confirm the live call path and refresh evidence after the checkout changes. Grounding reduces invented APIs and wrong-file edits; it still needs tests and product acceptance criteria.

Why this works

Connects the definition to verifiable artifacts and explains how apparently relevant evidence can be stale.

Practice follow-up

How would you detect that your evidence came from an obsolete implementation?

Your preparation path

Work through these questions in order. Read the answer aloud, then explain it in your own words.

1. Start with the foundations

Build the vocabulary and explain the core decisions.

  1. When is a coding agent the right tool instead of autocomplete or manual engineering? Free sample
  2. What information should a coding agent persist between steps? Free sample
  3. Why do tests matter differently for coding agents than for chatbots? Free sample

2. Apply it to a real workflow

Practice diagnosis, validation, and everyday tradeoffs.

  1. What makes a patch proposal safe enough to apply automatically? Free sample
  2. The agent can find the bug, but its patches are hard for humans to review. What would you change? Member answer
  3. How would you verify a coding agent's web feature beyond a passing build and a screenshot? Free sample

3. Prepare for senior discussions

Explain failure boundaries, recovery, and production choices.

  1. A coding agent can modify infrastructure, app code, and data access layers in one task. How do you constrain it? Member answer
  2. Two coding agents change an API and its client in parallel. How would you integrate their work safely? Member answer
  3. A coding-agent hook runs before the repository trust prompt. What is wrong with that design? Member answer

Related Questions