medium🧠 Behavioral

Tell me about a time you had to push back on a client request.

A client asks you to build a feature that you believe will not solve their underlying problem — and may create technical debt. **What to cover:** - How did you identify the mismatch between their request and actual need? - How did you communicate your concern diplomatically? - What was the outcome? Use the **STAR format**: Situation → Task → Action → Result.

💡 Hints (3)

1.Focus on the business outcome, not just the technical concern.
2.Show you listened first before pushing back.
3.Quantify the result if possible (e.g., saved 2 weeks of rework).

✅ View Solution

**Strong answer structure:** **S** — Client at [Company] wanted a custom dashboard export in a proprietary format. **T** — My job was to deliver value, not just ship features. **A** — I ran a 30-min discovery call to understand *why* they wanted it. Turned out they needed the data in their BI tool — which already had a standard CSV connector. I proposed that instead. **R** — Saved 3 weeks of eng time. Client got their insight 2 weeks faster. **Key signals interviewers look for:** curiosity, diplomacy, outcome-orientation.