In today’s matrix‑driven reviews, seniority is measured not just by delivery speed but by the ability to surface the right problems before anyone asks. As a software engineer at L2, you’ve already proven impact with a BU‑wide project; the missing piece is visible influence—showing that you can map product goals to technical opportunities without waiting for a ticket. Start by framing your insights as “opportunity briefs” for the PM and TL, linking data, user pain points, and potential ROI. This positions you as a proactive partner rather than a task‑taker, and it respects the strategic lens your leaders bring. **Key takeaways** - Schedule a brief “impact review” with your PM each sprint to propose one unassigned improvement. - Use metrics (adoption, latency, error rates) to justify why the demand matters. - Document these initiatives in your performance log to create a clear evidence trail. What small, data‑driven suggestion can you pitch this week to demonstrate autonomous thinking without stepping on anyone’s turf?