Describe a time when you had to collaborate with cross‑functional teams to deliver a product feature under tight deadlines. How did you ensure alignment and manage conflicting priorities?

STAR + MECE (120‑150 words, no story): S – Set context (team, deadline, goal). T – Define challenge (conflicting priorities). A – Action (stakeholder mapping, RICE prioritization, daily stand‑ups, shared OKRs). R – Result (feature shipped on time, metrics). MECE – Break actions into mutually exclusive, collectively exhaustive categories: communication, prioritization, execution.

I spearheaded the rollout of a new in‑app notification system for our mobile app, with a 4‑week sprint and three cross‑functional squads (engineering, design, data). The challenge was aligning divergent priorities: engineering wanted a robust API, design focused on UX, and data sought actionable insights. I began by mapping all stakeholders and their objectives, then applied the RICE framework to score each feature request. We created a shared Kanban board and scheduled daily stand‑ups to surface blockers. I also set up a weekly demo to keep stakeholders informed and adjust scope in real time. The result was a feature delivered 2 days ahead of schedule, a 28% increase in user engagement, and a 15% reduction in churn within the first month. This experience reinforced the importance of transparent communication, structured prioritization, and continuous stakeholder alignment.