How the interviewer opens it
“Design a service that determines which people and teams must approve a pull request based on path ownership rules. It must support a large, active monorepo and a fleet of repositories of different sizes.”
The prompt is vague on purpose. The first minutes are for you. Reduce the prompt to the core features and agree on the numbers before you draw.
What to clarify first
- Product boundary
- Repository scale
- Traffic, durability, and retention
- Rule meaning
- Changed paths and trusted policy
- Approval eligibility
- Publication deadlines and superseded updates
- Target changes and status reads
- Host contract and review freshness
- Availability and failures
The interviewer has the answers. In a SysRound round, Alex gives these answers, as a real interviewer does.
Scope of a strong answer
Core requirements
- Find the required approvals for every changed path.
- Show which requirements the current approvals satisfy.
- Authorize a merge only when the host can validate the required state.
- Explain which paths and rules create each requirement.
Usually out of scope
- Host Git repositories or implement Git merges.
- Run tests or build software.
- Balance reviewer workloads.
- Support arbitrary scripts as ownership rules.
What interviewers ask about
- Which approvals a PR requires
- A PR can touch paths with different owners. A flat reviewer list loses the distinction between alternatives and separate requirements.
- Correctness during concurrent changes
- A valid approval result can become invalid before merge. Commit checks alone cannot detect a review withdrawal.
- Evaluation cost under frequent changes
- One target update can affect many PRs. Large diffs and frequent review changes create very different amounts of work.
- People, teams, and review changes
- An approval belongs to a person. Account changes and team changes can remove that person's eligibility without changing the PR.
Common mistakes
- Combine all owners into one list and lose separate approval requirements.
- Trust a green status without an atomic merge check of review state.
- Let unmerged ownership edits change who must approve the same PR.
- Assume the host always returns a complete diff.
- Treat directory freshness and review freshness as the same guarantee.
- Evaluate every open PR after every target commit without a work estimate or a clear publication contract.
The bar by level
- Senior (L5/E5)
- Defines enforceable merge checks for commits, review revisions, and expiry. Handles directory freshness and event loss. Separates publication deadlines from target refresh and reuses evidence.
- Staff (L6+/E6+)
- Explains which host guarantees make revocation enforceable. Controls target fanout and uneven repository work. Evaluates merge retry costs without confusing response latency with merge progress.