Design a policy for when a coding agent may edit tests, docs, or infrastructure.
Instruction: Explain how you would govern non-application-code changes from a coding agent.
Context: Assesses whether the candidate can design a practical architecture and explain the main tradeoffs. Explain how you would govern non-application-code changes from a coding agent.
Updated
Official answer available
Read the opening below, then unlock the full answer and practical guidance.
I'd authorize edits by purpose and consequence, not extension alone. Adding a regression for a documented bug is useful; deleting an assertion to get green tests changes the evidence and needs review...
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.
2. Apply it to a real workflow
Practice diagnosis, validation, and everyday tradeoffs.
3. Prepare for senior discussions
Explain failure boundaries, recovery, and production choices.
- A coding agent can modify infrastructure, app code, and data access layers in one task. How do you constrain it? Member answer
- Two coding agents change an API and its client in parallel. How would you integrate their work safely? Member answer
- A coding-agent hook runs before the repository trust prompt. What is wrong with that design? Member answer
Related Questions
-
easy
-
easy
-
easy
-
easy
-
easy
-
easy