Describe how you handled a situation where cross-functional team priorities were misaligned.

In Simple Words: Anchor discussions to shared company-level OKRs and customer metrics, rather than departmental silos.

The STAR Response:

• Situation: In our mobile app development, our Backend team was prioritizing a gRPC protocol overhaul to reduce server costs, while the Mobile Frontend team was blocked on shipping an Apple Pay checkout feature needed for Q4 revenue goals.
• Task: Align engineering roadmaps so the business hit its revenue milestone without abandoning backend performance goals.
• Action:
  1. Facilitated a cross-functional alignment session between backend and mobile engineering leads.
  2. Framed the conversation around company-level Q4 OKRs: shipping Apple Pay was projected to increase mobile conversions by 18%, whereas the gRPC savings were minimal in the short term.
  3. Agreed on a phased compromise: Backend engineers mocked the Apple Pay API contracts first, allowing Mobile engineers to build in parallel against mock servers.
  4. Scheduled the gRPC migration for Q1 directly following the holiday sales surge.
• Result: The team launched Apple Pay on schedule, boosting mobile conversion by 21%, while the gRPC migration was delivered smoothly in the subsequent quarter.

Practical Script & Summary Template

### Cross-Team Alignment Playbook:
- Escalate to shared company OKRs: "Which deliverable drives the highest customer impact this quarter?"
- Decouple teams via API contracts: Use OpenAPI / Swagger specifications to enable frontend and backend to develop in parallel without blocking.