How do you fix a 200-item unmanageable product backlog?

WHAT THIS TESTS: This question tests your leadership, facilitation skills, and strategic thinking beyond rote Scrum mechanics. The interviewer is assessing your ability to diagnose a systemic failure (how did the backlog become a junk drawer?), propose a collaborative solution that empowers the team and Product Owner, and implement a process to prevent recurrence. It separates candidates who just follow process from those who improve the entire system.

A GOOD ANSWER COVERS: A strong answer outlines a specific, multi-step, collaborative strategy. First, propose a temporary moratorium on adding new items and schedule a dedicated, time-boxed workshop (e.g., a single 4-hour session) with the entire Scrum Team, especially the Product Owner. Second, begin the workshop by defining or reaffirming the Product Goal. This is the single filter for all subsequent decisions. Third, ruthlessly triage the entire backlog against this goal. For each of the 200+ items, ask: "Does this directly advance the current Product Goal?" If no, archive it immediately. If yes, do a rapid high-level sizing (e.g., t-shirt size). Fourth, with the small subset of remaining items, work with the PO to order them for the next 1-2 Sprints. Finally, propose a new, sustainable process for backlog health, like stricter entry criteria or a "one in, two out" policy for a period.

COMMON WRONG ANSWERS: The biggest red flag is the "hero" answer: "I would personally go through all 200 items and prioritize them for the PO." This usurps the PO's role and shows a misunderstanding of team ownership. Another weak answer is focusing on tools ("We need a better Jira workflow"), which confuses the symptom with the cause. Simply saying "we need to do more backlog refinement" is too vague for a senior role. Blaming the Product Owner is also a major red flag; a senior engineer frames this as a team process problem and facilitates a collaborative solution.

LIKELY FOLLOW-UPS: "What if the Product Owner is hesitant to archive items?" (Discuss creating a separate, un-prioritized 'Parking Lot' or 'Archive' project to reduce their anxiety, while emphasizing the cost of maintaining a large backlog). "What if the team doesn't have a clear Product Goal?" (Propose facilitating a session with the PO and key stakeholders to define one as the absolute first step). "What specific prioritization technique would you use in the workshop?" (Be ready to explain a simple one like Impact/Effort Matrix or a value-based question like "If we could only do one thing, what would it be?").

ONE CONCRETE EXAMPLE: "Our backlog had grown to over 300 items, and sprint planning was taking hours. I proposed a 'Backlog Bankruptcy' meeting. We got the PO and the two other senior devs in a room for 3 hours. We put our main quarterly OKR on the monitor. For every item, we asked 'Is this the most important thing we can do to move this Key Result?' We were ruthless. We archived over 250 tickets. It was liberating. This act of radical focus allowed us to ship a critical feature two weeks later that had been buried in the noise for months."