Your question is Prioritizing in a High-Stakes Build. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
What is your process for prioritizing competing cross-functional feature requests or engineering bugs during a high-stakes build cycle?
Answer as if you are the PM owning launch readiness. Focus on how you triage, align stakeholders, and make trade-offs when engineering, QA, design, and leadership all want different things. Be explicit about how you decide what ships, what slips, and what gets escalated.