# Explain Your Ownership in a Large System Choose a substantial project involving a system built by multiple people or teams. Explain exactly what you owned. Distinguish the system's overall scope from your decision authority, implementation work, operational responsibility, and measurable impact. ### Constraints & Assumptions - Use one real project rather than a survey of several projects. - Keep the initial answer to about five minutes, with details available for follow-ups. - Do not imply ownership of work performed by others. - Use architecture diagrams only to clarify boundaries and decisions. ### Clarifying Questions to Ask - Should the deep dive emphasize architecture, execution, operations, or cross-team leadership? - How much business and organizational context would be useful? - Is the interviewer looking for an individual-contributor or technical-leadership example? ### Hints - Draw the system boundary first, then highlight the components and decisions that were yours. - Prepare one difficult trade-off, one failure or surprise, and one result you can defend. - Be precise about where you consulted, influenced, decided, implemented, or operated. ### What a Strong Answer Covers - A comprehensible system overview without losing the ownership boundary. - Specific personal decisions, work products, and operational responsibilities. - Collaboration and dependency management without taking team credit. - Evidence of impact, trade-offs, and lessons learned. - Enough technical depth to support detailed follow-up questions. ### Follow-up Questions 1. Which decision could only you make, and which required broader approval? 2. What part of the system would have been different without your contribution? 3. What failed in production, and what did you personally do afterward? 4. If you had another quarter, what would you change and why?