Intervu is in beta — feedback welcome at support@intervu.io
Library
AppleSoftware Engineer· Behavioral

Walk me through a time you killed a feature — not because it was too hard to build, but because you believed it genuinely shouldn't exist. What convinced you, and what did it cost you to say no?

Weak · sample answer

We were adding a custom notification scheduler that product had pushed for three months. I pulled usage data and saw 94% of users never touched advanced settings. I flagged it to the PM, we cut it from the roadmap, and it never shipped.

Why this scores weak

Data-driven cut with no real cost — usage stats, not a principled argument about why it shouldn't exist.

Average · sample answer

We were shipping a location-based notification feature and I pushed hard to pull it. Privacy tradeoffs felt wrong. After two weeks of debate, leadership didn't kill it — they moved it to Q3. It shipped six months later without my changes.

Why this scores average

Values-based conviction with genuine cost — pushed on privacy, lost, and names it honestly.

Strong · sample answer

We were adding a note-pinning feature to a focus app. I killed it three weeks in — pinning created a second organizational layer that contradicted the app's single-priority model. My PM pushed back hard. We shipped without it. Retention actually improved.

Why this scores strong

Identifies a structural contradiction in the product model — reasoning is principled and survives the outcome.