Describe a time you had to push back on a Product Manager, Designer, or Stakeholder request.

In Simple Words: Never say "No" without context. Reframe pushback as presenting trade-offs, estimating risk, and offering viable alternatives that achieve the business goal safely.

The STAR Response:

• Situation: Two days before a marketing launch, a Product Manager requested adding a "Download All Lifetime User Records as CSV" button on the customer account dashboard.
• Task: Prevent database exhaustion and memory crashes on our production API while satisfying the customer data export requirement.
• Action:
  1. Explained the architectural risk constructively: executing a synchronous SELECT * across hundreds of thousands of rows inside an HTTP request would exhaust API Node.js heap memory and lock the database.
  2. Validated their business need: customers simply needed their data for accounting, but did not require it synchronously within 2 seconds.
  3. Proposed an asynchronous alternative: the button would trigger a background worker that generates the CSV in S3, creates a signed URL, and emails it to the user within 5 minutes.
  4. Built and shipped the asynchronous exporter within 36 hours.
• Result: Delivered 100% of the customer functionality without adding any risk to primary transactional API latency or database stability.

Practical Script & Summary Template

### How to Push Back Constructively:
1. **Validate Intent**: "I understand the urgency behind giving customers access to their lifetime records."
2. **Explain Concrete Risk**: "If an account with 100k records clicks this synchronously, the API will hit an out-of-memory crash, taking down checkout for everyone."
3. **Offer High-Quality Alternative**: "If we process this via our background queue and email a secure S3 link within 3 minutes, we protect production stability while delivering the exact same user value."