tl;dr: A staff engineer at Google (working on Perfetto) describes finding high-impact problems by passively absorbing complaints and requests across teams, then letting them accumulate rather than jumping on the first vocal request. The key skill is spotting the common underlying shape across seemingly unrelated requests—then pressure-testing the hypothesis via prototypes, RFCs, and conversations before committing to build. Solving real problems compounds: it earns trust and pulls the engineer into more conversations, widening their view of the org.