Describe a cross-team data project where you had to align architectural boundaries, ownership, and SLAs. How did you handle conflicting priorities, technical debt, and the scalability of communication as the number of stakeholders grew?

Architectural Logic: Cross-team projects need clear data contracts (schema, freshness, quality), defined ownership (who owns ingestion, transformation, consumption), and SLAs that map to business impact. Why boundaries matter: Prevents circular dependencies; enables parallel work; makes failure domains explicit. Scalability of coordination: Weekly syncs don't scale past ~5 teams; move to async updates, shared docs, and contract-first interfaces. Conflicting priorities: Tie to revenue/risk; use RACI; escalate blockers with impact quantification. Technical debt: Negotiate time-boxed remediation; avoid blocking new features. Cost: Coordination overhead grows O(n²) with teams; reduce via standardization and self-service. Best practice: Document interfaces and SLAs; use efficient meetings; track blockers visibly; balance responsiveness with focused work.