Design an architecture review process for 60 product teams that does not slow delivery.

Short answer

Define clear triggers so only significant decisions are reviewed, give teams templates and paved roads so most decisions are pre-approved, automate standards checks in pipelines, run reviews asynchronously with short SLAs, record decisions as ADRs, and measure review lead time and outcomes.

Detailed answer

  • Tiers: Tier 0 (team-local) – ADR in repo, no review; Tier 1 (cross-team, new data store from approved list) – async peer review by domain architect within 3 days; Tier 2 (new technology, Tier 0/1 systems, regulated data) – ARB session within a week.
  • Paved roads: approved stacks and templates make many decisions automatic.
  • Automation: policy as code in cloud, dependency allowlists, API linting, security scans.
  • Exceptions: time-boxed, owned, visible.
  • Feedback loop: publish decisions, measure review lead time, survey teams.

What the interviewer expects

Balance between control and autonomy, specific mechanisms, metrics.

Common mistakes to avoid

Reviewing everything, late-stage gates, document-heavy submissions, no SLAs.