Tell me about a time when you led a cross‑functional engineering team to deliver a critical feature under a tight deadline. How did you prioritize tasks, resolve conflicts, and maintain quality?

Use the CIRCLES framework: Clarify the goal, Investigate constraints, Recommend a plan, Communicate the plan, Listen to feedback, Execute the plan, Sustain improvements. 1) Clarify: define the feature scope and success metrics. 2) Investigate: assess team capacity, technical debt, and stakeholder priorities. 3) Recommend: create a MoSCoW‑prioritized backlog and a risk register. 4) Communicate: hold a kickoff with all stakeholders, share the plan and expectations. 5) Listen: gather concerns, adjust priorities, and address conflicts through active listening. 6) Execute: enforce sprint ceremonies, pair‑programming, and automated testing. 7) Sustain: conduct retrospectives, capture lessons, and update the knowledge base.

I led a 6‑person cross‑functional team to deliver a real‑time analytics dashboard within a 10‑day sprint. First, I clarified the MVP scope and success metrics with the product owner, ensuring alignment on what constituted a 'done' feature. I then investigated constraints: team capacity, existing technical debt, and integration points with the data lake. Using the CIRCLES framework, I recommended a MoSCoW‑prioritized backlog and a risk register that flagged potential API latency issues. I communicated the plan in a kickoff meeting, setting clear expectations and sprint goals. Throughout the sprint, I listened to daily stand‑ups, addressed conflicts by mediating design debates, and re‑allocated resources when a senior engineer identified a bottleneck in the ETL pipeline. Execution involved enforcing pair‑programming, automated unit and integration tests, and continuous integration pipelines to catch regressions early. After launch, I conducted a retrospective, captured lessons learned, and updated the team's knowledge base to sustain improvements. The result was a feature delivered on time, with a 25% reduction in query latency and a 30% increase in user engagement.